Skip to main content

Rate limits and best practices

Figure Markets applies rate limiting at the API gateway for REST traffic across Public API, Trader API, and Partner API. Limits protect the platform and keep usage fair. Exact thresholds can change and may differ by route or customer arrangement, but how you should respond is the same everywhere.

When you are limited​

  • 429 Too Many Requests — Your client or IP has exceeded a limit. Implement backoff (for example exponential) and retry only after a delay. Respect any Retry-After header or guidance in the response when present.
  • Conservative usage — Stay within a reasonable request rate. If you are unsure, start conservative and increase only after you confirm stable behavior.

Public API (market data)​

  • IP-based limiting — Public REST is commonly limited per IP because there is no authenticated identity.
  • Prefer WebSocket — For live market data, use the Public API WebSocket instead of tight REST polling. That cuts request volume and avoids hitting limits.

Trader API​

  • Same gateway behavior — Authenticated Trader REST is also limited. Treat 429 the same way: backoff, don’t hammer retries.
  • High-volume trading — For latency-sensitive or very high order rates, use Trading (low-latency) (and the low-latency spec), not sustained heavy load on standard REST alone.

Partner API​

  • REST — Partner REST is rate limited; 429 means backoff and retry with spacing.
  • FIX — Market makers doing high-frequency flow should use FIX for order entry and market data where that is your integration, rather than relying on REST polling for those paths. See Partner API — Trading (FIX).