As FastBound continues to grow and more partners integrate their solutions using our API, we need to ensure that we maintain an acceptable level of performance for all requests, including those made from the user interface. As such, starting on 2/2/2021 at midnight UTC, FastBound will begin limiting API requests to
60 requests/minute per account. Until then, rate limiting is off by default.
During the grace period, you can enable and disable rate limiting from account settings. We strongly encourage you to enable rate limiting and ensure all of your software integrations work properly before 2/2/2021 at midnight UTC. On 2/2/2021 at midnight UTC, FastBound will enforce rate limiting for all accounts that use our API, and you will no longer have the option to disable it.
How does it work?
When enabled, the first API request for an account will start a 1-minute window. Within that window, you can make a total of 60 API calls. If you exceed that number, you will get a
429 Too Many Requests response. After the 1-minute window elapses, your next API call will start a new 1-minute window where you can again make a total of 60 API calls.
Regardless of whether or not you have exceeded the rate limit, each response will contain headers that tell you about rate limiting:
X-RateLimit-Limit: your rate limit quota (number of requests allowed in a 1-minute period)
X-RateLimit-Remaining: the number of requests remaining in the current 1-minute period
X-RateLimit-Reset:the date/time of when the current 1-minute period will reset, sent as a UNIX timestamp (seconds)
You will need to ensure that your software gracefully handles these rate limits.
How do I enable rate limiting for my account?
To enable API rate limiting during the grace period, click Settings and then click Enable API Rate Limiting, as shown below: