A rate limit is a cap a system sets on how many API requests a caller can make in a given time, such as per second, minute or day.
Integration · Reviewed by Ray Rasouli
Ask about rate limit
Plain answers, with your setup in mind.
Ask anything about rate limit. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Vendors use rate limits to keep their service stable for everyone. If your integration sends more requests than allowed, the API starts refusing them, often with an error code 429 that means "too many requests."
A retailer might sync 500 product updates at once after a price change and suddenly find half of them rejected. The fix is usually to slow down, group updates into fewer calls, or spread the work over time.
Before building an integration, check the vendor's documented limits and compare them to your busiest day, not your average one.
In practice
Limits are tested on a quiet day.
Integrations work in testing and fail during a sale, month end or seasonal peak.
Rejected calls are not retried.
When the API says "slow down," code that does not wait and retry simply drops the data.
Several tools share one limit.
Your ecommerce app, reporting tool and iPaaS may all draw from the same account allowance.
Each record gets its own call.
Updating items one at a time burns through limits when a bulk endpoint would do it in a few requests.
It means too many requests. The caller has hit the rate limit and should wait before trying again.
Some vendors offer higher limits on bigger plans or by request. Check the vendor's pricing and documentation.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.