To ensure fair usage and optimal performance, we've implemented rate limits on our API. By default, each account is allowed a maximum of 120 operations per minute. An "operation" refers to any API call you make, regardless of whether it's a read or write operation. The rate limit applies globally across all API endpoints.

Exceeding the rate limit

If you exceed your rate limit, you'll receive a standard 429 Too Many Requests HTTP status code. The response body may include additional details about the rate limit and when it will reset.

Handling rate limits

To gracefully handle rate limits, we recommend implementing an exponential backoff strategy. This involves retrying failed requests with increasing delays between attempts.

Consider these general guidelines:

Maximum retries: Prevent your integration from getting stuck in an endless retry loop by setting a maximum number of times to attempt a failed request. For example, you might limit retries to 5 times.
Initial delay: Start with a short initial delay (e.g., 1 second) and gradually increase it with each retry (e.g., by doubling the delay each time).
Jitter: Introduce randomness to the delay to avoid synchronized retries.

Increasing your rate limit

If you have a consistent need to exceed the default rate limit, please contact us at support@pelcro.com to discuss options. In some cases, we may be able to increase your limit based on your specific use case.

Additional considerations

Queuing requests: For users who consistently reach the limit, storing requests in a queue and processing them at a controlled rate can be a helpful strategy.

By following these recommendations, you can effectively manage rate limits and optimize your API interactions.