This section contains a list of common status codes you'll see in response from the Twilio API, and what they mean.
HTTP status codes
Here are some of the Twilio Rest API error status codes.
| Code | Meaning | Description |
|---|---|---|
| 200 | OK | The request was successful and the response body contains the representation requested. |
| 201 | CREATED | The request was successful, we created a new resource and the response body contains the representation. This should only appear for POST requests. |
| 202 | ACCEPTED | The request has been accepted for processing, but the processing has not been completed. |
| 204 | OK | Used with the DELETE method. The request was successful; the resource was deleted. |
| 302 | FOUND | A common redirect response; you can GET the representation at the URI in the Location response header. |
| 304 | NOT MODIFIED | Your client's cached version of the representation is still up to date. |
| 401 | UNAUTHORIZED | The supplied credentials, if any, are not sufficient to access the resource. |
| 403 | Forbidden | The request is not authorized |
| 404 | NOT FOUND | The request resource wasn't found. |
| 405 | NOT ALLOWED | Typically means you can't DELETE the resource. |
| 429 | TOO MANY REQUESTS | Your application is sending too many requests too quickly, and you are reaching the concurrency limit of the Twilio API. |
| 500 | SERVER ERROR | We couldn't return the representation due to an internal server error - this one is Twilio's fault! |
| 503 | SERVER UNAVAILABLE | We are temporarily unable to return the representation. Please wait for a bit and try again |
See the full list of other error codes on Twilio in the Error and warning dictionary