Error responses for all routes
Here you will find details of the HTTP error responses that could occur with any route. Responses specific to a particular route will be found in the section for that route.
Documentation moved to new platform! The Serverside.ai documentation is now available at: https://help.equativ.com/serversideai. Please update your bookmarks.
The content in the article below (and this legacy platform) is no longer being maintained — use the new platform https://help.equativ.com/serversideai instead.
This legacy portal will be permanently shut down on February 1, 2026.
400 - Bad Request
The server could not understand the request due to invalid syntax.
Example
401 - Unauthorized
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
Example
403 - Forbidden
The client does not have access rights to the content, i.e. they are unauthorized.
Example
{
"type": "Forbidden",
"code": 403,
"message": "Invalid API key.",
"name": "ForbiddenError"
}404 - Not Found
The requested route or resource could not be found.
Example
422 - Unprocessable Entity
Usually means that a required parameter is missing from the request body.
500 - Internal Server Error
The server has encountered a situation it doesn't know how to handle. There will be further details in the response.
Example
Last updated