To ensure a fair and reliable usage of the Clasp API, we enforce a rate limiting policy. This policy helps protect against excessive requests that could affect service quality.

​
Standard Throttling

Requests Limit: Partners are allowed up to 25 requests per second across all their API keys. Concurrency Limit: A maximum of 50 concurrent requests per partner is enforced to prevent overload.

​
Handling Limits

When a request exceeds the allowed rate, a 429 HTTP status code is returned, indicating that the request has been throttled. The response provides details on when to retry: 
{
    "type": "throttled",
    "message": "Request was throttled. Expected available in 1 second."
}
Additionally, the Retry-After header offers the exact wait time before the next request attempt, simplifying automated retry logic.

​
Strategies for Managing Limits

Proactive Throttling: Clients should monitor their request frequency to stay within the imposed limits. Automated Retries: Implementing automatic retries with respect to the Retry-After timeframe is recommended for handling 429 responses efficiently.

​
Exceeding Limits

In scenarios requiring higher limits (e.g., bulk operations), partners should contact Clasp developer support to discuss a limit increase. Our goal is to accommodate valid use cases while maintaining system integrity and performance. This rate limiting policy aims to protect both Clasp and its partners from potential issues arising from excessive API calls, ensuring a stable and responsive service for all users.