24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/hl/hype-burn-stats
GETAvailable

HYPE burn statistics

HYPE burn statistics

GET/api/hl/hype-burn-stats

Request

This endpoint takes no parameters.

Example request

curl -s "https://www.coinboss.com/api/hl/hype-burn-stats"

Response fields

The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.

FieldTypeUnitDescription
successboolean—true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`.
updatednumbermsWhen the data was last updated.
dataSincenumbermsStart of the fill data behind these statistics (2026-07-15 UTC); windows reaching further back are marked `partial`.
supplyobject—Supply in coins.
supply.maxSupplynumberHYPEMaximum HYPE supply from the latest hourly supply snapshot (1,000,000,000 is assumed when no snapshot exists).
supply.totalSupplynumber—Total supply in coins.
supply.circulatingnumber—Circulating supply in coins.
supply.markPxnumberUSDMark price.
supply.change24hnumberfractionChange of `markPx` against the price of the last recorded fill at least 24 hours old (0.01 = 1 %); null when there is none.
supply.snapshotTimenumbermsTimestamp.
cumulativeobject—Running total taken from the assistance fund's latest buyback fill: its HYPE position before the fill plus the fill size.
cumulative.hypenumber—Value for HYPE.
cumulative.usdnumberUSDValue.
cumulative.pctOfMaxnumberfraction`cumulative.hype` ÷ `supply.maxSupply` (0.05 = 5 %).
cumulative.asOfnumbermsTime of the buyback fill the cumulative total is taken from; null when no buyback has been recorded.
burn24hobject—Totals of assistance-fund buybacks and HYPE spot fees over the last rolling 24 hours.
burn24h.hypenumber—Value for HYPE.
burn24h.usdnumberUSDValue.
burn24h.txsnumber—Transactions.
burn24h.bySourceobject—The 24-hour totals split by source; keys are `af_buyback` and `spot_fee`.
burn24h.bySource.af_buybackobject—HYPE bought back by the assistance fund in the last 24 hours.
burn24h.bySource.af_buyback.hypenumber—Value for HYPE.
burn24h.bySource.af_buyback.usdnumberUSDValue.
burn24h.bySource.af_buyback.cnumbercountNumber of buyback fills in the last 24 hours.
burn24h.bySource.spot_feeobject—HYPE taken as spot trading fees in the last 24 hours.
burn24h.bySource.spot_fee.hypenumber—Value for HYPE.
burn24h.bySource.spot_fee.usdnumberUSDValue.
burn24h.bySource.spot_fee.cnumbercountNumber of spot-fee fills in the last 24 hours.
burn7dobject—Totals of both sources over the last rolling 7 days.
burn7d.hypenumber—Value for HYPE.
burn7d.usdnumberUSDValue.
annualizedobject—Annualised rate: HYPE of the last 30 days ÷ `windowDays` × 365 ÷ total supply.
annualized.ratenumber—Rate.
annualized.windowDaysnumberdaysDays of data actually available inside the 30-day window used for `rate` (at most 30).
periodsarray—Totals over rolling windows of 30, 91 (`3m`), 182 (`6m`) and 365 (`1y`) days.
periods[]object—One window; `partial` is true when the window starts before `dataSince`.
periods[].keystring—Key.
periods[].daysnumber—Daily values or number of days.
periods[].hypenumber—Value for HYPE.
periods[].usdnumberUSDValue.
periods[].txsnumber—Transactions.
periods[].partialboolean—true when only part of the expected data is present.
dailyarray—Daily values.
daily[]object—Daily values.
daily[].datestring—Calendar date (UTC).
daily[].afnumberHYPEHYPE bought back by the assistance fund on that UTC day.
daily[].feenumberHYPEHYPE taken as spot trading fees on that UTC day.
daily[].afUsdnumberUSDUSD value of that day's assistance-fund buybacks at fill prices.
daily[].feeUsdnumberUSDUSD value of that day's HYPE spot fees at fill prices.
daily[].txsnumber—Transactions.

Generated 2026-11-11 23:00 UTC from 1 real responses.

Example response

/api/hl/hype-burn-stats · Real response captured 2026-11-13 04:02:56 UTC. Long arrays and maps are shortened for display: daily had 31 items; periods had 4 items.

  • {
    • "success": true,
    • "updated": 1794542576964,
    • "dataSince": 1784073600000,
    • "supply": {
      • "maxSupply": 1000000000,
      • "totalSupply": 998750842.1875432,
      • "circulating": 301716577.5760016,
      • "markPx": 71.338,
      • "change24h": -0.01290974249699059,
      • "snapshotTime": 1794541533063
      },
    • "cumulative": {
      • "hype": 48876713.80473923,
      • "usd": 3486767009.402487,
      • "pctOfMax": 0.04887671380473923,
      • "asOf": 1794542522355
      },
    • "burn24h": {
      • "hype": 35382.43393208404,
      • "usd": 2517259.1733999685,
      • "txs": 40821,
      • "bySource": { … 2 }
      },
    • "burn7d": {
      • "hype": 158346.25881098903,
      • "usd": 11676655.431899749
      },
    • "annualized": {
      • "rate": 0.010118555842570877,
      • "windowDays": 30
      },
    • "periods": [
      • { … 6 },
      • { … 6 }
      ],
    • "daily": [
      • { … 6 },
      • { … 6 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
45s
Edge micro-cache
10s
Update frequency
burn events ingested every 10 s; supply snapshot hourly; API cache 45 s
Window
24h / 7d / 30d / all; event-level data starts 2026-07-15 (earlier windows flagged partial)
Data sources
HYPE burn statistics computed from on-chain burn events read from our own Hyperliquid node, with supply snapshots from the official info API.
Exchange coverage
Two burn sources: Assistance Fund buybacks and spot trading fees
Pagination
none
Units
HYPE and USD; annualized rate in percent
Method
annualized burn rate = burn over last 30 days / days covered * 365 / totalSupply
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 04:02:56 UTCHTTP 2006024 msSchema matchesNewest data point 0s old

Availability, last 30 days

99.51% of 410 checks passed

Errors

Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →

CodeHTTPMeaningWhat to do
INVALID_PARAM400A required parameter is missing or a value is not accepted. `param` names the parameter when it is known.Do not retry unchanged; fix the request.
UNAUTHORIZED401The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key.Do not retry unchanged.
FORBIDDEN403The route is not part of the public API (internal or account-only).Do not retry.
NOT_FOUND404Unknown route, or the requested coin / exchange / fund does not exist.Do not retry; check the path and identifiers against the catalog.
RATE_LIMITED429More requests than the per-minute limit. `Retry-After` gives the seconds to wait.Wait for `Retry-After`, then retry with backoff.
INTERNAL500Unexpected server error. The message is generic by design; quote `request_id` when reporting it.Retry once after a few seconds; report it with the request id if it persists.
UPSTREAM_FAILED503The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place.Retry with backoff; check the status page.
UNAVAILABLE501 / 503The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet.Retry later; the catalog marks endpoints that are unavailable by design.
REQUEST_FAILED200Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status.Depends on the message; treat as a failed request.

Try it

GET/api/hl/hype-burn-statsAvailable
Parameters

No parameters.

Request URLhttps://www.coinboss.com/api/hl/hype-burn-stats
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.