> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptoquant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ETF Bitcoin Demand 30-days

> The 30-day and 1-year Bitcoin purchase from US-based ETFs

## What it measures

Net cumulative BTC purchased or sold by US spot Bitcoin ETFs over a 30-day and 1-year rolling window.

## How to interpret it

30-day.
Positive = ETFs are net buyers. Negative = net sellers. Accelerating = institutional conviction growing. Decelerating even while positive = fading conviction.

1-year.
Reveals whether institutional adoption is genuinely growing structurally or temporarily. Allows direct year-over-year comparison of institutional participation.

## Key thresholds

\~9K BTC/day avg (Q1 2024) = peak buying pace; 5–8K BTC/day = strong demand; Near 0 or negative = net selling mode; ETF demand = \~33% of total demand at Dec 2024 peak

## How to use it

Monitor alongside broader apparent demand. ETF demand alone is insufficient to drive ATH rallies without expanding total market demand.

<Card title="Run this metric in CryptoQuant Analytics" icon="chart-line" href="https://cryptoquant.com/analytics/query/686530f2d040215728725e4e" />


## OpenAPI

````yaml openapi/v2.json GET /community/bitcoin-etf-demand
openapi: 3.0.0
info:
  version: 2.0.0-beta
  title: CryptoQuant Data API v2
  description: >-
    The CryptoQuant Data API v2 serves curated, research-grade indicators built
    on the v1 conventions — the `status`/`result` response envelope, Bearer
    token authentication, and the `window`/`from`/`to` time parameters. Each
    metric ships with an interpretation guide covering what it measures, key
    thresholds, and how to combine it with other metrics.
  termsOfService: https://cryptoquant.com/terms-of-service
  contact:
    name: API Support
    email: contact@cryptoquant.com
servers:
  - url: https://api.cryptoquant.com/v2
    description: Default server
security: []
tags:
  - name: Community-built Indicators
paths:
  /community/bitcoin-etf-demand:
    get:
      tags:
        - Community-built Indicators
      summary: ETF Bitcoin Demand 30-days
      description: The 30-day and 1-year Bitcoin purchase from US-based ETFs
      operationId: V2getBitcoinEtfDemand
      parameters:
        - name: window
          in: query
          required: false
          description: Time interval for aggregation.
          schema:
            type: string
            default: day
          example: day
        - name: from
          in: query
          required: false
          description: >-
            Starting time, formatted as YYYYMMDDTHHMMSS (UTC). If `window=day`,
            YYYYMMDD is also accepted.
          schema:
            type: string
        - name: to
          in: query
          required: false
          description: >-
            Ending time, formatted as YYYYMMDDTHHMMSS (UTC). If `window=day`,
            YYYYMMDD is also accepted.
          schema:
            type: string
        - name: limit
          in: query
          required: false
          description: Maximum number of data rows to return. Ranges from 1 to 10,000.
          schema:
            type: integer
            default: 100
            minimum: 1
            maximum: 10000
      responses:
        '200':
          description: Monitoring Bitcoin demand
          content:
            application/json:
              schema:
                type: object
                required:
                  - status
                  - result
                properties:
                  status:
                    $ref: '#/components/schemas/Status'
                  result:
                    type: object
                    properties:
                      window:
                        type: string
                      data:
                        type: array
                        items:
                          type: object
                          properties:
                            datetime:
                              type: string
                              description: >-
                                The datetime, formatted as YYYY-MM-DD HH:MM:SS
                                (UTC).
                              example: '2026-06-14 00:00:00'
                            etf_demand_30d:
                              type: number
                              description: >-
                                Net BTC purchased or sold by US spot Bitcoin
                                ETFs over a 30-day rolling window.
                              example: -53782.96
                            etf_demand_1y:
                              type: number
                              description: >-
                                Net BTC purchased or sold by US spot Bitcoin
                                ETFs over a 1-year rolling window.
                              example: 1592.04
      security:
        - AccessToken: []
      x-codeSamples:
        - lang: Shell
          source: >-
            curl -X GET
            "https://api.cryptoquant.com/v2/community/bitcoin-etf-demand?window=day"
            \

            -H "Authorization: Bearer <YOUR_API_KEY>"
        - lang: JavaScript
          source: >-
            fetch("https://api.cryptoquant.com/v2/community/bitcoin-etf-demand?window=day",
            { headers: { "Authorization": "Bearer <YOUR_API_KEY>"} })
              .then(response => response.json())
              .then(data => console.log(data))
        - lang: NodeJS
          source: |-
            require('axios')
              .get("https://api.cryptoquant.com/v2/community/bitcoin-etf-demand?window=day", { headers: { Authorization: 'Bearer <YOUR_API_KEY>' } })
              .then(response => console.log(response))
        - lang: Ruby
          source: >-
            require 'net/http'

            uri =
            URI("https://api.cryptoquant.com/v2/community/bitcoin-etf-demand?window=day")

            req = Net::HTTP::Get.new(uri)

            req["Authorization"] = "Bearer <YOUR_API_KEY>"

            res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) {
            |http| http.request(req) }

            puts res.body
        - lang: Python
          source: >-
            import requests

            headers = {'Authorization': 'Bearer <YOUR_API_KEY>'}

            url =
            "https://api.cryptoquant.com/v2/community/bitcoin-etf-demand?window=day"

            print(requests.get(url, headers=headers).json())
components:
  schemas:
    Status:
      type: object
      description: >-
        Returned with every response; indicates whether the request was
        successful.
      example:
        code: 200
        message: success
      required:
        - code
        - message
      properties:
        code:
          type: integer
          format: int32
          description: HTTP status code.
          example: 200
        message:
          type: string
          description: Text description of the error or success.
          example: success
  securitySchemes:
    AccessToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      x-default: Bearer <YOUR_API_KEY>
      description: >-
        For each API request, include the `Authorization` HTTP header with
        `Bearer <YOUR_API_KEY>`.

````