Hevo uses conventional HTTP response codes to indicate the success or failure of an API request. The response codes available for an endpoint are listed in its detailed view. When you try out an endpoint, the response also mentions the associated code.
Use the following as a quick reference for understanding the API response:
Response Code Range
The API request was successful.
There is an error in the request. For example, the request body is not formed correctly, or the API access token is invalid. The exact response code provides more detail.
There is a problem with Hevo’s servers. This is a rare occurrence.
The following is the list of response codes based on the API method:
The request was successful and data has been returned.
The request was successful, and there was no data to be returned.
A generic success response that contains some data in the response body.
A new entity was created. The response body contains the newly created data.
The action performed was successful, and there was no data to be returned.
The data was successfully updated and relevant data was returned in response.
The request was successful and no data was expected to be returned.
The entity was deleted successfully, or the entity was already deleted.
The request was unacceptable, often due to incorrect parameters or a missing required parameter.
The API key and secret is not valid.
The user associated with the authenticating API key does not have permissions to perform the API request.
The requested resource does not exist.
500, 502, 503, 504
Something went wrong at Hevo's end.
(A rare occurrence!)
A unique code for an individual error type.
An optional identifier used by Hevo for logging.
A human-readable message providing details about the error.
An indicator specifying whether the request was successful or not. This is always false in case of failures.