Rate limit

Poodle API endpoints are rate-limited to ensure fair usage and maintain service stability. Exceeding the rate limit for an endpoint will result in a 429 Too Many Requests error.

Rate limit headers

All API responses include the following headers to help you manage your usage:

• ratelimit-limit: The maximum number of requests allowed within the rate limit window for the specific endpoint.
• ratelimit-remaining: The number of requests remaining within the current window.
• ratelimit-reset: The Unix timestamp (in seconds) indicating when the rate limit window resets.
• retry-after: (Only present on 429 responses) The number of seconds to wait before making another request to the endpoint.

Handling 429 errors

When you receive a 429 Too Many Requests response:

1. Check the retry-after header: This tells you exactly how many seconds to wait before retrying the request.
2. Implement backoff: Use an exponential backoff strategy for retries to avoid overwhelming the API.
3. Monitor headers: Proactively check ratelimit-remaining and ratelimit-reset to stay within the limits.