API Status Codes

These are the HTTP status codes returned by the REV23 API. When working with API keys or webhooks, these codes indicate what happened with your request.

Code	Status	Description
200	OK	The request succeeded.
201	Created	A new resource was created successfully.
204	No Content	The request succeeded but there is no content to return. Typically returned after deleting a resource.
400	Bad Request	The request could not be processed due to invalid data, missing required fields, or a business rule violation.
401	Unauthorized	Authentication credentials are missing or invalid. Verify your API key and Cloud name headers.
402	Payment Required	The problem details identify the cause: a disabled feature, an ended trial, a cancelled or past-due subscription, or a failed card or refund operation.
403	Forbidden	The authenticated user or API key does not have permission to access this resource.
404	Not Found	The requested resource or endpoint does not exist.
409	Conflict	The request conflicts with the current state of a resource, such as creating a duplicate entry.
413	Content Too Large	The request body exceeds the endpoint’s size limit — for idea intake, 61 MB.
422	Unprocessable Entity	The request was well-formed but could not be completed. For example, a unique constraint was violated or an operation is not valid for the resource’s current state.
426	Upgrade Required	The client app version is too old. Update to the latest version to continue.
429	Too Many Requests	Rate limit exceeded. API requests are limited to 750 per minute, counted per Cloud and caller. Honor the Retry-After header before retrying.
451	Unavailable For Legal Reasons	The subscription has been suspended for a terms of service violation.
500	Internal Server Error	An unexpected error occurred on the server. If this persists, contact support.
502	Bad Gateway	An error occurred connecting to the database. This is typically temporary.
503	Service Unavailable	The server is temporarily unavailable due to maintenance or high load. Try again shortly.