API Rate Limiting
To ensure service stability and to prevent abuse, as of 26 November, 2025, Seemplicity applies rate limits on requests with the API token.
The limits are according to the following contexts:
- Global - Seemplicity limits all requests to the API, no matter the identity of the token. We do this to protect the platform from extensive usage.
- Customer - Seemplicity limits API requests per customer so that one customer cannot block the usage of other customers. By default, this limit is smaller than the global limit.
- Token - Seemplicity limits API requests per token within the context of the customer. One customer may manage/have multiple token keys, and each is limited. By default, this limit is smaller than the customer limit.
A request can be independently blocked according to any one of these limits (Global, Customer, or Token).
In cases where a limit is breached, the user receives a response informing them how long to wait before attempting another request.
Recommended: In cases where your organization breaches the limit and you're employing a script with the API, you can adjust it once the breach occurs so you can see the error information and structure. In the error's headers, Retry-After informs you of the number of seconds to wait until you can retry your request. For example, Retry-After: 3597 indicates you must wait one hour in seconds. Once you have this data, set your script to retry after the amount of time has passed.
See the example Response with the 429 Status Code: 429 TOO MANY REQUESTS
{
"error": "rate_limited",
"message": "Too Many Requests"
}In cases where Seemplicity fails to identify the token or the customer of a request, the Global limit is applied.
On this page
- API Rate Limiting