Hyperliquid Info API
Available Types (today)
Any other
type value returns {"error":"unsupported_type","type":"<the type you sent>"} with HTTP 400. Requests are not forwarded to upstream Hyperliquid.
Migration Pattern
The GoldRush Hyperliquid Info API is a drop-in replacement for
POST https://api.hyperliquid.xyz/info. The request body, the response shape, and the JSON keys are byte-for-byte identical to the public Hyperliquid API. The only differences are the URL and the authentication header.
Forty-nine wire-compatible type values are supported today across market metadata, user state, user history, vaults, and staking - plus four GoldRush-native types (two batched state lookups and two builder-keyed fill feeds) with no upstream equivalent.
Endpoint
The most-requested reads
Most Hyperliquid apps start from the same REST calls - a user’s trades and their account state. Over the drop-in/info API that is:
- User trades (fills) -
userFillsfor the latest fills, oruserFillsByTimefor a time window (GoldRush serves these past upstream’s ~10,000-fill retention limit). - Perp account state -
clearinghouseStatefor a single wallet, orbatchClearinghouseStatefor up to 50 wallets in one request. - Spot balances -
spotClearinghouseState, orbatchSpotClearinghouseStatefor many wallets at once.
POST /info with a type field - so these are the same requests you already make against api.hyperliquid.xyz, pointed at a faster, unthrottled host.
Comparison with the public Hyperliquid API
Available types
The Info API supports the wire-compatible drop-in types below, organized by what they return. Four GoldRush-native types (batchClearinghouseState, batchSpotClearinghouseState, builderFills, builderFillsByTime) have no upstream Hyperliquid equivalent.
Market metadata
User account state
User history
Vaults & staking
Builder activity
GoldRush-native batch
If you send a
type that isn’t in the table above, the response body is {"error":"unsupported_type","type":""}. Requests are not forwarded to upstream Hyperliquid.
How clients see it
Existing Hyperliquid SDKs work unchanged after abaseUrl override. See SDK compatibility for nomeida/hyperliquid (JS) and hyperliquid-dex/hyperliquid-python-sdk setup snippets.
Errors
Networks
Mainnet only. Testnet support is deferred.Next
Migration guide
Side-by-side examples - change one URL and one header.SDK compatibility
Drop-in setup fornomeida/hyperliquid and hyperliquid-python-sdk.
Limits and caching
No rate limits - what to know about caching and recommended polling cadences.API reference
Per-endpoint request and response schemas.Moving from the public Hyperliquid
/info API to GoldRush is two changes:
- URL - replace
api.hyperliquid.xyz/infowithhypercore.goldrushdata.com/info. - Header - add
Authorization: Bearer.
Side-by-side
cURL
Public Hyperliquid
GoldRush
JavaScript / TypeScript
Public Hyperliquid
GoldRush
Python
Public Hyperliquid
GoldRush
Behavioral notes
Things to be aware of when you cut over.Response is byte-equal, modulo live drift
For implemented types, the response body matches Hyperliquid byte-for-byte - same keys, same nesting, same value types. Numeric fields update independently on each side, so a market-price field will diverge by tens of milliseconds, but the schema is identical.Unsupported types return a JSON error
Types that GoldRush doesn’t natively serve return{"error":"unsupported_type","type":""} with HTTP 400. They are not forwarded to upstream Hyperliquid. See the Info API overview for the current list of supported types.
Auth errors return JSON
A missing or invalid key returns401 with body {"error":"unauthorized"}. Public Hyperliquid has no auth and never returns 401.
Existing SDKs work after a baseUrl override
The two most-used SDKs work unchanged:
nomeida/hyperliquid(JavaScript)hyperliquid-dex/hyperliquid-python-sdk(Python)
Authentication
The Info API uses your standard GoldRush API key. The same key works against the Foundational API. If you don’t have one yet, sign up here. Never hardcode keys in source. Use environment variables or a secrets manager.What you gain
- No rate limits. No 1200 weight/min cap, no per-address throttling, no IP buckets.
- Faster reads. Sub-150 ms p50 target for warm responses; orderbook reads driven from a live WebSocket-fed cache.
- More types. Batched user state, builder-attribution data, liquidation feed, and composites.
- HIP-3 and HIP-4 first-class. Deployer-prefix syntax (
xyz:GOLD-USDC) is supported acrossmetaandmetaAndAssetCtxswhen adexis provided. - One key for everything Hyperliquid. The same API key unlocks HyperEVM via the Foundational API.
The most popular Hyperliquid SDKs work against GoldRush after a one-line
baseUrl override and adding an Authorization header.
JavaScript / TypeScript: nomeida/hyperliquid
Install
npm
yarn
Configure
Note: If your SDK version doesn’t expose aheadersoption, wrapfetchto inject the header globally before instantiating the SDK. See the patch pattern below.
Header injection fallback
Python: hyperliquid-dex/hyperliquid-python-sdk
Install
Configure
Tip: skip_ws=True is recommended when using the Info API only - it skips the WebSocket connection that the SDK opens by default to upstream Hyperliquid.
Verification
After cutover, confirm everything is wired correctly:- Diff a known wallet - call
clearinghouseStatefor the same wallet against both endpoints; the JSON shape (keys, nesting, types) should match exactly. - Confirm auth - remove the API key and confirm you get a
401with body{"error":"unauthorized"}. If you get any other response, your request isn’t reaching GoldRush.
Other SDKs
The pattern is the same for any HTTP client: override the base URL tohttps://hypercore.goldrushdata.com and attach Authorization: Bearer . If you run into a specific SDK that doesn’t expose either knob, email us - we’ll publish a recipe.
Hyperliquid API rate limits
The public Hyperliquid/info API is rate limited to 1200 request weight per minute per IP address. Every /info request carries a weight cost, so heavy usage - polling many wallets, refreshing market state frequently, or running a fleet of workers behind one IP - hits the cap quickly and starts getting throttled.
The GoldRush Hyperliquid Info API removes this limit entirely. It’s a drop-in /info replacement on hypercore.goldrushdata.com/info with byte-for-byte identical request and response shapes, but no per-IP, per-key, or per-address rate limits.
No rate limits with GoldRush
With no weight cap and no per-IP throttling, you can:- Poll any user-state endpoint as fast as your code wants.
- Open as many concurrent connections as your client supports.
- Pull state for thousands of wallets in tight loops.
walletTxs subscription instead - push-based, also no rate limits.
How caching works
Responses are served from a real-time cache that’s kept fresh by direct ingestion from Hyperliquid. The cache is transparent to your client code - same JSON in, same JSON out.Recommended polling cadences
You’re not rate-limited, but polling smartly saves your own bandwidth.Watch out for client-side limits
GoldRush has no rate limits, but the rest of your stack might:- Browser fetch concurrency - most browsers cap at ~6 concurrent requests per host. Use connection pooling on the server side or batch requests.
- HTTP/2 stream limits - most clients allow 100+ concurrent streams per connection by default. Bump if you’re saturating.
- OS file descriptor limits - if you’re opening thousands of connections, raise
ulimit -n.
batchClearinghouseState and batchSpotClearinghouseState endpoints, which accept up to 50 wallets per call. For more than 50 wallets, issue multiple calls.
Network and TLS
- HTTP/2 keep-alive is supported and recommended.
- TLS 1.2+ required.
Accept-Encoding: gzipis honored.zstdsupport is on the roadmap.
Need higher guarantees?
Enterprise SLA, dedicated capacity, regional pinning, and on-prem options are all available. Email sales.Hyperliquid Info API Reference
activeAssetData | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "activeAssetData" is used to fetch a user’s active trading limits, leverage setting, available size, and mark price for a single Hyperliquid perpetual asset.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "activeAssetData", "user": "...", "coin": "ETH"}.
coinaccepts the Hyperliquid asset identifier for the target perp market. For HIP-3 markets, pass the same dex-qualified coin string used by Hyperliquid for that asset.maxTradeSzsandavailableToTradeare returned as two directional decimal-string values. Preserve the upstream array order and use fixed-precision decimal handling.- For whole-account position and margin state, use
clearinghouseState; this endpoint is scoped to one user and one active asset.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single JSON object with the user’s active trading configuration and directional trading capacity for the requested asset.Field descriptions
Note: Prices, sizes, and available amounts are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
metaAndAssetCtxs
fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.spotMetaAndAssetCtxs
fetch the spot universe metadata, token configuration, and live market data in a single call. Last reviewed: 2026-07-08allMids | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "allMids" is used to fetch the current mid price for every actively traded asset in a single call.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "allMids"}.
- The response is a flat map keyed by asset. Perp assets use their symbol (e.g.
BTC); spot pairs are keyed as@using the spot pair index from spotMeta. - The optional
dexfield takes a perp DEX name. It defaults to the empty string, which represents the first (native) perp DEX; pass a HIP-3 dex name to scope mids to that dex. - Mid prices are returned as decimal strings - keep them as strings or use a fixed-precision decimal type rather than parsing as floats.
BTC); spot pairs are keyed as @, using the spot pair index from spotMeta.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A JSON object mapping each asset key to its mid price as a decimal string.Field descriptions
Note: All mid prices are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
batchClearinghouseState | Hyperliquid Info API
Credit Cost: 25 per call Processing: Realtime The Hyperliquid info endpoint withtype: "batchClearinghouseState" is used to fetch perpetuals account state for up to 50 wallets in a single request.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - No upstream equivalent. This endpoint exists only on hypercore.goldrushdata.com. It is not a passthrough.
- Deduplication is case-insensitive. Two addresses that differ only in case (
0xAbC...vs0xabc...) collapse to a single slot in the output, at the position of the first occurrence in the input. - Order preservation. The order of slots in the response matches the order of unique wallets in the input.
- Partial failure is normal. HTTP
200 OKis returned even when individual slots are error envelopes. Always check for theerrorkey on each slot before using its fields. - No cursor or pagination. All requested wallets are fanned out in parallel. For batches larger than 50, issue multiple calls.
- Use cases: portfolio dashboards, multi-wallet PnL aggregators, fleet-level liquidation risk monitoring, copy-trade source-wallet inventory.
/info API is single-wallet, so polling N wallets means N round trips; this endpoint fans them out in parallel against our private node and returns a single combined response.
This is a GoldRush-native extension. There is no equivalent on api.hyperliquid.xyz/info. The wrapped slots return exactly the same shape as Hyperliquid’s native single-wallet clearinghouseState, with a thin per-wallet error envelope when an individual wallet fails.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
i corresponds to the i-th unique wallet in the deduplicated input order. Each element is either:
- The raw upstream Hyperliquid response object for that wallet (success), or
- A slot-level error object (failure for that wallet only, see below).
All success
Example success body forbatchClearinghouseState with 3 wallets: one empty account, one with a single cross-margin position, one with a single isolated-margin position.
Mixed result (one wallet failed)
When a single wallet fails (upstream timeout, transport failure, parse failure, etc.), only its slot is replaced with an error object. The rest of the batch is unaffected. The HTTP status is still200 OK.
Per-wallet error slot
clearinghouseState slot field reference
Each success slot mirrors Hyperliquid’s nativeclearinghouseState response: assetPositions[], crossMarginSummary, marginSummary, crossMaintenanceMarginUsed, time, withdrawable. There is no schema imposition - it’s the raw upstream object.
For full per-field types and notes (including the two leverage shapes and the nullable liquidationPx), see the single-wallet endpoint:
clearinghouseState field reference
Full request and response schema for the single-wallet variant. The batch endpoint returns the same object per slot. For the canonical upstream documentation, see Hyperliquid’s Perpetuals info docs.Related endpoints
batchSpotClearinghouseState
fetch spot account balances for up to 50 wallets in a single request.clearinghouseState
fetch a single user’s perpetuals account state by wallet address.spotClearinghouseState
fetch a single user’s spot account balances by wallet address. Last reviewed: 2026-06-13batchSpotClearinghouseState | Hyperliquid Info API
Credit Cost: 25 per call Processing: Realtime The Hyperliquid info endpoint withtype: "batchSpotClearinghouseState" is used to fetch spot account balances for up to 50 wallets in a single request.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - No upstream equivalent. This endpoint exists only on hypercore.goldrushdata.com. It is not a passthrough.
- Deduplication is case-insensitive. Two addresses that differ only in case collapse to a single slot at the position of the first occurrence in the input.
- Order preservation. Slots in the response are in the order of unique wallets in the input.
- Partial failure is normal. HTTP
200 OKis returned even when individual slots are error envelopes. Always check for theerrorkey on each slot before using its fields. - No cursor or pagination. All requested wallets are fanned out in parallel. For batches larger than 50, issue multiple calls.
- Use cases: token treasury monitoring, holder analytics, balance reconciliation, multi-wallet airdrop eligibility checks.
/info API is single-wallet; this endpoint fans the requests out in parallel against our private node and returns a combined response.
This is a GoldRush-native extension. There is no equivalent on api.hyperliquid.xyz/info. The wrapped slots return exactly the same shape as Hyperliquid’s native single-wallet spotClearinghouseState, with a thin per-wallet error envelope when an individual wallet fails.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
i corresponds to the i-th unique wallet in the deduplicated input order. Each element is either:
- The raw upstream Hyperliquid response object for that wallet (success), or
- A slot-level error object (failure for that wallet only, see below).
All success
Example success body forbatchSpotClearinghouseState with 3 wallets: one empty wallet, one with a single USDC balance, one with multiple tokens including held amounts.
Mixed result (one wallet failed)
When a single wallet fails (upstream timeout, transport failure, parse failure, etc.), only its slot is replaced with an error object. The rest of the batch is unaffected. The HTTP status is still200 OK.
Per-wallet error slot
spotClearinghouseState slot field reference
Each success slot mirrors Hyperliquid’s nativespotClearinghouseState response: balances[] plus the optional tokenToAvailableAfterMaintenance field. There is no schema imposition - it’s the raw upstream object.
The tokenToAvailableAfterMaintenance field is optional and only present when at least one token has a non-zero margin-deduction-aware balance. Wallets without this field can simply ignore it; absence is normal for empty or inactive wallets.
For full per-field types and notes, see the single-wallet endpoint:
spotClearinghouseState field reference
Full request and response schema for the single-wallet variant. The batch endpoint returns the same object per slot. For the canonical upstream documentation, see Hyperliquid’s Spot info docs.Related endpoints
batchClearinghouseState
fetch perpetuals account state for up to 50 wallets in a single request.spotClearinghouseState
fetch a single user’s spot account balances by wallet address.clearinghouseState
fetch a single user’s perpetuals account state by wallet address.spotMeta
fetch the spot universe metadata and full token configuration without live market context. Last reviewed: 2026-05-21builderFillsByTime | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "builderFillsByTime" is used to fetch a builder’s attributed trade fills within a time window for revenue attribution and fee accounting.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native: NoPOST api.hyperliquid.xyz/infoequivalent. Available only viaPOST hypercore.goldrushdata.com/info.
- Each response contains at most 2,000 fills; widen the window in chunks or page by advancing
startTimeif you need more. - GoldRush serves this
typefrom a dedicated HyperCore historical store, so windows can extend back to GoldRush’s full HyperCore coverage. - Use
builderFills(noTimesuffix) when you only need the most recent N fills without specifying a window.
[startTime, endTime] window in milliseconds. Use this for builder revenue reports, monthly fee reconciliation, or rebuilding historical builder order-flow.
Builder-keyed. GoldRush-native as there is no upstream Hyperliquid /info equivalent. Served from a dedicated HyperCore historical store, so windows can extend back to GoldRush’s full HyperCore coverage.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of fill objects ordered bytime. Each entry is a fill from an order that was routed through the builder address within the window.
Field descriptions
Note: All numeric fields (px,sz,startPosition,closedPnl,fee,builderFee) are returned as decimal strings with full upstream precision (up to 18 decimal places). Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
builderFills
fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.userTwapSliceFillsByTime
fetch a user’s TWAP slice fills within a time window for execution-quality reconciliation on algorithmic…userFills
fetch a user’s most recent trade fills without specifying a time window. Last reviewed: 2026-06-16builderFills | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "builderFills" is used to fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native: NoPOST api.hyperliquid.xyz/infoequivalent. Available only viaPOST hypercore.goldrushdata.com/info.
- Each response contains at most 2,000 fills, ordered most-recent first.
- For windowed queries for revenue reports and monthly reconciliation, use
builderFillsByTime.
/info equivalent.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of fill objects ordered most-recent-first. Each entry is a fill from an order that was routed through the builder address.Field descriptions
Note: All numeric fields (px,sz,startPosition,closedPnl,fee,builderFee) are returned as decimal strings with full upstream precision (up to 18 decimal places). Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
builderFillsByTime
fetch a builder’s attributed trade fills within a time window for revenue attribution and fee accounting.userFills
fetch a user’s most recent trade fills without specifying a time window.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.userTwapSliceFills
fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders. Last reviewed: 2026-06-16candleSnapshot | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "candleSnapshot" is used to fetch historical OHLCV candles for a coin and interval over a time window for charting and backtesting.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "candleSnapshot", "req": {...}}. Note the nestedreqobject.
- Each response contains at most 5,000 candles (per-response cap, not a retention limit); page by advancing
startTimefor longer ranges. - GoldRush serves candles from a dedicated HyperCore historical store, so candles older than the upstream window can extend back to GoldRush’s full HyperCore coverage.
[startTime, endTime] window. Each candle carries the open/close timestamps, the coin, the interval, open/high/low/close prices, base volume, and trade count. Use it for chart backfills, indicator computation, and backtests.
This is a global, non-user-keyed type. NOT LIMITED TO THE MOST RECENT 5,000 CANDLES. GoldRush serves it from a dedicated HyperCore historical store so candles older than the upstream window remain available; page through time by advancing startTime.
Endpoint
Request
The request parameters are nested inside areq object.
Example
cURL
TypeScript
Python
Response
An array of candle objects, oldest first.Field descriptions
Note: The price and volume fields (o,c,h,l,v) are returned as decimal strings, preserving upstream precision. Do not parse them as floats.
Paginating a large backfill
Each response returns at most 5,000 candles - a per-response cap, not a limit on how far back history goes. To backfill a range wider than 5,000 candles, page forward through time: start at your window’sstartTime, then set the next request’s startTime to the last candle’s close time (T) plus one millisecond. Repeat until a response returns fewer than 5,000 candles.
Because T is the inclusive close of a candle and the next candle opens at T + 1, advancing to T + 1 lands exactly on the following candle - no overlap to de-duplicate and no gaps.
TypeScript
TypeScript
Python
Response
Field descriptions
Note: All numeric fields below (account value, position size, prices, funding amounts, etc.) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
batchClearinghouseState
fetch perpetuals account state for up to 50 wallets in a single request.batchSpotClearinghouseState
fetch spot account balances for up to 50 wallets in a single request.spotClearinghouseState
fetch a single user’s spot account balances by wallet address. Last reviewed: 2026-07-07delegations | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "delegations" is used to list a user’s active HYPE staking delegations.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "delegations", "user": "..."}.
- Returns an empty array when the user has no active delegations.
- For staking totals use
delegatorSummary; for the delegate / undelegate event history behind them, usedelegatorHistory.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of delegation objects, one per validator. Empty when the user has no active delegations.Field descriptions
Note: amount is returned as a decimal string, preserving upstream precision. Do not parse it as a float.
Last reviewed: 2026-07-24
delegatorHistory | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "delegatorHistory" is used to reconstruct the sequence of HYPE staking events behind the totals shown in delegatorSummary.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "delegatorHistory", "user": "..."}.
- For totals (delegated, undelegated, pending withdrawal sums), use
delegatorSummary. - For accrued staking and commission rewards, use
delegatorRewards.
time. Use this to reconstruct the sequence behind the totals shown in delegatorSummary.
User-keyed. Each entry carries a delta whose discriminator describes the event variant.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of staking event objects.Field descriptions
Note: delta.delegate.amount is returned as a decimal string, preserving upstream precision. Do not parse it as a float.
Related endpoints
delegatorRewards
fetch a user’s current HYPE staking position.delegatorSummary
get a one-shot snapshot of a user’s HYPE staking position for dashboards and portfolio overviews.fundingHistory
fetch a coin’s historical funding rates and premiums over a time window for funding analytics and basis… Last reviewed: 2026-06-13delegatorRewards | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "delegatorRewards" is used to fetch a user’s current HYPE staking position.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "delegatorSummary", "user": "..."}.
- For the sequence of delegation events behind these totals, use
delegatorHistory. - For accrued staking and commission rewards, use
delegatorRewards.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of reward entries.Field descriptions
Note: totalAmount is returned as a decimal string, preserving upstream precision. Do not parse it as a float.
Related endpoints
delegatorHistory
reconstruct the sequence of HYPE staking events behind the totals shown in delegatorSummary.delegatorSummary
get a one-shot snapshot of a user’s HYPE staking position for dashboards and portfolio overviews. Last reviewed: 2026-06-13delegatorSummary | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "delegatorSummary" is used to get a one-shot snapshot of a user’s HYPE staking position for dashboards and portfolio overviews.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "delegatorSummary", "user": "..."}.
- For the sequence of delegation events behind these totals, use
delegatorHistory. - For accrued staking and commission rewards, use
delegatorRewards.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
Field descriptions
Note:delegated,undelegated, andtotalPendingWithdrawalare returned as decimal strings. Do not parse them as floats.
Related endpoints
delegatorHistory
reconstruct the sequence of HYPE staking events behind the totals shown in delegatorSummary.delegatorRewards
fetch a user’s current HYPE staking position. Last reviewed: 2026-06-13exchangeStatus | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "exchangeStatus" is used to fetch the current exchange operational status.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "exchangeStatus"}.
specialStatusesisnullunder normal operation and carries status flags only when the exchange is in a special state.- This is a global, non-user-keyed type;
timereflects the exchange’s current clock.
specialStatuses is null; a non-null value signals that the exchange is in a special state. The time field is the exchange’s current timestamp, useful for detecting clock skew or a stalled feed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object describing the exchange status.Field descriptions
Last reviewed: 2026-07-24
extraAgents | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "extraAgents" is used to list a user’s approved API-agent wallets.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "extraAgents", "user": "..."}.
- Returns an empty array when the user has approved no agent wallets.
- Each agent’s
validUntilis a millisecond timestamp after which the API wallet’s approval expires.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of agent-wallet objects. Empty when the user has approved no agents.Field descriptions
Last reviewed: 2026-07-24
frontendOpenOrders | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "frontendOpenOrders" is used to fetch a user’s currently open orders enriched with frontend metadata.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "frontendOpenOrders", "user": "..."}.
- Use
frontendOpenOrdersinstead ofopenOrderswhen you need the trigger metadata and human-readable order type - exactly what the Hyperliquid web UI displays.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of open orders. Each order object includes the standardopenOrders fields plus the frontend* enrichment fields.
Field descriptions
Last reviewed: 2026-06-13
fundingHistory | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "fundingHistory" is used to fetch a coin’s historical funding rates and premiums over a time window for funding analytics and basis strategies.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "fundingHistory", "coin": "..."}.
- Each response contains at most 500 entries per call.
- This is market-wide funding history for a coin. For a single wallet’s actual funding payments, use userFunding instead.
- For the current funding rate alongside live market context, use metaAndAssetCtxs.
[startTime, endTime] window. Each entry carries the funding rate that was applied and the mark-vs-oracle premium at that time. Use it for funding-rate charts, basis/carry analytics, and historical funding P&L modeling.
This is a global, non-user-keyed type. Page through time by advancing startTime.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of funding-interval objects, oldest first.Field descriptions
Note:fundingRateandpremiumare returned as decimal strings, preserving upstream precision. Do not parse them as floats.
Related endpoints
delegatorHistory
reconstruct the sequence of HYPE staking events behind the totals shown in delegatorSummary.userFunding
fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.userNonFundingLedgerUpdates
fetch a user’s non-funding USDC ledger history (deposits, withdrawals, transfers, vault flows) within a time… Last reviewed: 2026-06-13l2Book | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "l2Book" is used to fetch an aggregated Level-2 order book snapshot for a single coin - bids and asks as price, size, and order-count levels.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "l2Book", "coin": "..."}.
- Returns at most 20 levels per side.
- For a continuous push stream instead of polling snapshots, subscribe to the WebSocket API
l2Bookchannel (optional wildcardcoin) or the GoldRush-nativel2BookDifffor incremental updates.
coin: two arrays of price levels (bids first, then asks), each level carrying the price, the total resting size at that price, and the number of orders comprising it. Use it for a one-shot depth snapshot, spread checks, or seeding a book before switching to a diff stream.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single JSON object.levels is a two-element array: element 0 is the bid side (descending price), element 1 is the ask side (ascending price). Each level is a {px, sz, n} object.
Field descriptions
Note:pxandszare returned as decimal strings, preserving upstream precision. Do not parse them as floats.
Last reviewed: 2026-06-16
leadingVaults | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "leadingVaults" is used to list the vaults a user leads.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "leadingVaults", "user": "..."}.
- Returns one entry per vault the user leads (manages); the array is empty when the user leads none.
- Each entry gives the vault’s address and name; use vaultDetails for the full breakdown.
- User-keyed by the leader address.
{vaultAddress, name} entries. The array is empty when the user does not lead any vault.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of vaults the user leads. Empty when the user leads none.Field descriptions
Last reviewed: 2026-07-24
liquidatable | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "liquidatable" is used to list accounts currently eligible for liquidation.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "liquidatable"}.
- Global, non-user-keyed: it takes no
userfield and returns the accounts that are liquidatable at the instant of the call. - The array is frequently empty - eligible accounts are typically liquidated the moment they cross the threshold, so a point-in-time snapshot rarely catches an open candidate.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of liquidatable-account entries. The array is empty when no account is currently eligible for liquidation, which is the common case.Field descriptions
Note: Upstream Hyperliquid does not publish a stable, fully-specified per-entry schema for liquidatable, and the result is empty in the vast majority of calls. When the array is non-empty, each entry identifies an at-risk account by its wallet address; treat any additional per-entry fields defensively.
Last reviewed: 2026-07-24
marginTable | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "marginTable" is used to fetch the margin-tier (leverage-bracket) table for a given margin table id.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "marginTable", "id": ...}.
idis themarginTableIdreferenced by a meta universe entry (universe[].marginTableId), also listed inline inmeta.marginTables.marginTiersdescribes how the maximum leverage steps down as a position’s notional grows.
meta.marginTables.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object describing the table’s description and its ordered leverage tiers.Field descriptions
Last reviewed: 2026-07-24
maxBuilderFee | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "maxBuilderFee" is used to fetch the maximum builder fee a user has approved for a given builder.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "maxBuilderFee", "user": "...", "builder": "..."}.
- The response is a bare integer in tenths of a basis point (e.g.
10= 1 basis point = 0.01%). - Returns
0when the user has not approved any builder fee for that builder.
0 means no approval is in place for that builder.
User-keyed (and scoped to a single builder).
Endpoint
Request
Example
cURL
TypeScript
Python
Response
The body is a bare integer - the approved ceiling in tenths of a basis point.Field descriptions
Last reviewed: 2026-07-24
maxMarketOrderNtls | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "maxMarketOrderNtls" is used to fetch the maximum market-order notional for each leverage bucket.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "maxMarketOrderNtls"}.
- Each entry is a
[leverage, maxNotionalUsd]tuple; the notional is a decimal string. - This is a global, non-user-keyed type. Buckets are ordered from highest leverage to lowest.
[maxLeverage, maxNotional] tuple: a position running at up to maxLeverage may place a single market order of at most maxNotional USD. The cap tightens as leverage rises, bounding slippage on aggressive market orders.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of[maxLeverage, maxNotional] tuples, ordered from highest leverage to lowest.
Field descriptions
Note: The notional value in each tuple is returned as a decimal string, preserving upstream precision. Do not parse it as a float - keep it as a string or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
metaAndAssetCtxs | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "metaAndAssetCtxs" is used to fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toReturns a tuplePOST api.hyperliquid.xyz/infowith{"type": "metaAndAssetCtxs"}.
[meta, assetCtxs[]] covering the entire Hyperliquid perpetuals universe - every coin’s metadata plus a live snapshot of mark price, funding rate, open interest, and 24-hour volume.
This is a global, non-user-keyed type. A single cache entry is shared across all callers and is refreshed continuously from upstream Hyperliquid.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A two-element JSON array. Element 0 is the universe metadata; element 1 is an array of per-asset contexts indexed identically to theuniverse array.
Element 0: meta
Element 1: assetCtxs[]
Array of per-asset live context, indexed identically to universe.
Related endpoints
spotMetaAndAssetCtxs
fetch the spot universe metadata, token configuration, and live market data in a single call.activeAssetData
fetch a user’s active trading limits, leverage setting, available size, and mark price for a single…meta
fetch the perpetuals universe metadata without live market context.outcomeMeta
enumerate all active HIP-4 binary outcome markets on HyperCore. Last reviewed: 2026-06-13meta | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "meta" is used to fetch the perpetuals universe metadata without live market context.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "meta"}.
- Use metaAndAssetCtxs when you also need live per-asset mark price, funding, open interest, and day volume.
- The optional
dexfield takes a perp DEX name. It defaults to the empty string which represents the first perp DEX. - For the spot equivalent, use spotMeta.
metaAndAssetCtxs, this payload carries no live market data, so it is cheap to cache and changes only when listings or margin parameters change.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single JSON object describing the perp universe, the margin-tier tables it references, and the collateral token.Field descriptions
Related endpoints
metaAndAssetCtxs
fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.outcomeMeta
enumerate all active HIP-4 binary outcome markets on HyperCore.spotMeta
fetch the spot universe metadata and full token configuration without live market context.spotMetaAndAssetCtxs
fetch the spot universe metadata, token configuration, and live market data in a single call. Last reviewed: 2026-06-13openOrders | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "openOrders" is used to list a user’s resting open orders.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "openOrders", "user": "..."}.
- For orders enriched with trigger metadata, TP/SL flags, and the human-readable order type shown in the Hyperliquid web UI, use
frontendOpenOrdersinstead. - The optional
dexfield scopes the query to a HIP-3 builder DEX; the empty string (default) returns orders on the canonical Hyperliquid perp DEX. - For a real-time stream of order placement and cancellation events, subscribe to
walletTxs.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of open-order objects. Empty when the user has no resting orders.Field descriptions
Note:limitPx,sz, andorigSzare returned as decimal strings, preserving upstream precision. Do not parse them as floats.
Last reviewed: 2026-07-24
outcomeMeta | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "outcomeMeta" is used to enumerate all active HIP-4 binary outcome markets on HyperCore.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "outcomeMeta"}.
- For real-time price updates on a discovered outcome, subscribe to ohlcvCandlesForPair using the per-side encoding. See the HIP-4 markets recipe for end-to-end discovery and streaming patterns.
- HIP-4 launched on Hyperliquid mainnet on May 2, 2026. Read the canonical spec: HIP-4: Outcome markets.
outcome ID, human-readable name, structured description, and sideSpecs (Yes / No).
This is a global, non-user-keyed type. A single cache entry is shared across all callers and is refreshed continuously from upstream Hyperliquid.
outcomeMeta is HIP-4’s dedicated metadata type - separate from metaAndAssetCtxs, which covers perps and spot. Use it to discover live outcome IDs and compute per-side market encodings (encoding = 10 * outcome + side) before subscribing to OHLCV or fills.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
Field descriptions
Related endpoints
meta
fetch the perpetuals universe metadata without live market context.metaAndAssetCtxs
fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.settledOutcome
retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.spotMeta
fetch the spot universe metadata and full token configuration without live market context. Last reviewed: 2026-06-13perpDeployAuctionStatus | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "perpDeployAuctionStatus" is used to fetch the current perp-deploy Dutch-auction status.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "perpDeployAuctionStatus"}.
- Describes the current perp-deploy (HIP-3) Dutch auction: the gas price decays over
durationSecondsfromstartGas, andcurrentGasis the live price a deployer would pay now. currentGasisnullonce the auction has ended;endGasisnullwhile the auction is still active.- Gas prices are decimal strings. This is a global, non-user-keyed type.
startGas. currentGas is the live price; it becomes null after the auction ends, at which point endGas records the final price.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object describing the current perp-deploy gas auction.Field descriptions
Note: Gas prices are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
perpDexLimits | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "perpDexLimits" is used to fetch the open-interest, position-size, and transfer limits for a HIP-3 perp DEX.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "perpDexLimits", "dex": "..."}.
- The
dexfield names the HIP-3 builder-deployed perp DEX to inspect. Enumerate deployed DEX names with perpDexs. - Returns
nullfor a DEX that has no configured limits (including the empty-string native perp DEX). coinToOiCapis an array of[coin, cap]tuples; all limit values are decimal strings.
name from perpDexs as the dex field to inspect that DEX’s limits.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object describing the DEX’s limits, ornull when the DEX has no configured limits.
Field descriptions
Note: All limit values are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
perpDexs | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "perpDexs" is used to enumerate every HIP-3 builder-deployed perpetual DEX on HyperCore.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "perpDexs"}.
- The
nullat index0represents the canonical Hyperliquid perp DEX; use meta or metaAndAssetCtxs with the defaultdex: ""to query its universe. - Pass a builder DEX
namefrom this list as thedexfield on meta or metaAndAssetCtxs to fetch a specific HIP-3 perp universe. assetToStreamingOiCapandassetToFundingMultiplierare[coin, value]tuple arrays scoped to that DEX.
0 is null and represents the canonical Hyperliquid perp universe; each subsequent entry is a HIP-3 builder-deployed perp DEX, exposing its short name, full name, deployer address, oracle updater, fee recipient, per-asset streaming open-interest caps, and per-asset funding-rate multipliers.
This is a global, non-user-keyed type. A single cache entry is shared across all callers and is refreshed as new HIP-3 DEXes are deployed or their parameters change.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of perpetual DEX entries. Index0 is null and represents the canonical Hyperliquid perp universe (query it via meta / metaAndAssetCtxs with the default empty dex field). Each subsequent element is a HIP-3 builder-deployed perp DEX.
Field descriptions
Last reviewed: 2026-07-07
perpsAtOpenInterestCap | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "perpsAtOpenInterestCap" is used to list the perp assets currently at their open-interest cap.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "perpsAtOpenInterestCap"}.
- While an asset is in this list it has reached its open-interest cap; orders that would increase aggregate open interest are rejected (see the
openInterestCap*order-rejection reasons) until open interest falls back below the cap. - This is a global, non-user-keyed type refreshed continuously from upstream Hyperliquid.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of coin symbol strings for the perp assets currently at their open-interest cap. Empty when no market is capped.Field descriptions
Last reviewed: 2026-07-24
settledOutcome | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "settledOutcome" is used to retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toReturns the on-chain settlement data for a single settled HIP-4 outcome: the integer outcome ID, the resolved side, the resolution price, and the settlement timestamp. Use this once an outcome has resolved to confirm which side paid out and reconcile against your own books.POST api.hyperliquid.xyz/infowith{"type": "settledOutcome", "outcome": }.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
question object:
Field descriptions
Note: settleFraction is returned as a decimal string with full upstream precision. Do not parse it as a float - keep it as a string or use a fixed-precision decimal type.
Related endpoints
outcomeMeta
enumerate all active HIP-4 binary outcome markets on HyperCore. Last reviewed: 2026-06-19spotClearinghouseState | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "spotClearinghouseState" is used to fetch a single user’s spot account balances by wallet address.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "spotClearinghouseState", "user": "..."}.
- USDC balance is returned as
token: 0.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
Field descriptions
Note: All numeric balance fields (total,hold,entryNtl) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
batchSpotClearinghouseState
fetch spot account balances for up to 50 wallets in a single request.batchClearinghouseState
fetch perpetuals account state for up to 50 wallets in a single request.clearinghouseState
fetch a single user’s perpetuals account state by wallet address.spotMeta
fetch the spot universe metadata and full token configuration without live market context. Last reviewed: 2026-06-13spotDeployState | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "spotDeployState" is used to fetch the spot-token deployment state and gas auction for a deployer.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "spotDeployState", "user": "..."}.
stateslists the deployer’s in-progress spot-token deployments; it is empty for auserwith no active deployment.gasAuctiondescribes the current spot-deploy Dutch gas auction, with gas prices returned as decimal strings.- User-keyed by the deployer address.
states) plus the current spot-deploy gas auction (gasAuction). Use it to track a deployer’s genesis configuration and the live gas price required to deploy a spot token.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object with the deployer’s in-progress deployments and the current gas auction.states is empty when the deployer has no active spot deployment.
Field descriptions
Note: Gas prices and genesis balances are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
spotMetaAndAssetCtxs | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "spotMetaAndAssetCtxs" is used to fetch the spot universe metadata, token configuration, and live market data in a single call.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "spotMetaAndAssetCtxs"}.
- For perp universe + live contexts, use
metaAndAssetCtxsinstead.
[spotMeta, assetCtxs[]] covering the entire Hyperliquid spot universe - every pair’s universe entry, every token’s metadata, and a live snapshot of mark price, mid price, prior-day price, and 24-hour notional volume per pair.
This is the spot counterpart of metaAndAssetCtxs. Global, non-user-keyed; a single cache entry is shared across all callers and refreshed continuously from upstream Hyperliquid.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A two-element JSON array. Element 0 is the spot universe and token metadata; element 1 is an array of per-pair live contexts indexed identically to element 0’suniverse.
Element 0: spotMeta
Element 1: assetCtxs[]
Array of per-pair live context, indexed identically to universe.
Note: All numeric fields below are returned as decimal strings. Do not parse them as floats.
Related endpoints
metaAndAssetCtxs
fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.spotMeta
fetch the spot universe metadata and full token configuration without live market context.activeAssetData
fetch a user’s active trading limits, leverage setting, available size, and mark price for a single…batchSpotClearinghouseState
fetch spot account balances for up to 50 wallets in a single request. Last reviewed: 2026-06-13spotMeta | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "spotMeta" is used to fetch the spot universe metadata and full token configuration without live market context.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "spotMeta"}.
- Use spotMetaAndAssetCtxs when you also need live per-pair mark price, mid, and day volume.
- For the perpetuals equivalent, use meta.
universe) and the full token registry (tokens) with each token’s decimals, on-chain identifier, and linked HyperEVM contract. Carries no live market data, so it is cheap to cache and changes only when new tokens or pairs are listed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single JSON object with two arrays:tokens (the token registry) and universe (the tradeable pairs that reference those tokens by index).
tokens[]
universe[]
Related endpoints
spotMetaAndAssetCtxs
fetch the spot universe metadata, token configuration, and live market data in a single call.batchSpotClearinghouseState
fetch spot account balances for up to 50 wallets in a single request.meta
fetch the perpetuals universe metadata without live market context.metaAndAssetCtxs
fetch the full Hyperliquid perpetuals market universe with live per-asset trading context. Last reviewed: 2026-06-13subAccounts | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "subAccounts" is used to fetch a master wallet’s sub-accounts along with their full perp and spot state in a single call.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "subAccounts", "user": "..."}.
- For multi-wallet polling without traversing master/sub-account hierarchy, see
batchClearinghouseStateandbatchSpotClearinghouseState.
null for wallets that aren’t master accounts.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of sub-account objects, ornull if the queried wallet is not a master account.
Field descriptions
Last reviewed: 2026-06-13
userAbstraction | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userAbstraction" is used to fetch a user’s account-abstraction mode.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userAbstraction", "user": "..."}.
- The response body is a bare JSON string (for example
"disabled"), not an object - parse it as a scalar. - Values seen in production are
disabledandunifiedAccount; the wider native enum also includesportfolioMargin,default, and the legacydexAbstraction.
disabled means the account keeps separate perp and spot balances, while unifiedAccount means a single balance per asset is shared across all DEXes with cross-margin positions sharing collateral.
User-keyed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
The body is a bare JSON string - not an object - naming the account-abstraction mode.Field descriptions
Last reviewed: 2026-07-24
userBorrowLendInterest | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userBorrowLendInterest" is used to fetch a user’s borrow/lend interest accrual history.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userBorrowLendInterest", "user": "...", "startTime": ...}.
- Bounded by a
[startTime, endTime)window in milliseconds;endTimedefaults to the current server time when omitted. - Amounts are decimal strings, one row per token per accrual point.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of per-token interest accrual points within the window. Empty when the user accrued no borrow/lend interest over the range.Field descriptions
Note:borrowandsupplyare returned as decimal strings, preserving upstream precision. Do not parse them as floats.
Last reviewed: 2026-07-24
userFees | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userFees" is used to fetch a user’s fee schedule and recent daily volume.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userFees", "user": "..."}.
feeScheduleis the exchange-wide tier table;userCrossRate/userAddRateare the effective rates this user pays after VIP-tier, referral, and staking discounts.- All rate and volume fields are decimal strings; a rate of
"0.00045"means 4.5 basis points.
cross) and maker (add) rates a wallet actually pays, and to reconstruct the tier table and discounts that produce them.
User-keyed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object with the user’s recent daily volume, the exchange-widefeeSchedule, the user’s effective rates, and any active discounts / trial state.
Field descriptions
Note: All rate and volume fields (userCross,userAdd,exchange,cross,add,userCrossRate,userAddRate, and the tier / discount values) are returned as decimal strings. Do not parse them as floats. Rates are expressed as fractions of notional -"0.00045"= 4.5 bps.
Last reviewed: 2026-07-24
userFillsByTime | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userFillsByTime" is used to fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userFillsByTime", "user": "...", "startTime": ...}.
- Each response contains at most 2,000 fills; widen the window in chunks or page by advancing
startTimeif you need more. - GoldRush serves this
typefrom a dedicated HyperCore historical store, so windows older than upstream Hyperliquid’s 10,000-fill retention are still fulfilled. - Use
userFills(noTimesuffix) when you only need the most recent N fills without specifying a window.
[startTime, endTime) window in milliseconds. Use this when you want fills since a specific moment - daily P&L recaps, post-deploy backfills, or rebuilding a tax ledger - rather than the most recent N fills.
User-keyed. The upstream Hyperliquid API caps each response at 2,000 fills; page by advancing startTime. NOT LIMITED TO THE 10,000 MOST RECENT FILLS. GoldRush serves this type from a dedicated HyperCore historical store so windows extending past the upstream retention limit are fulfilled from GoldRush data rather than truncated.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of fill objects ordered bytime.
Field descriptions
Note: All numeric fields (px,sz,startPosition,closedPnl,fee,builderFee) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userTwapSliceFillsByTime
fetch a user’s TWAP slice fills within a time window for execution-quality reconciliation on algorithmic…builderFillsByTime
fetch a builder’s attributed trade fills within a time window for revenue attribution and fee accounting.userFills
fetch a user’s most recent trade fills without specifying a time window.userTwapSliceFills
fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders. Last reviewed: 2026-06-16userFills | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userFills" is used to fetch a user’s most recent trade fills without specifying a time window.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userFills", "user": "..."}.
- Each response contains at most 2,000 fills.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of fill objects ordered most-recent-first.Field descriptions
Note: All numeric fields (px,sz,startPosition,closedPnl,fee,builderFee) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.userTwapSliceFills
fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders.userTwapSliceFillsByTime
fetch a user’s TWAP slice fills within a time window for execution-quality reconciliation on algorithmic…builderFills
fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics. Last reviewed: 2026-06-13userFunding | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userFunding" is used to fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userFunding", "user": "..."}.
- Use
userNonFundingLedgerUpdatesfor deposits, withdrawals, transfers, vault flows, liquidations, and other balance-moving events.
[startTime, endTime) window. Each entry is one funding application: a coin, the rate that was applied, the position size at the time, and the resulting USDC delta (negative = paid, positive = received).
User-keyed. Use this for funding-only P&L attribution; use userNonFundingLedgerUpdates for everything else.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of funding event objects, one per applied funding interval and coin.Field descriptions
Note: All numeric delta fields are returned as decimal strings. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userNonFundingLedgerUpdates
fetch a user’s non-funding USDC ledger history (deposits, withdrawals, transfers, vault flows) within a time…fundingHistory
fetch a coin’s historical funding rates and premiums over a time window for funding analytics and basis…userFills
fetch a user’s most recent trade fills without specifying a time window.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction. Last reviewed: 2026-06-13userNonFundingLedgerUpdates | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userNonFundingLedgerUpdates" is used to fetch a user’s non-funding USDC ledger history (deposits, withdrawals, transfers, vault flows) within a time window.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userNonFundingLedgerUpdates", "user": "..."}.
- Funding payments are not included here - use
userFunding.
delta whose type discriminates the event variant - deposits, withdrawals, internal transfers, sub-account transfers, vault flows, liquidations, rewards claims, and similar.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of ledger event objects. Each entry hastime, hash, and a delta discriminated by delta.type.
Field descriptions
Note: All numeric delta fields are returned as decimal strings. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userFunding
fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.fundingHistory
fetch a coin’s historical funding rates and premiums over a time window for funding analytics and basis…userFills
fetch a user’s most recent trade fills without specifying a time window.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction. Last reviewed: 2026-06-17userRateLimit | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userRateLimit" is used to fetch a user’s API rate-limit usage and cap.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userRateLimit", "user": "..."}.
- This reports Hyperliquid’s own address-based L1 request allowance; it is unrelated to your GoldRush credit budget.
- The request cap (
nRequestsCap) is a function of the account’s cumulative traded volume (cumVlm), so higher-volume accounts are granted more requests.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
Field descriptions
Note: cumVlm is returned as a decimal string. Do not parse it as a float.
Last reviewed: 2026-07-24
userRole | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userRole" is used to fetch a user’s account role.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userRole", "user": "..."}.
- The
rolevalue is one ofmissing,user,agent,vault, orsubAccount. - The
subAccountandagentroles additionally carry adataobject identifying the controlling master account.
user accounts; this type also distinguishes API agent wallets, vault addresses, and subAccounts. For a subAccount (and for an agent), a nested data object carries the master account address that controls the wallet.
User-keyed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object with arole discriminator. A plain trading wallet returns {"role": "user"}; a sub-account additionally returns its controlling master under data.
Field descriptions
Last reviewed: 2026-07-24
userToMultiSigSigners | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userToMultiSigSigners" is used to fetch the authorized signers for a multi-sig user.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userToMultiSigSigners", "user": "..."}.
- Returns
nullwhen the queried wallet is not a multi-sig account. - A multi-sig account has at most 10 authorized signers;
thresholdis the minimum number that must sign to authorize an action.
threshold) required to authorize an action. Returns null for ordinary (non-multi-sig) wallets.
User-keyed.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An object describing the multi-sig signer set, ornull when the queried wallet is not a multi-sig account.
Field descriptions
Last reviewed: 2026-07-24
userTwapSliceFillsByTime | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userTwapSliceFillsByTime" is used to fetch a user’s TWAP slice fills within a time window for execution-quality reconciliation on algorithmic orders.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userTwapSliceFillsByTime", "user": "...", "startTime": ...}.
- Each response contains at most 2,000 slice fills; widen the window in chunks or page by advancing
startTimeif you need more. - GoldRush serves this
typefrom a dedicated HyperCore historical store, so windows older than upstream Hyperliquid’s 10,000-fill retention are still fulfilled. - TWAP slice fills have a
hashof all zeros - use that, or the presence oftwapId, to distinguish them from regular fills. - Use
userTwapSliceFills(noByTimesuffix) when you only need the most recent N slice fills without specifying a window.
**startTime, endTime) window in milliseconds. Each entry is a {fill, twapId} pair, where twapId ties the slice back to its parent TWAP order. Use this when you want execution-quality data for TWAP orders within a specific window - daily slice recaps, post-deploy backfills, or reconciling realized TWAP execution against benchmarks.
User-keyed. The upstream Hyperliquid API caps each response at 2,000 slice fills; page by advancing startTime. NOT LIMITED TO THE 10,000 MOST RECENT FILLS. GoldRush serves this type from a dedicated HyperCore historical store so windows extending past the upstream retention limit are fulfilled from GoldRush data rather than truncated.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of TWAP slice fill objects ordered bytime.
Field descriptions
Note: All numericfillfields (px,sz,startPosition,closedPnl,fee) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userTwapSliceFills
fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.builderFillsByTime
fetch a builder’s attributed trade fills within a time window for revenue attribution and fee accounting.userFills
fetch a user’s most recent trade fills without specifying a time window. Last reviewed: 2026-06-19userTwapSliceFills | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userTwapSliceFills" is used to fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "userTwapSliceFills", "user": "..."}.
- Each response contains at most 2,000 most recent TWAP slice fills. Older slices beyond that window are not retrievable from this endpoint.
- TWAP slice fills have a
hashof all zeros - use that, or the presence oftwapId, to distinguish them from regular fills. - Use
userFillsByTimewhen you want all fills (regular + TWAP slices) for a wallet within a time window; each TWAP slice there carries the sametwapIdfield.
{fill, twapId} pair, where twapId ties the slice back to its parent TWAP order. Multiple slices from the same TWAP share the same twapId.
User-keyed. Use this when you want execution-quality data for TWAP orders specifically - slippage per slice, fills-per-TWAP, realized average price - rather than the unified fills feed from userFillsByTime.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of TWAP slice fill objects, most recent first.Field descriptions
Note: All numericfillfields (px,sz,startPosition,closedPnl,fee) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
Related endpoints
userTwapSliceFillsByTime
fetch a user’s TWAP slice fills within a time window for execution-quality reconciliation on algorithmic…userFills
fetch a user’s most recent trade fills without specifying a time window.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.builderFills
fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics. Last reviewed: 2026-06-13userVaultEquities | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "userVaultEquities" is used to fetch a user’s locked vault equity positions across all vaults they have deposited into.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toReturns the wallet’s per-vault equity: one entry per vault the user has deposited into, with the locked amount and the timestamp at which that equity becomes unlockable. User-keyed. The result isPOST api.hyperliquid.xyz/infowith{"type": "userVaultEquities", "user": "..."}.
[] for wallets that haven’t deposited into any vault.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of vault equity entries.Field descriptions
Note: equity is returned as a decimal string, preserving upstream precision. Do not parse it as a float - keep it as a string or use a fixed-precision decimal type.
Related endpoints
userFills
fetch a user’s most recent trade fills without specifying a time window.userFillsByTime
fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.userFunding
fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.userNonFundingLedgerUpdates
fetch a user’s non-funding USDC ledger history (deposits, withdrawals, transfers, vault flows) within a time… Last reviewed: 2026-06-13validatorL1Votes | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "validatorL1Votes" is used to fetch the pending validator L1 governance votes/actions.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "validatorL1Votes"}.
- Each entry is an L1 governance action currently awaiting validator votes, with an
expireTime(ms) after which the pending vote lapses. - The
actionobject is a tagged variant; its inner shape depends on the specific L1 action being voted on (the example below shows asettleOutcomeaction). - This is a global, non-user-keyed type.
expireTime with the action under vote.
The action is a tagged variant whose inner structure depends on the action type, so treat it as an opaque object keyed by action tag unless you are decoding a specific action you recognize.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of pending L1 action votes. Empty when no L1 action is awaiting votes.Field descriptions
Last reviewed: 2026-07-24
vaultDetails | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "vaultDetails" is used to fetch detailed information for a specific vault.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "vaultDetails", "vaultAddress": "..."}.
vaultAddressis required; the optionaluserfield populatesfollowerStatewith that wallet’s position in the vault.portfoliois an array of[period, series]pairs bucketed byday,week,month,allTime, and theirperp*variants.- Aggregate stats (
apr,leaderFraction,leaderCommission,maxDistributable,maxWithdrawable) are JSON numbers, while position, equity, and history values are decimal strings. - For a lightweight list across all vaults, use vaultSummaries.
portfolio), headline stats (apr, distributable and withdrawable amounts), the follower roster, and the vault’s relationship to any parent or child vaults.
Pass the optional user field to have followerState reflect that wallet’s position in the vault.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
A single object describing the vault.Field descriptions
Note: Position, equity, and history values (portfolioaccount-value/PnL samples,vlm, and followervaultEquity/pnl/allTimePnl) are returned as decimal strings. The aggregate statsapr,leaderFraction,leaderCommission,maxDistributable, andmaxWithdrawableare returned as JSON numbers.
Last reviewed: 2026-07-24
vaultSummaries | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "vaultSummaries" is used to list summary information for every vault on the platform.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toPOST api.hyperliquid.xyz/infowith{"type": "vaultSummaries"}.
- Returns one entry per vault on the platform. The array may be empty depending on platform state.
relationship.typedistinguishes standalone vaults ("normal") from parent/child vault relationships.- This is a global, non-user-keyed type;
tvlis a decimal string. - For a single vault’s full breakdown (portfolio history, followers, APR), use vaultDetails.
vaultDetails for a single vault’s full breakdown.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
An array of vault-summary objects, one per vault. May be empty depending on platform state.Field descriptions
Note: tvl is returned as a decimal string, preserving upstream precision. Do not parse it as a float - keep it as a string or use a fixed-precision decimal type.
Last reviewed: 2026-07-24
webData2 | Hyperliquid Info API
Credit Cost: 1 per call Processing: Realtime The Hyperliquid info endpoint withtype: "webData2" is used to fetch the composite snapshot the Hyperliquid web app uses for a wallet in a single call.
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-equal toReturns the same composite payload the Hyperliquid web frontend pulls on page load for a given wallet: perp clearinghouse state, spot balances, open orders with trigger metadata, recent fills, and assorted UI-side context. User-keyed. Use this when you want a single round-trip to populate a dashboard for a wallet.POST api.hyperliquid.xyz/infowith{"type": "webData2", "user": "0x..."}.
Endpoint
Request
Example
cURL
TypeScript
Python
Response
The response is a single composite object. The example below shows one representative element of each array; in practicemeta.universe, assetCtxs, spotAssetCtxs, and openOrders each contain many entries.
Field descriptions
Note: All numeric balances, prices, and sizes are returned as decimal strings with full upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type. Timestamps (serverTime,time,timestamp) are integer Unix milliseconds.
Last reviewed: 2026-06-19