Is there a rate limit on the API?
Quick answer
Yes. Each API key may make up to 1,200 read requests and 120 write requests per minute. Limits are counted per key, so one runaway script cannot starve your other integrations. Requests without a valid key are limited per IP address. A request over the limit receives a 429 response with retry information.
Detailed answer
The limits are set generously for normal integrations while protecting the platform.
The limits
- Reads (GET): 1,200 per minute per key.
- Writes (PUT, POST, DELETE): 120 per minute per key.
- Unauthenticated or invalid-key requests: a lower per-IP limit, counting failed key checks.
How they are counted
Fixed one-minute windows per key. A burst across a window boundary is possible, but sustained traffic above the limit is refused.
What a refused request looks like
A 429 response. Wait for the next window before retrying, and use exponential backoff in your client.
Designing within the limits
- Nightly exports: 1,200 reads per minute is enough to fetch reports for thousands of accounts in minutes.
- Checkout integrations: one write per sale is far below 120 per minute.
- Dashboards: cache responses on your side instead of calling the API on every page view.
Separate keys
Because limits are per key, give each integration its own key so a heavy export never slows your checkout.
PropExecutor team · Updated