The CallRail API returns standard HTTP success or error status codes. For errors, extra information about what went wrong will be encoded in the response as JSON.
For more information, check out the API v3 docs.
Response codes
Below, you'll find a list of the HTTP status codes and a description of each.
| Code | Description |
|---|---|
| 200 | OK – The request has succeeded. |
| 201 | Created – The request has been fulfilled, and a new resource has been created. |
| 204 | No Content – The server successfully processed the request and is not returning any content. |
| 400 | Bad Request—The server cannot or will not process the request due to something perceived to be a client error (e.g., malformed request syntax or invalid request parameters). |
| 401 | Unauthorized – The request has not been processed because it lacks a valid API key for the target resource. |
| 403 | Forbidden – The server understood the request but refused to authorize it. |
| 404 | Not Found – The server did not find the target resource or endpoint. |
| 405 | Method Not Allowed – The HTTP method received in the request is known by the origin server but not supported by the target resource. |
| 406 | Not Acceptable – Request parameters were supplied in an unacceptable format. For GET requests, verify that parameters are sent as part of the URL. For other requests, verify that parameters are sent as JSON. |
| 422 | Unprocessable Entity—The server cannot or will not process the request due to something perceived to be a client error (e.g., malformed request syntax or invalid request parameters). |
| 429 | Too Many Requests – The User or Agency has sent too many requests in a given amount of time (See Rate Limiting). |
| 500 | Internal Server Error – The server encountered an unexpected condition that prevented it from fulfilling the request. If this error persists, please contact support. |
| 503 | Service Unavailable – The CallRail API is temporarily offline for maintenance, or the server is overloaded. Please try again later. |