API Error and Response Codes
HTTP Response Codes
The API will return one of the following HTTP response codes with each request. If the response is anything other than a 200 OK, an error code and message will also be returned (see API Response Errors, below).
The API will return one of the following HTTP response codes with each request. If the response is anything other than a 200 OK, an error code and message will also be returned (see API Response Errors, below).
-
200 OK: Success!
-
400 Bad Request: The request cannot be fulfilled due to bad syntax or an invalid parameter.
-
401 Unauthorized: Invalid authentication credentials. For example, a request to the API with an invalid API Key
-
403 Forbidden: Valid request but it has been rejected by the server. For example: a request to cancel a send that was already sent; a request to delete a blast that has started sending; etc.
-
404 Not Found: Resource was not found. For example: request to get a blast that doesn’t exist
-
405 Method Not Found: A request was made of a resource using a request method not supported by that resource.
-
409 Method Not Found: The web server notes that the request submitted by the client can not be completed because it conflicts with an established ruleset.
- 429 Too Many Requests: You have exceeded the limit of requests per minute for the given type (GET or POST) and endpoint. For limit details, see the Rate Limiting section on the API Technical Details page.
-
500 Internal Server Error: Something is broken on the system’s side. This shouldn’t happen normally.
API Response Errors
This is a list of global error codes you can receive from the API. Each endpoint documentation page also lists endpoint-specific error codes and messages.1: Unsupported HTTPS method
The API only supports GET, POST or DELETE, and some calls only support one or the other. This means you are trying to access an API call with an HTTPS method you can’t use.