Response Codes
The Response Codes below include Success Responses and Error Codes for which the response is uniquely described. DLR uses HTTP response status codes to the success or failure of your API requests. If your request fails, a DLR error code will be returned using the appropriate status code. Whenever you contact API Support for any specific error you are seeing in an API, provide the error code listed below.
In general, there are three code ranges you can expect:
2XX Success – Confirm that your request as expected.
| 200 | OK | The request has succeeded. |
| 201 | Created | The request has been fulfilled and resulted in a new resource being created. |
| 204 | No Content | The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. |
4XX Client error – Indicate an error due to the information provided.
| 400 | Bad Request | The request cannot be fulfilled due to bad syntax. The client SHOULD NOT repeat the request without modifications. |
| 401 | Unauthorized | Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". |
| 403 | Forbidden | The requested operation is not permitted for the user. |
| 404 | Not Found | The server has not found anything matching the Request-URI. |
| 405 | Method not allowed | Method Not Allowed response status code indicates that the request method is known by the server but is not supported by the target resource. |
| 406 | Not acceptable | The endpoint does not support the response format specified in the request Accept header. |
| 408 | Request Timeout | Request Timeout response status code means that the server would like to shut down this unused connection. |
| 413 | Payload Too Large | The HTTP 413 Payload Too Large response status code indicates that the request entity is larger than limits defined by server. |
| 415 | Unsupported media type | The endpoint does not support the format of the request body. |
| 429 | Too Many Requests | The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). |
5XX Server error – Indicate an error with DLR servers.
| 500 | Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request. |
| 502 | Bad Gateway | Server received an invalid response while acting as a gateway or proxy server. |
| 503 | Service Unavailable | The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. |
| 504 | Gateway Timeout | The server did not receive a timely response from an upstream server it needed to access in order to complete the request. |
The possible DLR error codes that can be returned, along with additional information about how to resolve them, have been compiled for each status code for your convenience.”
