for ChatGPT, Claude, Perplexity…
DEVELOPER

Hyperliquid rate limits

· 7 min read

Hyperliquid's info API needs no key, which is why people assume it is unlimited. It is not: every request spends from a shared 1,200 weight-per-minute budget per IP address, and the endpoints you need most for history work are the most expensive ones. This page documents the weight table, the math for fills exports, the 429 behavior we measured crawling a 45k-fill wallet, and the official escape valve.

Key facts
  • Aggregate budget: 1,200 weight per minute per IP across all REST calls.
  • History endpoints (userFills, userFillsByTime, userFunding, fundingHistory, recentTrades, historicalOrders, TWAP/delegator endpoints…) cost base 20 + 1 weight per 20 items returned — a full 2,000-fill page costs 120 weight.
  • That caps deep pagination at ~10 full calls/min ≈ 12,000 fills/min theoretical ceiling — our 45,147-fill month needs ≥4 minutes of crawling.
  • Overage returns HTTP 429; measured behavior is transient failure, not a hard wall — retry with back-off. Sustained violations can get an IP banned.
  • Bulk alternative: requester-pays S3 buckets (node_fills_by_block, node_trades, misc_events_by_block) — see the bulk download guide.

The weight table (October 2026 docs)

RequestWeightSurcharge
info: l2Book, allMids, clearinghouseState, orderStatus, spotClearinghouseState, exchangeStatus2—
info: userRole60—
info: all other documented calls20—
info: userFills, userFillsByTime, userFunding, fundingHistory, recentTrades, historicalOrders, nonUserFundingUpdates, twapHistory, userTwapSliceFills(ByTime), delegatorHistory, delegatorRewards, validatorStats20+1 per 20 items returned
info: candleSnapshot20+1 per 60 items returned
exchange actions1 + floor(batch/40)—
explorer calls40blockList: +1 per block
EVM JSON-RPC (rpc.hyperliquid.xyz/evm)—separate 100 req/min cap

Note the surcharge mechanism: it is the response size that is billed, not the request. An empty page costs base weight only — which is why the correct crawl pattern is "page until empty", not "page until error".

The math for a fills export

Everything else sharing your IP counts against the same 1,200 — a second tab running a scan, a bot on the same egress, your own retry loop. Budget for it.

What a 429 actually means (measured)

Deep-crawling a wallet with 80k+ fills we hit stretches of failed responses mid-history. The pattern that mattered: the failures were transient — retrying the identical window after ~1.5s returned data again, and fills continued for months past the failure point. Two rules fall out of this:

Per-address limits: a separate budget

Besides the per-IP budget, exchange actions (orders/cancels — not reads) are capped per address, scaled by trading volume. You can query the budget itself:

POST https://api.hyperliquid.xyz/info
{"type":"userRateLimit","user":"0x…"}

Measured response on a $18.9B-volume wallet (October 20, 2026):

{"cumVlm":"18928394140.0200004578",
 "nRequestsUsed":6440,
 "nRequestsCap":18928404140,
 "nRequestsSurplus":0}

The cap tracks cumulative volume with a ~10k-request floor — irrelevant for read-only tax exports, but the field to know if you ever write trading code.

Websocket and EVM caps

The official escape valve: S3

The docs' own answer for large batch needs is "use the S3 bucket instead" — requester-pays buckets holding fills by block, trades, non-trade events (funding, staking, transfers) and L2 book snapshots. Hundreds of GB of raw history, billed to your AWS account at cents per GB. Routes and bucket layout: Hyperliquid data download guide.

Your own history, paced for you

The scanner paginates within the weight budget automatically — fills, funding and ledger, grouped per tax year. Free, in your browser.

Scan my wallet

Common questions

What is the Hyperliquid API rate limit?

REST requests share an aggregate budget of 1,200 weight per minute per IP address. Most info calls cost 20 weight, but the history endpoints (userFillsByTime, userFunding and friends) add a surcharge of 1 weight per 20 items returned — so a full 2,000-fill page costs 120 weight and you can only afford about ten of those per minute.

What happens when I exceed the limit?

Requests start returning HTTP 429 instead of data. In our deep crawls the failures are transient — the same window succeeds after a short back-off — but sustained overage can get an IP banned. Retry the same window; never treat an error as the end of your data.

How do I get around the limit for bulk exports?

For your own tax history you cannot go around it, only pace to it — roughly 10 full fills calls per minute. For bulk market data the official route is the requester-pays S3 buckets (node_fills_by_block, node_trades, misc_events_by_block, market_data snapshots), not the API at all.

Primary sources

Check the linked sources for the rules, integration limits and API definitions discussed on this page. A general source does not settle every classification question or verify every third-party integration behavior.

  1. Hyperliquid docs — Rate limits and user limits 各接口的权重、按地址计的请求预算与 429 触发条件。

How this page was produced