Rate Limiting

Warp’s API enforces a rate limit of 60 requests per minute with a max burst request limit of 100 requests.

Rate Limit Response

When you exceed the rate limit, you’ll receive an HTTP 429 response with a body containing a retryAt timestamp indicating when you can retry your request.

{
  "_tag": "RateLimitExceeded",
  "message": "Rate limit exceeded",
  "retryAt": "2026-01-01T00:00:00Z"
}

Field	Type	Description
_tag	"RateLimitExceeded"	Error identifier
message	string	Human-readable error message
retryAt	string (ISO 8601)	Timestamp indicating when to retry

Best Practices

Implement exponential backoff in your application to gracefully handle rate limit errors.

• Monitor the retryAt timestamp and wait until that time before retrying
• Implement request queuing to avoid bursts of requests
• Cache responses when possible to reduce API calls