Skip to main content
This reference documents HTTP response status codes used by the Quivo API and explains when each code is returned

​
Overview

The Quivo API uses standard HTTP status codes to indicate the result of API requests. All responses follow REST conventions, where status codes communicate the success or failure of operations.
For detailed endpoint-specific response information, see the API Reference endpoints documentation.

​
Success Codes (2xx)

These codes indicate that a request was successfully received, understood, and processed.

​
200 OK

The request succeeded. The response body contains the requested data or the result of the operation. When returned:
  • Successful GET requests that retrieve data
  • Successful PUT or PATCH requests that update resources
  • Successful POST requests that return the created or updated resource

​
204 No Content

The request succeeded, but there is no content to return in the response body. When returned:
  • Some endpoints return 204 No Content for successful operations that don’t require a response body
  • DELETE operations that successfully remove a resource
  • Some PUT or PATCH operations that update resources without returning the updated resource

​
Client Error Codes (4xx)

These codes indicate that the client made an error in the request.

​
400 Bad Request

The request was invalid or malformed. When returned:
  • Invalid request body or parameters
  • Validation errors (for example, required fields missing or invalid values)
  • The request body or parameters could not be read
Example response:

​
401 Unauthorized

Authentication failed or the request lacks valid authentication credentials. When returned:
  • The access token is missing, unknown or expired (tokens expire after 1 hour)
  • The token request has a wrong client ID or client secret, or the credential is revoked or expired ({"error": "invalid_client"})
On API calls, the response includes the header WWW-Authenticate: Bearer. Example response:
When you receive a 401 Unauthorized error on an API call, request a new access token from POST /v2/oauth2/token and retry your request once. If the token request itself returns 401 with {"error": "invalid_client"}, a new token will not help: check the credential in The Connector. See the Authentication reference for detailed instructions.

​
403 Forbidden

The request was valid, but the server is refusing to fulfill it due to insufficient permissions or other access restrictions. When returned:
  • Access denied
  • Invalid signature
  • Missing authentication token (returned when the requested path does not exist)
  • The request was blocked by security rules
Example responses:

​
404 Not Found

The requested resource was not found. When returned:
  • The specified resource ID doesn’t exist
  • The endpoint path is incorrect
Example response:

​
405 Method Not Allowed

The HTTP method used is not allowed for the requested endpoint. When returned:
  • Using an unsupported HTTP method (for example, using PUT on an endpoint that only supports GET)
Example response:

​
413 Request Entity Too Large

The request body is too large. When returned:
  • The request body is larger than the allowed size

​
415 Unsupported Media Type

The request’s Content-Type is not supported. When returned:
  • The Content-Type header is missing or not supported

​
429 Too Many Requests

The client has exceeded the rate limit or quota. When returned:
  • Quota exceeded
  • Too many requests in a short time (rate limit)
The response includes the header Retry-After: 1. Wait at least that many seconds, then retry. See Rate limits.

​
Server Error Codes (5xx)

These codes indicate that the server encountered an error while processing the request.

​
500 Internal Server Error

The server encountered an unexpected error. When returned:
  • Unexpected server errors
  • The authentication service failed to process the request

​
501 Not Implemented

The requested functionality is not implemented. When returned:
  • The endpoint or feature is not yet available

​
503 Service Unavailable

The service is temporarily unavailable. When returned:
  • The token service is unavailable. The token endpoint returns {"error": "server_error"}. Retry with exponential backoff and a limit on the number of attempts.

​
504 Gateway Timeout

The server, acting as a gateway, did not receive a timely response from an upstream server. When returned:
  • The service did not respond in time

​
Error Response Format

The Quivo API uses different error response formats depending on where the error occurs:

​
Backend Errors

Errors returned by the Quivo API backend are typically simple strings:

​
Gateway Errors

Errors returned before a request reaches the Quivo backend, such as authentication and rate-limit errors, are formatted as JSON with a message (or Message) field:

​
Additional Response Codes

The Quivo API uses standard HTTP status codes. The codes documented above are the primary ones you’ll encounter. Other standard HTTP status codes can occur in specific scenarios.

​
Where to go next

Now that you understand HTTP response codes, continue with these guides:

Authentication

Learn about authentication and how to handle 401 Unauthorized errors.

Environments

Understand production and sandbox environments for testing error scenarios.