API Errors

If your CleverTap API request fails, you will receive an error response, including a response code and a message explaining the reason for the error.

Generic API Codes

The following response code pattern applies across all CleverTap API requests:

2xx codes indicate that the request was successfully processed. The following are the most common 2xx status codes:

Status Code	Text	Description
200	OK	The proposal has been successfully processed.
201	Created	The request has been fulfilled, creating one or more new resources.
202	Accepted	The request has been received for processing but has yet to be completed.
204	No Content	The server has successfully fulfilled the request, and there is no additional content to send in the response payload body.

4xx codes indicate an error in either the request or the data. The following are the most common 4xx status codes:

Status Code	Text	Description
400	Bad Request	Invalid parameter passed.
401	Unauthorized	Invalid credentials or URL.
403	Forbidden	Operation is not allowed.
404	Not Found	The resource does not exist or cannot be found.
405	Method Not Allowed	The server knows the request method but is not supported by the target resource.
409	Conflict	Resource already exists.
429	Too Many Requests	API Request limit exceeded

5xx codes indicate that there was an internal error with the server. The following are the most common 5xx status codes:

Status Code	Text	Description
500	Internal Server Error	An error within the API.
503	Service Unavailable	The system is unavailable. Try again later.

For more details on the REST API error codes, refer to REST API documentation.