Skip to main content

​
Rate limits

The RevenueBase API uses rate limits to ensure fair usage. Limits are applied per API key.
Limit typeDefaultNotes
Requests per minute60Per API key
Requests per day10,000Resets at midnight UTC
When you exceed a limit, the API returns 429 Too Many Requests. Include a short delay or use exponential backoff before retrying.

​
Rate limit headers

Responses may include:
  • X-RateLimit-Limit — Max requests allowed in the window.
  • X-RateLimit-Remaining — Requests left in the current window.
  • X-RateLimit-Reset — Unix timestamp when the window resets.

​
Error codes

HTTP statusMeaningWhat to do
400Bad RequestCheck request body and parameters.
401UnauthorizedVerify your API key and x-key header.
403ForbiddenKey valid but not allowed for this resource.
404Not FoundEndpoint or resource does not exist.
422Validation ErrorFix the fields listed in the response detail.
429Too Many RequestsRespect rate limits; retry after backoff.
500Server ErrorRetry with backoff; contact support if it persists.

​
Validation errors (422)

Validation errors return a JSON body with a detail array describing each issue: 
{
  "detail": [
    {
      "loc": ["body", "email"],
      "msg": "value is not a valid email address",
      "type": "value_error.email"
    }
  ]
}
Use loc and msg to fix the request and retry.