Rate Limiting

API rate limits are in place to protect the Heyy API from traffic spikes that could put our systems at risk. We measure the number of requests sent to the API and throttle when they exceed the allowed amount. When you exceed the limit, we respond with 429 Too Many Requests and include the following headers:

Header Name	Description
`X-RateLimit-Limit`	Maximum number of requests allowed for the app.
`X-RateLimit-Remaining`	Number of requests left in the current minute.
`X-RateLimit-Reset`	Time when the request count resets to the maximum. Shown as a UNIX timestamp.

Rate limits by plan

Limits are applied per 1-minute window. The table below shows the maximum number of requests allowed per minute for each plan.

Plan	Requests per minute
Hobby	100
Pro	500
Ultra	1,000
Enterprise	Custom

Error response example

When you are rate limited, the API returns 429 Too Many Requests with this body:

{
  "success": false,
  "error": {
    "messageKey": "rate_limit_exceeded",
    "message": "Too many requests. Limit is applied per minute per tenant. Please retry after the time indicated by the X-RateLimit-Reset header."
  }
}

Use the X-RateLimit-Reset header to know when you can send requests again, and consider implementing exponential backoff or queuing to avoid hitting the limit repeatedly.

GETTING STARTED

HEYY API

Rate limits by plan

Error response example

​Rate limits by plan

​Error response example

Rate limits by plan

Error response example