Rate limiting

• Global across all endpoints.
• User Profile Searching with max_concurrent=1 or in situations where the API is being used abusively.
• Creating a Delivery with max_concurrent=1 per User Profile to handle the enforcement of the maximum Pending Deliveries.

• The global strategy is applied to all requests with limited exceptions. Currently set to 60-120 requests per minute.
• The max_concurrent strategy is used to limit based on the maximum concurrent requests. When limiting with this strategy, we subtract and add from an N-sized bucket. We give an X-RateLimit-Limit header with N number of concurrent requests when that limit is reached. Please wait until at least one of the outstanding requests finishes. This strategy will queue for up to 4 seconds to allow other concurrent requests to complete. If no request completes during that initial 4 second wait, a 429 response will be sent.
• The bucket strategy is used to limit based on the total number of requests. Using this strategy, the bucket window expires after N seconds. We give an X-Ratelimit-Wait header with N number of seconds. This is the number of seconds to pause for until requests can proceed without immediate rate limiting.

Contact us to speak about Changing these limits.

​

HTTP Response

X-Ratelimit-Wait: 12

{
  "code": 429,
  "messages": ["Rate Limited: Please refer to the API docs https://developers.chameleon.io/concepts/rate-limiting for more information"],
  "wait": 12
}

X-Ratelimit-Limit: 4

{
  "code": 429,
  "messages": ["Rate Limited: Please refer to the API docs https://developers.chameleon.io/concepts/rate-limiting for more information"],
  "limit": 4
}