Rate limits
How much an integration key may send, size limits, time windows and what happens at the limit.
Per key#
| What | Limit |
|---|---|
REST and MCP with Authorization: Bearer | 600 requests per minute per key |
Inbound events (/inbound/{tenant}) | 600 events per minute per key, counted separately |
Windows are fixed calendar minutes, counted per server process (we run two, so short bursts
can pass a little above the number). Over the limit you get 429 rate_limited with
Retry-After. Inbound events are idempotent — resend the same id after the pause.
Web sessions of people are not rate-limited per request; sign-in, password reset, public forms and the new contact page have their own anti-abuse limits.
Sizes and windows#
| What | Limit |
|---|---|
| Inbound body | 256 KB |
| Signature time window | ±300 seconds |
Page size (limit) | max 200 (default 50) |
MCP history_* | max 100 changes |
| File upload | 25 MB |
| Webhook response time | 10 seconds, first 2 KB of the answer are logged |
| Webhook retries | 5 attempts over ~8.5 hours, then dead |
Need more?#
If a sync needs more, page with limit=200 and the cursor instead of many small calls,
or write to us — limits are per key and can be raised for a tenant.