Rate limiting - Duoplane API

In order to maintain the health and stability of our system, all Duoplane APIs are subject to rate limits. Limits are calculated using the leaky bucket algorithm with the following settings:

Bucket size: 40 requests per API user

Leak rate: 2 per second

All requests that are made after rate limits have been exceeded will see a 429 Too Many Requests error response.

To help you track your API usage, each API response includes the following data in the meta object of the JSON response:

requests_remaining: The number of API requests remaining in your "bucket"

retry_after_seconds: If the rate limit has been exhausted, this is the number of seconds to wait until making another API call.

Please design your code to implement a backoff period if you receive a 429 Too Many Requests response. If we continue to receive API requests after rate limits have been exceeded, those API requests will increase the time that you are required to wait until retrying an API call.