Rate limits

RowCall limits how fast each key can send requests, and how many calls each org can have on at once. Limits protect shoppers from floods of calls and keep the API fast for everyone.

Request limits

Each API key, or each app's token for one org, can send 600 requests a minute. Over the limit, you get 429 with RATE_LIMITED. Wait a little, then retry with backoff.

The limit is per key, so two systems with their own keys don't slow each other down.

Lines and busy calls

Each org can only have as many calls on at once as it has free lines. A run whose lines are all busy isn't refused: it waits about 15 seconds and tries again, without using up an attempt. If you start many runs together, such as a batch of orders, they go out in turn.

Staying inside the limits

• Start runs as events happen rather than in large bursts.
• Use webhooks instead of polling runs.
• Back off with jitter on 429 and 5xx, and send the same Idempotency-Key when you retry a POST. See Handling errors.

Need higher limits for a launch? Ask through Contact.

Next stepTypeScript SDK

Call the API from TypeScript with typed requests.