API reference
3 min read
Request limits per plan and how to handle 429 responses.
Limits protect the API for everyone. They apply per workspace and reset every second.
Starter: 100 requests per second
Growth: 500 requests per second
Enterprise: custom limits
When you hit a limit the API returns 429 Too Many Requests with a Retry-After header. The official SDKs retry automatically with exponential backoff.
Was this page helpful?
Most searched
The three articles developers open most. Start here if you're stuck on auth, webhooks or keys.
Authentication
How do I authenticate API requests?
How do I authenticate API requests?
Top result
Authentication
↵
to open
Set up webhooks
My webhooks aren’t arriving. What should I check?
My webhooks aren’t arriving. What should I check?
Top result
Set up webhooks
↵
to open
Rotate API keys
How do I rotate a leaked API key?
How do I rotate a leaked API key?
Top result
Rotate API keys
↵
to open
Support
Docs answer most questions. For everything else, the engineers who built the API are one message away.
MK
Maya · Northwind
Our webhooks stopped at 14:02 UTC. Request ID req_8f2a91.
PS
Priya · Tessera engineer
Found it. Your endpoint returned 502 for 3 minutes. We replayed 214 events, all delivered.
Priya is typing
CAN’T FIND IT?
Ask the people who build the API. Send a request ID
or a failing payload and we’ll trace it on our side.
Replies in under 4 hours on weekdays
Answered by engineers, not a script
Full logs checked for every request ID
Quire Template
from
$79
