Skip to content

Rate Limits ​

To keep the API responsive for everyone, requests are rate limited. The limits apply to all endpoints, including the license key endpoints.

LimitPer secondPer minute
Per IP address20 requests200 requests
Per access token20 requests200 requests

Both limits apply at the same time, so a request counts towards its IP address and, if it has an access token, towards that token too. The windows are fixed: counts reset at the start of each second and each minute.

When you exceed a limit ​

The API responds with 429 Too Many Requests and an empty body. The response doesn't include a Retry-After header, so wait before retrying, ideally with exponential backoff (for example 1, 2, then 4 seconds).

Staying under the limits ​

  • Validate licenses from your users' devices, not from one server. License key endpoints are limited per IP address, so validating from each user's device spreads the load. If you validate from your own backend, all requests share your server's IP address.
  • Cache validation results. You rarely need to validate a license on every action; validating at startup and then periodically is usually enough.
  • Use pagination instead of many single-item requests. List endpoints can return many objects in one request. See Pagination.

Package usage limits ​

Separately from rate limits, your Licensing package may limit how many API calls your account can make. When you reach that limit, requests get 429 with the body "Too Many Requests (Reached license limit)". You can see your usage in the Licensing app.