Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Status codes and errors


When you make a request to the v1/Emails endpoint, your payload undergoes strict validation. Twilio returns as many issues as possible in a single response to help you debug quickly.


Success response

success-response page anchor
Status codeDescriptionDetails
202AcceptedThe request was accepted and an Operation was created to track progress. The response body contains the operationId and a link to the Operation resource.

Status codeDescriptionAction
400Bad RequestThe request content was malformed or ambiguous. Check the response body for specific validation errors.
404Not FoundThe requested resource doesn't exist. Verify the resource ID in your request.
429Too Many RequestsToo many requests were sent to the API. Retry after the duration specified in the Retry-After response header.
500Internal Server ErrorThe Twilio API is experiencing server-side issues. Don't retry the request.
503Service UnavailableThe server is temporarily unavailable. Retry after the duration specified in the Retry-After response header.