# 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

| Status code | Description | Details                                                                                                                                                     |
| ----------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `202`       | Accepted    | The request was accepted and an Operation was created to track progress. The response body contains the `operationId` and a link to the Operation resource. |

## Error responses

| Status code | Description           | Action                                                                                                           |
| ----------- | --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `400`       | Bad Request           | The request content was malformed or ambiguous. Check the response body for specific validation errors.          |
| `404`       | Not Found             | The requested resource doesn't exist. Verify the resource ID in your request.                                    |
| `429`       | Too Many Requests     | Too many requests were sent to the API. Retry after the duration specified in the `Retry-After` response header. |
| `500`       | Internal Server Error | The Twilio API is experiencing server-side issues. Don't retry the request.                                      |
| `503`       | Service Unavailable   | The server is temporarily unavailable. Retry after the duration specified in the `Retry-After` response header.  |