To maintain a uniform developer experience for all users of the Bluefin API, there are rate limits on requests and constraints on open orders.
Please make use of the WebSockets API if you need real-time data.
Rate limits are subject to change
All rate limits are subject to change in the future to help ensure a balance between demand and reliability.
Limits are enforced by IP Address for public endpoints, and by both IP Address and Account for private endpoints.
The rate limit on incoming requests is set 5,000 requests per 60 seconds, although brief bursts above this rate are permissible. Requests that exceed the rate limits will receive a HTTP response status code 429 along with
error code: 1015 in the error message .
Clients must adapt to the rate limits by managing HTTP 429 responses and honoring the Retry-After response header value, expressed as a decimal number of seconds. By waiting this specified minimum duration, subsequent requests should not be subject to rate limiting. The Retry-After value is set to 60 seconds by default.
An alternative approach to comply with rate limits is to reduce the pace of upcoming requests. This can often be achieved by utilizing one or multiple queues for pending requests, which can be processed by sending requests as long as Bluefin does not return an HTTP 429 response.
High Frequency Trading or Market Making partners known to Bluefin can request higher rate limits on their account.
The maximum number of open orders an account may have on one side of a market is 40. This implies the total number of open orders an account may have is
Num Markets * 2 Sides * 40.