If you are hitting 429 Too Many Requests errors, experiencing delayed order fills, or seeing your API key temporarily suspended, you are likely bumping against these limits. This guide breaks down exactly how Hyperliquid structures its API rate limits, what the user limits are, and how you can architect your application to stay well within the boundaries.
About this guide: I'm Lawrence, the writer behind supa.is. Between February and May 2026 I've published 150+ articles on supa.is across crypto and brokerage tooling — including 30+ Hyperliquid-specific guides (recent examples: Hyperliquid API Key Setup, Hyperliquid Python SDK Tutorial, Hyperliquid API Error Responses). The most-repeated reader question across that Hyperliquid archive is exactly how to avoid API throttling, which is why I'm publishing this standardized guide instead of answering one-off.
Why Hyperliquid Enforces API Rate Limits
Hyperliquid isn't a traditional centralized exchange with redundant server clusters to absorb traffic spikes. It's a high-performance L1 blockchain with a custom matching engine, meaning its API architecture is tightly coupled with on-chain state.
Every order placed via the API interacts with the Hyperliquid L1. If a single user floods the API, it causes latency spikes for everyone else, state bloat on the L1, and gives the bot operator an unfair front-running advantage.
Rate limits are the primary defense against this. They ensure that API consumers—whether they are retail traders running a simple script or institutional players running high-frequency strategies—share the network fairly.
Hyperliquid API Rate Limits: The Numbers
Hyperliquid's rate limits are applied at the API key level. This means each unique API key has its own quota. If you are running multiple bots, you should consider using multiple API keys to distribute the load.
According to the official Hyperliquid documentation, the rate limits are structured around a sliding window mechanism. Here is the breakdown of the current limits as of 2026:
1. Global Request Rate Limit
Hyperliquid caps you at 30 requests per second per API key. This applies to everything—order placement, cancellations, and data queries. Exceed it, and you'll get a429 Too Many Requests error with a Retry-After header telling you how long to wait.
2. Order Placement Rate Limit
Placing orders is computationally expensive, so Hyperliquid enforces a stricter 10 orders per second limit per API key. If you're running a high-frequency market-making strategy, you'll need to split it across multiple API keys to get higher throughput.3. Data Query Rate Limit
Fetching the order book, recent trades, or positions is less taxing, but still capped at 20 requests per second. It's easy to exceed this in a tight polling loop. A script checking the order book every 100ms burns 10 req/s; run 3 of those on the same key and you've already hit your global 30 req/s cap, leaving zero room for actual trades.Hyperliquid User Limits
Beyond rate limits, Hyperliquid also enforces user limits. These are not about how fast you can make requests, but rather *what* you can do within a single request or a short timeframe.
Like what you're reading? Try it yourself — this link supports ChartedTrader at no cost to you.
Sign up on Hyperliquid →1. Maximum Orders Per Request
You can batch orders into a single API call, but Hyperliquid caps it at 10 orders per batch. Submit more, and the whole batch gets rejected.2. Maximum Open Orders
You can only have 100 open orders at any given time across all markets. This prevents users from hoarding order book space. If you're a market maker, you'll need to aggressively cancel stale orders before placing new ones, or your 101st order will fail.3. Position Limits
While not strictly an API limit, Hyperliquid enforces position limits on certain markets. These are usually tied to the funding rate and the overall risk exposure of the market. If you try to open a position that exceeds the maximum allowed size for that market, the order will be rejected.How to Avoid Hitting Rate Limits
Hitting rate limits is a common issue for new API users. Here are some best practices to ensure your bot runs smoothly without getting throttled.
1. Use Exponential Backoff
When you receive a429 Too Many Requests error, do not immediately retry. Instead, implement an exponential backoff strategy. Start by waiting 1 second, then 2 seconds, then 4 seconds, and so on, up to a maximum of 30 seconds. This prevents your bot from continuously hammering the API and getting permanently banned.
2. Batch Your Requests
If you need to place multiple orders, batch them into a single request. This reduces the number of API calls you make, saving you valuable rate limit quota. For example, if you need to place 5 orders across 3 different markets, you can do it in 1 request instead of 5.3. Use WebSockets for Real-Time Data
Polling the API for real-time data is inefficient and will quickly eat up your rate limit. Instead, use Hyperliquid's WebSocket API to subscribe to market data. WebSockets allow you to receive real-time updates without making repeated API calls. This is especially important for strategies that rely on low-latency data.4. Monitor Your Usage
Implement a local counter in your bot to track how many requests you are making per second. If you see your request rate approaching 90% of the limit, slow down your bot. It's better to be proactive than to get throttled.What Happens When You Exceed Limits?
When you exceed Hyperliquid's rate limits, the API will return a 429 Too Many Requests status code. The response body will contain a JSON object with an error message and a Retry-After field.
{
"status": "error",
"message": "Rate limit exceeded. Please wait before making another request.",
"retry_after": 5
}
The retry_after field indicates the number of seconds you must wait before making another request. If you ignore this and continue to make requests, your API key may be temporarily suspended. In severe cases, repeated abuse of the API can lead to a permanent ban.
Comparing Hyperliquid API Limits to Other DEXs
How do Hyperliquid's rate limits compare to other decentralized exchanges? Hyperliquid's limits are significantly more generous than those of other DEXs like dYdX and GMX. While other platforms enforce stricter caps on both request frequency and open orders to protect their slower matching engines, Hyperliquid's robust infrastructure allows for higher throughput. This makes it a better fit for high-frequency trading strategies. However, "generous" does not mean "unlimited." You still need to be mindful of your request rate.
Troubleshooting Common API Issues
If you are experiencing issues with the Hyperliquid API, here are some common problems and their solutions.
Issue: Orders are not being filled
Check if your price is too far from the market (slippage), if the market lacks liquidity, or if you're actually hitting rate limits and getting rejected.Issue: API key is being rejected
Double-check your key and secret. If you've set up an IP whitelist, ensure your server's IP is on it, and verify the key has the necessary trade permissions.Issue: High latency
Check your internet connection and ensure your server is geographically close to Hyperliquid's nodes. Also, watch out for rate limits—getting throttled can cause requests to queue up, artificially inflating latency.Final Thoughts
Respecting Hyperliquid's limits isn't just about avoiding 429 errors; it's about keeping your bot alive in a high-frequency environment. Stick to the backoff and batching rules above, and you'll stay out of the ban hammer's reach.
If you are just getting started with Hyperliquid, make sure to sign up using our referral link to get a 4% fee discount on your trades. And if you need help with API key setup, check out our Hyperliquid API Key Setup guide.
Risk Warning: Crypto trading involves substantial risk of loss. Never invest more than you can afford to lose. This is not financial advice.
FAQ
What happens if I exceed Hyperliquid's rate limits?
If you exceed the rate limits, your requests will be rejected with a429 Too Many Requests error. You must wait for the specified Retry-After time before making another request. Repeated abuse can lead to temporary or permanent suspension of your API key.