You can make as many API calls as needed — Chift does not impose any internal restrictions. Any limitations you may encounter come directly from the connected third-party software (connectors).
How Chift Handles Rate Limits
Even though Chift doesn’t define its own limits, we handle rate limits from connectors gracefully to avoid unnecessary errors and ensure stable synchronizations. We distinguish between two main types of rate limits:1. Daily rate limits
When a connector enforces a daily limit, Chift cannot bypass it.In such cases, we return a clear error specifying:
- the type of rate limit, and
- the remaining time before it resets.
2. Short-term (minutely) rate limits
For short-term rate limits, Chift automatically retries the request to maximize the success rate. By default:- up to 5 retries are performed,
- with exponential backoff between attempts: 1s, 2s, 4s, 8s, and 16s.
Note: If all retries ultimately fail, Chift returns an error with a specific code and message indicating a rate limit issue.
When the connector does not provide clear information about rate limits, the error may appear as a generic synchronization failure.
Custom Handling
For some connectors, we apply custom retry logic based on the additional information available in their documentation or error messages.For example, when a “retry-after” value is provided, Chift will respect it. This retry logic is fully abstracted from your side — you don’t need to handle it manually.
Its purpose is simply to maximize reliability and reduce unnecessary failures caused by rate limits.