Skip to content

All integrations

Connect Mailgun to ShipVitals

Deliveries, failures and complaints per domain, and the plan's cost

AvailableKey, not read-only · about 2 minutes

Connect Mailgun

What it reads

Read-only (Analyst) key
Reads domains and metrics.

Not read-only at Mailgun. Without role-based keys, the account key can also send mail and change settings; ShipVitals only reads domains and metrics.

What ShipVitals keeps: The key, encrypted, its region and the plan price you enter.

Every connector's scopes, on one page

How to connect

  1. Open Settings → API security in Mailgun.
  2. Create a key named ShipVitals, with the Analyst role if your plan offers roles.
  3. Copy the key.

About 2 minutes.

Open Mailgun

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

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
Mailgun 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 Mailgun. Connect it again; the history it brought in is kept.
Rate-limited
Mailgun asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
Quota reached
The account used up a Mailgun quota. The sync resumes when the quota resets.
Not found
Something the connection reads is gone from Mailgun: renamed, moved or removed. Review the connection's resources, or connect again.
Mailgun is unavailable
Mailgun is having trouble on its side. Check its status page; ShipVitals retries by itself.
Couldn't reach Mailgun
The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Mailgun is reachable.
An answer ShipVitals didn't expect
Mailgun 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 Mailgun. Check it against How to connect, and test again.

Docs