How Spot Unfilled Order Limits Respond to Orders and Fills

Summary

This exchange guide explains how spot order rate limits count newly placed orders that remain unfilled. A successful order placement increases the count for the current interval; reaching the configured limit causes later requests to be rejected. The limit is shared across an account’s IP addresses, API keys, and supported APIs, and can be queried through exchange information.

A first partial or full fill reduces the count across active intervals, with maker fills and large fills potentially receiving larger reductions. Cancellations and expirations do not lower the count, and fills from orders placed on an earlier day can reduce the current count. The examples illustrate these rules, including delayed count updates and the absence of further credit once the count reaches zero. Actual limits may differ from the illustrative configuration, and order requests remain subject to separate general API or message limits; traders should monitor counts and stop submitting orders after a rate-limit rejection until the interval expires.

Key ideas

• Each successful order placement adds to the account’s unfilled order count for the current interval.
• The count is shared across an account’s IP addresses, API keys, and APIs.
• A first fill reduces the count, and maker or large fills may reduce it by more than one.
• Canceled and expired orders do not reduce the count.
• Fills from older orders can reduce the current count, but the count cannot fall below zero.
• The examples are illustrative, and actual limits and update timing may differ.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.