Connect Postmark to ShipVitals
Sends, bounces and spam complaints per server (delivered estimated as sent less bounces), and the plan's cost
BetaKey, not read-only · about 2 minutes
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- Account token or server token
- An account token lists every server and your sending domains; a server token reads its one server's stats
Not read-only at Postmark. Postmark's tokens can't be limited to reading: a server token can also send, and an account token can manage servers and domains. ShipVitals only reads servers, domains, message streams and outbound stats.
What ShipVitals keeps: The token, encrypted, and the plan details you enter.
How to connect
- In Postmark, open the API Tokens tab: your account's for every server, or a server's for that one.
- Copy the token. Postmark's tokens can't be limited to reading, so an account token is best kept to ShipVitals and your own tools.
About 2 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Health.
Figures it fills
- Emails sent
- Emails delivered
- Emails bounced
- Spam complaints
- Postmark emails this month
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Postmark didn't accept the token: it may have been reset. Copy the account's or a server's token from its API Tokens tab again.
- A permission is missing
- What ShipVitals has can't read everything it needs. Add the permissions under What it reads, or create a new key with them, and test again.
- Access removed
- ShipVitals' access was removed in Postmark. Connect it again; the history it brought in is kept.
- Rate-limited
- Postmark is asking for fewer requests. ShipVitals tries again shortly.
- Quota reached
- The account used up a Postmark quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Postmark: renamed, moved or removed. Review the connection's resources, or connect again.
- Postmark is unavailable
- Postmark is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Postmark
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Postmark is reachable.
- An answer ShipVitals didn't expect
- Postmark answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- A field in the connection doesn't work with Postmark. Check it against How to connect, and test again.