Rate Limits & Errors

API requests are rate limited per API key:

• •Standard Plan — 100 requests per minute
• •Professional Plan — 500 requests per minute
• •Enterprise Plan — 2000 requests per minute

**Rate Limit Headers:**

• •X-RateLimit-Limit — Maximum requests per window
• •X-RateLimit-Remaining — Requests remaining in current window
• •X-RateLimit-Reset — Unix timestamp when the window resets

When rate limited, the API returns 429 Too Many Requests.

Standard HTTP status codes used:

• •200 — Success
• •201 — Resource created
• •400 — Bad request (validation errors)
• •401 — Unauthorized (invalid or expired token)
• •403 — Forbidden (insufficient permissions)
• •404 — Resource not found
• •409 — Conflict (duplicate resource)
• •422 — Unprocessable entity
• •429 — Rate limit exceeded
• •500 — Internal server error

All error responses follow a consistent format:

• •error.code — Machine-readable error code (e.g., VALIDATION_ERROR)
• •error.message — Human-readable error description
• •error.details — Array of specific field-level errors (for 400/422)

Best practices:

• •Always check the HTTP status code first
• •Use exponential backoff when retrying after 429 or 500 errors
• •Log error codes and request IDs for debugging