Hyperliquid Perpetual Market Snapshot avatar

Hyperliquid Perpetual Market Snapshot

Pricing

Pay per usage

Go to Apify Store
Hyperliquid Perpetual Market Snapshot

Hyperliquid Perpetual Market Snapshot

Read-only normalized Hyperliquid perpetual market snapshots with optional bounded L2 books.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Sarthiii B

Sarthiii B

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Share

Hyperliquid market snapshot

Read public Hyperliquid perpetual market data through the official /info endpoint.

The Actor sends POST https://api.hyperliquid.xyz/info with { "type": "metaAndAssetCtxs" }. It joins each universe[index] metadata item to assetCtxs[index]. It preserves documented decimal string fields as strings, so downstream code does not lose precision.

Set includeL2Book to true to make one bounded l2Book request per selected symbol. The Actor keeps at most 20 symbols, 20 order-book levels per side, and 2,000,000 response bytes. It times out each request after 10 seconds by default. A HTTP 429 response waits for Retry-After and retries once. The Actor sends Content-Type only. It does not send an API key or wallet signature.

Input

{
"symbols": ["BTC", "ETH"],
"includeL2Book": true,
"l2BookDepth": 10,
"timeoutMs": 10000
}

An empty or omitted symbols array returns all markets in the metadata response.

Local use

npm install
npm test
npm start

npm start runs the Apify Actor and reads its input from the Apify runtime.

A live read uses only free public market-data requests:

$SYMBOLS=BTC,ETH INCLUDE_L2_BOOK=true npm run live-read

The live command prints JSON to stdout. It does not place orders, require credentials, or use paid infrastructure.

Output

Each record contains symbol, the source metadata, decimal-string market fields, optional l2_book, and an ISO-8601 observed_at timestamp.

Fixture tests cover response shape, index joins, decimal-string preservation, timestamp capture, timeout, response-size limits, symbol and depth bounds, and 429 handling.

Official sources