Errors

The 360X API uses conventional HTTP response codes to indicate the outcome of an API request. Response codes can be grouped into the following categories:

2xx: The request was successful.

4xx: An error occurred due to the information provided, e.g., missing or incorrect parameters.

5xx: Those errors are returned if there was an error in 360X servers.

360X API error responses all follow a standard format. They include the HTTP response code, the reason for the error, and a unique ID for use with 360X customer support.

Error response parameters

Parameter	Type	Description
`id`	string	Unique ID of the error. Submit this ID when filing a ticket with 360X customer support.
`statusCode`	string	The HTTP status code of the error
`timestamp`	string	Timestamp
`message`	string	Description message.
`error`	string	Detailed description.
`path`	string	containing information about which attribute on a model caused the error

Example error: 400 Bad Request:

        {
            "id": "93aa74d5-8caf-473f-af2f-42cf806ddfdc",
            "timestamp": "2011-10-05T14:48:00.000Z",
            "statusCode": 401,
            "message": "Invalid Token",
            "error": "Token is invalid",
            "path": "/api/v1/participant/offers"
        }

List of error codes

Most model validation errors result in invalid_model errors (as opposed to validation_error errors) and contain a message that explains the cause of the error.

NOTE
The 360X API will return different errors at different stages of the validation process, which may abort the process. For example, it will raise a 403 Forbidden or 404 Not Found error before validating any models. If this happens, then the API will not return any information about invalid model attributes.

Status Code	JSON Code	Title	Detail
400 Bad Request	string	Validation Error
401 Unauthorized	string	Invalid Token	Token is invalid.
403 Forbidden	string	Unauthorized Action	Authorization is required.
404 Not Found	string	Not Found
429 Too Many Requests	string	Too Many Requests
500 Internal Server Error	object	Generic Error
502 Internal Server Error	object	Bad Gateway
503 Internal Server Error	object	Connection Error
504 Internal Server Error	object	There was a generic error

Requesting support from 360X

If you're encountering errors and you'd like to request support from 360X, please pay attention to the following points:

360X needs the endpoint URL, error code, and unique request ID to handle any support requests.

360X stores logs for only 30 days.

360X doesn't store the request's payload in the logs.

Error response parameters#

List of error codes#

Requesting support from 360X#

Error response parameters

List of error codes

Requesting support from 360X