Status codes and limits

Response codes

The Reva API uses the following status / error codes.

Response CodeDescription
200OK -- All good, your request is has been successful.
201Created -- Your request is has been successful and the resource has been created.
202Accepted -- Your request is has been successful and the resource has been updated.
400Bad Request -- There is something wrong or invalid with your request.
401Unauthorized -- There is something wrong with your Authorization header, e.g. your API key is wrong.
403Forbidden -- You don’t have permission to perform this action.
404Not Found -- The specified request/resource could not be found.
429Too Many Requests -- Slow down!
500Internal Server Error -- We had a problem with our server. Try again later.
503Service Unavailable -- We're temporarily offline for maintenance. Please try again later.

Request Limits

The Reva API rate limit is 150 requests per minute.

If this limit is exceeded, the application returns a 429 code ("Too Many request"). If the user reaches the limit, they must wait for the period (1 minute) to end before making API calls again.

The RateLimit-Limit, RateLimit-Remaining & RateLimit-Reset headers will be returned to let you know when you can start querying the API again.