Rate limiting

Rate limiting applies to the Bunce API. Send up to 500 requests per minute before getting a 429 error.

Rate limiting helps protect the Bunce platform and make sure it works smoothly for everyone. It works by putting a cap on the amount of requests that an IP address can make in a certain timeframe.

If you send too many requests, you'll get an error with a 429 response code.

429 - Too Many Requests

{
  "success": false,
  "message": "You have reached maximum request limit."
}

Rate Limit

TIP

Rate limiting may change. We'll communicate any changes in plenty of time on our developer changelog.

• All operations in the Bunce API are rate limited
• Each IP address can make up to 500 requests per minute.
• If exceeded, subsequent requests return a `429` error.
• When you get a `429` error, an IP address can't make another request for 60 seconds.

Handle rate limiting

When you get a rate limit error, it includes a Retry-After response header to let you know how long to wait before retrying your request. You should avoid making requests during this time.

To handle rate limiting, we recommend watching for 429 errors and building a retry mechanism that runs when the limit has expired.