Rate Limits for Integrators and Market Makers

Every request to the Derive API passes a per-wallet request budget and, for order flow, a per-instrument bucket. Integrators and market makers can qualify for higher matching-engine rate limits through the Institutional Trading Rewards Program. The V3 rate-limit model, request classes, budget windows, and the public/getRateLimits introspection method are documented in full on the Rate Limits reference page. This page focuses on what changes for integrators.

​

Integrator and market maker limits

Program participants qualify for the highest matching-engine rate-limit tier. There are two tiers today, based on market maker vs standard trader status: The Exchange reserves the right to add tiers assigned based on volume share and market maker rankings. Burst requests for both REST and WebSocket refresh every 5 seconds. For example, a trader can send 5× matching requests in a single burst but must wait 5 seconds before more can be sent.

​

Which requests count as matching

The following requests count as matching and per-instrument matching:

• private/order
• private/replace (counted as 1 request)
• private/cancel
• private/cancel_by_nonce
• private/cancel_by_instrument
• private/cancel_by_label (only when the instrument_name param is set)

custom rate-limited requests:

• private/cancel_all — 1 TPS
• private/cancel_by_label — 10 TPS (when instrument_name param is NOT set)

All other requests count as non-matching.

​

How to apply for increased limits

Market makers are eligible for higher rate limits. To apply, contact Derive support or complete the Institutional Trading Rewards contact form. Increased limits are granted alongside the fee-tier and rebate benefits of the program.

​

V3 rate-limit model

The canonical rate-limit model, class semantics, error codes, and the public/getRateLimits runtime introspection method live on the main reference page:

​

Related