Rate Limits

All API keys are rate-limited to protect the platform and ensure fair usage across workspaces.

Default Limits

Limit	Value
Requests per minute	1,000 per API key
Max configurable	10,000 per API key
Burst allowance	Up to 50 requests in a single second

Response Headers

Every response includes rate limit headers:

X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 847
X-RateLimit-Reset: 1711180800

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per minute
`X-RateLimit-Remaining`	Requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp when the window resets

Exceeding the Limit

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:

{
  "error": {
    "code": 429,
    "message": "Rate limit exceeded. Retry after 12 seconds.",
    "retry_after": 12
  }
}

The Retry-After header indicates how many seconds to wait before retrying.

Best Practices

Use bulk operations

Prefer records.bulk_create and lists.bulk_add_entry over individual calls when creating multiple items.

Cache reads

Cache objects.list and views.list responses — schemas change infrequently.

Respect Retry-After

Always honor the Retry-After header. Exponential backoff is recommended.

Request higher limits

Contact support to increase your per-key limit up to 10,000 requests/minute.

Configuring Limits

Workspace owners can adjust per-key rate limits:

Go to Settings > Developers > API Keys
Click the key you want to modify
Set the Rate Limit field (100 to 10,000)
Save

Getting Started

Connect

Examples

Agent Workflows

Sources

Reference

Default Limits

Response Headers

Exceeding the Limit

Best Practices

Use bulk operations

Cache reads

Respect Retry-After

Request higher limits

Configuring Limits

​Default Limits

​Response Headers

​Exceeding the Limit

​Best Practices

Use bulk operations

Cache reads

Respect Retry-After

Request higher limits

​Configuring Limits

Default Limits

Response Headers

Exceeding the Limit

Best Practices

Configuring Limits