Rate limits
The Zillo API enforces per-key + per-merchant quotas. Every response carries the current state so you can pace yourself.
Default limits
| Bucket | Live keys | Test keys |
|---|---|---|
| Per key (per minute) | 60 | 30 |
| Per key (per hour) | 5,000 | 1,000 |
| Write methods (per minute) | 30 | 15 |
| All keys for a merchant (per minute) | 600 | 300 |
Need a quota raise? Contact support — increases are configured per merchant by Zillo staff.
Response headers
Every response — including 200s — includes:
X-RateLimit-Limit: 60 X-RateLimit-Remaining: 47 X-RateLimit-Reset: 1717592400 X-Request-Id: 3a1b...c9f
X-RateLimit-Reset is unix seconds. On 429 the response also carries Retry-After in seconds and an error body:
{
"error": "rate_limited",
"message": "Too many requests. Slow down or request a quota raise.",
"retry_after_seconds": 28
}Request id
Every response carries an X-Request-Id. Include it in support tickets so we can join from email back to the exact request in your logs.