Status Codes & Errors

The Mailjet API uses conventional HTTP response codes to indicate the success or failure of an API request. Overall:

  • Codes in the `2xx` range indicate that the request was processed successfully.
  • Codes in the `4xx` range indicate that that there was an error with the request (e.g. unauthorized access, a required parameter is missing etc.).
  • Codes in the `5xx` range indicate that there is an issue with Mailjet's servers. Those are quite rare.

Error responses will usually include an Error Identifier, Error Message and Status Code.

Below you can see a list of status codes returned by the Mailjet API to notify you of the success of failure of your requests:

Code

Reason

Description

200

OK

All went well. Congrats!

201

Created

The `POST` request was successfully executed.

204

No Content

No content found or expected to return. Returned when a `DELETE` request was successful.

304

Not Modified

The `PUT` request didn't affect any record.

400

Bad Request

One or more parameters are missing or maybe misspelled (unknown resource or action).

401

Unauthorized

You have specified an incorrect API Key / API Secret Key pair. You may be unauthorized to access the API or your API key may be inactive. Visit API keys Management section to check your keys.

403

Forbidden

You are not authorized to access this resource.

404

Not Found

The resource with the specified ID you are trying to reach does not exist.

405

Method Not Allowed

The method requested on the resource does not exist.

429

Too Many Requests

Oops! You have reach the maximum number of calls allowed per minute by our API. Please review your integration to reduce the number of calls issued by your system.

500

Internal Server Error

Ouch! Something went wrong on our side and we apologize! When such error occurs, it will contain an error identifier in it's description (e.g. "ErrorIdentifier" : "D4DF574C-0C5F-45C7-BA52-7AA8E533C3DE"), which is crucial for us to track the problem and identify the root cause. Please contact our support team, providing the error identifier and we will do our best to help.