Public API
Rate limits
RateLimit response headers, Retry-After, and 429 handling
Limits are applied per API key using a fixed window (default 120 requests / 60 seconds). Exact values may be configured on the server.
Response headers
Every authenticated Public API response includes:
| Header | Meaning |
|---|---|
RateLimit-Limit | Maximum requests allowed in the current window |
RateLimit-Remaining | Remaining requests in the window |
RateLimit-Reset | Unix timestamp (seconds) when the window resets |
When you exceed the limit
The API responds with 429 Too Many Requests and:
Retry-After— seconds to wait before retryingapplication/problem+jsonwith typehttps://cowtic.com/problems/rate-limited
HTTP/1.1 429 Too Many Requests
RateLimit-Limit: 120
RateLimit-Remaining: 0
RateLimit-Reset: 1721491200
Retry-After: 60
Content-Type: application/problem+jsonClient guidance
- Read
RateLimit-Remainingand slow down before hitting zero when possible. - On
429, wait at leastRetry-Afterseconds (exponential backoff is fine on top). - Spread bursts; prefer background jobs over tight loops.
- Use separate keys per integration if you need independent budgets.