Rate Limiting

Verifa enforces two types of limits: rate limits (requests per minute) and product quotas (resource creation per minute).

Rate limits by plan

Product quotas

Product quotas limit how quickly you can create specific resources:

Daily verification limits

Response headers

Every API response includes rate limit headers:

When a product quota applies, additional headers are included:

Handling 429 responses

When you exceed a rate limit or quota, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait:

1
HTTP/1.1 429 Too Many Requests
2
Retry-After: 12
3
X-RateLimit-Limit: 300
4
X-RateLimit-Remaining: 0
5
X-RateLimit-Reset: 1738368012
6
7
{
8
  "error": "rate_limited",
9
  "detail": "Rate limit exceeded. Retry after 12 seconds.",
10
  "status_code": 429
11
}

Best practice: Implement exponential backoff with jitter. Respect the Retry-After header value as the minimum wait time before retrying.

Endpoint-specific limits

A few endpoints sit outside the per-plan request bucket and have dedicated limits:

These limits also return 429 Too Many Requests with a Retry-After header.

Related

• Errors — Full error response reference including 429
• Authentication — API key types and plan tiers
• Idempotency — Safe retries with idempotency keys