public/getRateLimits.
Tier 1 — Request budget (per wallet)
Every method carries a rate-limit class (shown on each method’s page in the API Reference tab). The class selects which per-wallet budget the request decrements. Authenticated traffic is keyed by wallet; unauthenticated/public traffic is keyed by IP.
Across the 134 JSON-RPC methods the classes are distributed:
non_matching
98 methods
matching
5 methods
proven
20 methods
endpoint
10 methods
custom
1 method
matching (5)
matching (5)
order, replace, cancel, cancel_by_instrument, cancel_by_nonce. All
order-flow writes share one per-wallet matching budget, regardless of how
many connections or session keys the wallet has open.proven (20)
proven (20)
private/transfer_spot, private/transfer_spot_external,
private/transfer_positions, private/withdraw, private/liquidate,
private/set_session_key, private/edit_session_key,
private/delete_subaccount, private/update_whitelisted_recipients,
private/change_subaccount_label, private/set_mmp_config,
private/reset_mmp, private/create_vault, private/update_vault_info,
private/mint_vault_shares, private/burn_vault_shares,
private/request_vault_deposit, private/request_vault_withdraw,
private/cancel_all_vault_requests, private/force_burn. Each call
changes account state, so all of them share one small per-wallet budget
(proven in
remaining_per_endpoint), independent of the matching and non-matching
budgets.endpoint (10)
endpoint (10)
cancel_all, private/send_quote, private/replace_quote,
private/cancel_quote, public/register_deposit_address,
private/register_bridge_deposit, private/register_withdraw_address,
private/send_block_proposal, private/accept_block_proposal,
private/cancel_block_proposal. Each decrements
its own per-(wallet, method) budget instead of a shared one, so a bulk
cancel or a market maker’s quoting doesn’t consume the matching or
non-matching budget.custom (1)
custom (1)
cancel_by_label decrements the matching budget when instrument_name is set, and its own per-method budget otherwise.Budgets are wallet-scoped, not per-subaccount or per-session-key. All
concurrent connections and session keys belonging to one wallet share a single
budget. Public, pre-authentication traffic is limited per source IP, along
with a cap on simultaneous WebSocket connections per IP.
Budget & window semantics
A request budget is a fixed window. The number of points available in each window is:Tier 2 — Per-instrument order-rate limit
Order-flow requests (order, replace, cancel, …) pass a second limiter: a
per-instrument token bucket, keyed by (wallet, instrument).
- The refill rate is a per-second TPS chosen by asset type — one value for perps and spot, another for options.
- The bucket’s capacity (its burst allowance) is
refill_rate × burst_multiplier. - Unlike the request budget’s fixed window, the bucket refills continuously, so it does not permit a window-boundary double-burst.
Daily RFQ limit
private/send_rfq also has a daily limit per wallet. All subaccounts of a wallet share it.
- A wallet can send a set number of RFQs per UTC day (20 in the mainnet reference below).
- Each RFQ of yours that fills adds more RFQs to that day’s limit (5 in the mainnet reference). An RFQ counts once, even if it fills in parts.
- The count resets at 00:00 UTC. A rejected RFQ does not count.
private/send_rfq returns -32000. Its data field is a JSON string with daily_rfq_limit,
rfqs_sent_today and reset_timestamp (the next reset, in milliseconds). This limit is not reported by
public/getRateLimits.
Open block proposal limit
A wallet can have a set number of open block proposals at the same time (3 in the mainnet reference below). A proposal counts until it ends: it executes, is cancelled or declined, or expires. At the limit,private/send_block_proposal returns -32000. Its data field is a JSON string with
max_open_block_proposals. Cancel a proposal or wait for one to end, then send again. This limit is not reported
by public/getRateLimits.
Concrete limits
All limits are deployment-specific and read from configuration at startup
— code defaults, testnet, and mainnet differ. Treat the values below as a
mainnet reference snapshot, not a contract, and always read your live
budget with
public/getRateLimits — the
authoritative, live source for your budget.Runtime introspection
public/getRateLimits returns your live request budgets. It is itself a non_matching
method, so calling it costs one non-matching point. It takes no parameters.
Per-method budgets, keyed by method name (e.g.
cancel_all), plus the
shared proven budget. A budget appears once the wallet has used it.getRateLimits exposes only the request-budget tier. The per-instrument
token buckets are not reported, so perp/option instrument limits cannot be
discovered at runtime.Rejection error codes
When a request exceeds a limit it is rejected — never queued — with a JSON-RPC error. Codes-32000 through -32099 are reserved for rate-limit errors. See
Error codes for the full catalogue.
Rejection
