Postmark
Connect Postmark for premium email deliverability. Postmark is known for its strict sending policies and excellent inbox placement rates.
Prerequisites
- A Postmark account
- A server created in Postmark
- A verified sender signature or domain
Setup Steps
- 1
Get your server token
In Postmark, select your server and open the API Tokens tab. Copy the Server API Token. - 2
Add the provider in GoodPostal
Go to Configure > Email Providers, click "Add Provider", select Postmark, and paste your server token. - 3
Test the connection
GoodPostal verifies the token by querying the Postmark API. If it fails, ensure the token is for the correct server. - 4
Leave webhook setup switched on
Set up webhooks automatically is checked by default. Leave it checked and GoodPostal creates the Postmark webhook for you, as described below.
Server Token
Server Token: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Note: Use the Server API Token, NOT the Account API Token.
The Account token is for account-level operations only.Webhook Setup
You do not create the Postmark webhook yourself. GoodPostal creates it over the Postmark API when you save the connection, and secures it with Basic Auth credentials it generates. A webhook you add by hand carries no such credentials, so its events are rejected.
- 1
Leave automatic setup checked
When you add Postmark, the Set up webhooks automatically checkbox is already on. Leave it on and save the connection. - 2
GoodPostal configures Postmark for you
GoodPostal creates a webhook on your broadcast message stream, switches on all six event triggers listed below, and sets its own Basic Auth username and password on it. There is nothing to copy or paste. - 3
Re-run it whenever you need to
Open Configure > Email Providers, select your Postmark connection, and use Re-configure webhooks on the Webhook & Tracking card. Use this after you rotate a server token or if setup did not finish the first time.
Events GoodPostal Tracks
- Delivery
- Bounce
- Spam Complaint
- Open
- Click
- Subscription Change
Message Streams
Postmark uses message streams to separate transactional and broadcast (marketing) emails. GoodPostal sends through the broadcast stream by default. If your campaigns are being rejected, ensure your Postmark server has a broadcast message stream enabled.
Troubleshooting
- 422 error when sending - Check that your sender signature or domain is verified in Postmark
- Inactive recipient error - The recipient has previously bounced. Reactivate them in Postmark's suppression list if appropriate
- No broadcast stream - Enable a broadcast message stream in your Postmark server settings
See also: Webhook Configuration Guide