Contents
Predicted next funding
Predicted next funding per coin for Hyperliquid, Binance and Bybit (from Hyperliquid predictedFundings, refreshed every 5 minutes): hourly rate, annualised rate, funding interval and next funding time per venue.
/api/v1/funding/predictedEvery keyDescription
Disabled venues are left out, and so are Binance / Bybit during the licence review (meta.restricted). Sorted by Hyperliquid open interest.
Who can call it
Available with every key and keyless (X-Blockmetric-Access: public). Keys of Free accounts get free-tier data (real-time feeds, 30 days of history, heatmap over time for every coin over the last 24 hours, liquidation levels now for every coin, the same as the free web plan); Pro and Desk keys the data of their plan; API Dev / API Pro raise the limits.
- No key
- 24 h
- Free
- 30 days
- Pro
- 365 days
- Desk
- 1095 days
- API Dev
- 365 days
- API Pro
- 1095 days
History window per plan. Limits: Authentication & limits.
Parameters
| Parameter | Description |
|---|---|
coinstring | Only this coin (optional). |
limitinteger | Number of items, default 300, clamped to 1–500.1–500 · default 300 |
fieldsstring | Comma-separated fields of every item to return, e.g. coin,byVenue (case-insensitive). All other fields are left out, so large lists get much smaller; an unknown name answers 400 with the list of fields. Default: every field. |
formatstring | json (default: the { data, meta } envelope) | csv (the rows with a header line; nested values as JSON text) | ndjson (one JSON object per row and line). csv and ndjson carry the meta block in headers: Link rel="next" and X-Blockmetric-Next-Cursor (next page), X-Blockmetric-Next-After (forward polling), X-Blockmetric-Updated-At, X-Blockmetric-Warnings, X-Blockmetric-License. Errors stay JSON.one of json, csv, ndjson · default json |
Response fields
Every success is { data, meta }; these are the fields of data. meta is the same on every endpoint.
| Field | Description |
|---|---|
[].coinstring | Coin name as on Hyperliquid (BTC, kPEPE, HIP-3 names like xyz:TSLA). |
[].byVenueobject | Per venue (hyperliquid, binance, bybit; switched-off venues are missing). |
[].byVenue.hyperliquidobject | - |
[].byVenue.hyperliquid.fundingHourlynumber | Predicted rate per hour, fraction. |
[].byVenue.hyperliquid.fundingAprnumber | Annualised (hourly × 24 × 365), fraction. |
[].byVenue.hyperliquid.intervalHoursnumber | Funding interval of the venue in hours. |
[].byVenue.hyperliquid.nextFundingTimestring (ISO 8601) · nullable | Next funding time of the venue. |
[].byVenue.binanceobject | - |
[].byVenue.binance.fundingHourlynumber | Predicted rate per hour, fraction. |
[].byVenue.binance.fundingAprnumber | Annualised (hourly × 24 × 365), fraction. |
[].byVenue.binance.intervalHoursnumber | Funding interval of the venue in hours. |
[].byVenue.binance.nextFundingTimestring (ISO 8601) · nullable | Next funding time of the venue. |
[].byVenue.bybitobject | - |
[].byVenue.bybit.fundingHourlynumber | Predicted rate per hour, fraction. |
[].byVenue.bybit.fundingAprnumber | Annualised (hourly × 24 × 365), fraction. |
[].byVenue.bybit.intervalHoursnumber | Funding interval of the venue in hours. |
[].byVenue.bybit.nextFundingTimestring (ISO 8601) · nullable | Next funding time of the venue. |
[].updatedAtstring (ISO 8601) | Newest data time of this item (ISO 8601 UTC). |
Errors
- 400
invalid_paramInvalid parameter - 401
unauthorizedMissing or invalid API key - 403
plan_requiredPlan does not include this - 403
scope_requiredKey not scoped for this API - 403
ip_not_allowedAddress not on the IP allowlist of the key - 403
origin_not_allowedKey used from a browser origin it does not allow - 403
source_restrictedExchange data not redistributed - 403
https_requiredhttps required - 429
rate_limitedPer-minute limit reachedretry - 429
daily_limit_exceededDaily limit reachedretry - 429
stream_limitToo many open streamsretry - 500
internal_errorInternal errorretry
Methodology
- Predicted funding (how it is computed and its limits)
Code snippets in these docs are licensed under MIT-0: copy them into your own code without attribution. The SDKs, CLI and MCP server will be, once published, Apache-2.0; the name Blockmetric is not licensed (forks must be renamed). Data from the API is governed by the API terms; third-party exchange data by the exchange’s terms.