Rate Limits

Rate limiting is a technique for limiting network traffic. It sets a limit on how many requests a client can make to the API within a certain time period. The Whippy Public Open API uses rate limiting to ensure fair usage and protect the service from abuse.

The rate limits in the Whippy Public Open API are defined based on the type of API and the type of request (read or write). The limits are categorized into three types:

• Standard APIs: These have a limit of 25 requests per second for both read and write operations.
• Time Consuming APIs: These are APIs that typically take longer to process, such as requests to "v1/campaigns", "v1/contacts/lists", and "v1/sequences". They have a limit of 10 requests per minute for write operations.
• High Limit APIs: These are APIs that have a higher limit, such as "v1/organization". They have a limit of 35 requests per second for write operations and 50 requests per second for read operations.

The rate limits are applied separately for each API key and organization ID. If a client exceeds the rate limit for an API key or an organization, the API will respond with a 429 Too Many Requests status code.

Please note that these limits are subject to change, and it's recommended to design your application to handle rate limit errors gracefully. This can include strategies like exponential backoff, where the client progressively lengthens the wait time between requests to reduce the load on the server.