Connect MailerSend to ShipVitals
Sends, bounces and complaints per domain, and the plan's cost
AvailableRead-only key · about 2 minutes
What it reads
- Analytics: read
- Daily counts per domain
- Activity: read
- What happened to each send
- Domains: read
- Your sending domains
Read-only: ShipVitals can't change anything at MailerSend.
What ShipVitals keeps: A read-only token, encrypted, and the plan price you enter.
How to connect
- Open Integrations → API tokens in MailerSend.
- Generate a token named ShipVitals.
- Give it read access to the permissions listed below, and nothing else.
- Copy the token. It starts with mlsn., and MailerSend shows it once.
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
- quota.api.remaining
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
- MailerSend no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
- 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 MailerSend. Connect it again; the history it brought in is kept.
- Rate-limited
- MailerSend asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
- Quota reached
- The account used up a MailerSend quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from MailerSend: renamed, moved or removed. Review the connection's resources, or connect again.
- MailerSend is unavailable
- MailerSend is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach MailerSend
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that MailerSend is reachable.
- An answer ShipVitals didn't expect
- MailerSend 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 MailerSend. Check it against How to connect, and test again.