Skip to content
Last updated

Rate limiting

Unless otherwise specified, most Integration Platform APIs impose rate limits on the number of API calls that can be issued over a period of time.

While we do not publish exact rate limit rules, these limits are not designed to inhibit normal application behaviours. Your application should handle 429 errors.

When the rate limit is exceeded these endpoints will return an HTTP 429 Too Many Requests response with the following response body indicating when requests will be allowed again:

{
  "type": "https://tools.ietf.org/html/rfc6585#section-4",
  "title": "Too Many Requests",
  "status": 429
}

The Retry-After response header indicates how many seconds a client should wait before retrying the request. For example

Retry-After: 60

In addition, some of our APIs also returns common unofficial HTTP headers such as

  • X-RateLimit-Limit - The maximum number of requests permitted during the current rate-limiting window.
  • X-RateLimit-Remaining - The number of requests remaining before the allocated quota is exhausted.
  • X-RateLimit-Reset - The number of seconds until the rate-limit bucket is fully replenished.