Usage limits

Requests are subject to a daily quota and a per-minute limit. Reaching either limit returns HTTP 429.

Daily quota by plan

Plan	Default quota	Shared by
Pro	1,000 requests per day	The person's tokens.
Business	10,000 requests per day	The company's tokens.

The quota resets at the start of each service day. Check the applied limit and current usage under API > Today's quotas in the dashboard, or in the response headers.

Requests that reach endpoint processing count toward the quota, including validation errors such as 400, 404, 409, 413, or 415. Requests rejected earlier, for example due to an invalid token, missing authorization, an incorrect method, or an exhausted limit, do not consume the daily quota.

Per-minute token limit

The per-minute limit applies separately to each token and is the same on both plans. Read X-RateLimit-Limit for the current limit. A request can count toward this limit even if the endpoint subsequently rejects it.

Usage headers

Header	Description
X-Quota-Limit	Daily quota applied to the person or company.
X-Quota-Remaining	Requests remaining in the daily quota.
X-RateLimit-Limit	The token's per-minute limit.
X-RateLimit-Remaining	Requests remaining in the current one-minute window.
Retry-After	Wait time in seconds for a 429 response.

Daily quota headers appear when that quota is checked. Per-minute headers appear after token verification. Account summary also returns daily usage and the per-minute limit in the api object.

Handle HTTP 429

Read Retry-After and wait for the specified duration before retrying. For the per-minute limit, the reported wait is 60 seconds. For the daily quota, it is the time remaining until the quota resets.

Plan batch requests

Before starting a batch, check your usage with Account summary. Reuse list and statistics results where possible, and follow Pagination and filters to reduce the number of requests.