Reminder: Changes to Email API validation going live at 1:30pm EST

Changes to Email API validation – Action may be required

We're making some improvements to our API infrastructure and as a result, we're changing how we handle the validation of your API requests beginning today, November 28th at 1:30pm EST.

In the past, Postmark's email API has been pretty forgiving to requests that are passed incorrectly. In some cases, we've accepted invalid request headers, malformed JSON and mismatched field types — even if they didn't match our API documentation. Going forward, we'll start to reject invalid requests and return an error message instead.

If you see Postmark return error messages to API requests that were previously accepted without issues, please double-check your request JSON and ensure it is actually valid. The possible failures are:

- HTTP error 415: Unsupported Media Type. Solution: Check that the documented request headers are being passed (Content-Type and Accept)
- HTTP error 422. API error code: 403 — Invalid request fields(s) - {FIELD_NAME}. The {FIELD_NAME} will indicate where the invalid JSON is.
- HTTP error 422. API error code: 402 — Invalid JSON. The request payload is not valid JSON

We recommend using a tool such as [JSONLint](https://jsonlint.com/) to check your request payloads for any obvious validation errors, if that shows no issues then refer to our [API documentation](https://postmarkapp.com/developer/api/email-api) pages and make sure your request matches the schema(s) we are expecting.

Blackout periods were previously held on November 15th to help you catch any issues ahead of this cut over.

See our [full announcement here](https://postmarkapp.com/updates/changes-to-email-api-validation-action-may-be-required) for more details and some common reasons why your request might be invalid.

If you have any questions or need any help [let us know](https://postmarkapp.com/contact).