Skip to main content

Prerequisites

Setup

1

Get your Postmark server token

In Postmark, open the server you send from and copy its Server API token.
2

Configure in Courier

Open the in Courier, enter your API token and From Address, then save.
Addressing a recipient and sending are the same on every email provider, so they are documented once: and .

Subject character limit

The Postmark API limits subject lines to ~60 characters. Emojis and special characters lower that limit because of encoding.

Overrides

covers the two levels and which one wins. lists the fields every email provider takes. A provider override changes what Courier sends to Postmark’s Email API. This example adds a MessageStream and an attachment:
Overrides are deep-merged into the request. Fields you set replace their counterparts, and everything you leave out is still sent. For every option, see the Postmark API docs. override.config.fromAddress swaps the sender for one message, in place of the From Address saved on the integration. A template From value or a channels.email.override.from still wins over it. covers the order.

Using Postmark templates

The message.providers.postmark.override.config property replaces Courier templates with Postmark’s Templates API. Include the https://api.postmarkapp.com/email/withTemplate URL in the config object, and TemplateId and TemplateModel in the body.
With Postmark templates, your request must use a template parameter, not content. Otherwise content takes precedence over the Postmark override. An invalid template_id causes an error.

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.