Mailgun Integration
BetaNative connector
Import Mailgun bounces and complaints, and verify mailing-list members with results stored as member variables.
Connect Mailgun
Dashboard → Integrations → Mailgun
DashboardBounce guarantee
Connect your sending provider and bounced "deliverable" addresses are refunded automatically
How it worksConnect with
API key
Category
Email Sending (bounce feeds)
Write-back
Fields
Bounce feed
Yes
How to Connect
In RocketVerifier open Dashboard → Integrations → Mailgun, paste the credentials below (a Mailgun private API key, region and sending domain) and click Connect. They are validated against the platform before anything is saved.
| Field | Required | Where to find it |
|---|---|---|
| API key | Required | Mailgun → API Security → private API key. |
| Region | Required | US (api.mailgun.net) or EU (api.eu.mailgun.net). |
| Sending domain | Optional | e.g. mg.example.com. Bounces and complaints are imported from this domain. |
| Webhook signing key | Optional | Sending → Webhooks → HTTP webhook signing key. Needed to accept real-time webhooks. |
Credentials are stored encrypted and are only ever sent to the platform's own API hosts.
What It Syncs
Sources
Any mailing list.
Incremental syncs
Mailgun has no change filter, so an incremental sync reads the whole source; contacts verified within the skip window are still skipped.
Schedules & Credits
- Schedule: Manual only, Daily, Weekly or Monthly. Each run syncs the source chosen in the settings; Sync now starts one immediately. Only one sync runs per integration at a time.
- Mode: Full re-checks every contact in the source except those verified in the last N days (default 30, 0-365); Incremental only checks contacts changed since the last sync.
- Each sync creates a regular verification job: 1 credit per unique address, and
unknownresults are refunded when it completes. If the balance is too low the sync stops withinsufficient_creditsbefore anything is charged. - Results are written back when the job completes; the sync history in the dashboard shows updated, failed and skipped counts per run.
Write-back
Fields ("Write status fields")
rv_email_statusrv_email_sub_statusrv_email_scorerv_verified_at
Member variables (vars).
Status values are deliverable, undeliverable, risky and unknown (disposable addresses are undeliverable, catch-all addresses unknown). Sub-status is a sub_status value (none when there is no extra detail), score is 0-100 and verified-at is an ISO 8601 UTC timestamp.
Action Rules
In the integration settings, pick an action per result: Invalid, Disposable, Risky, Catch-all, Unknown or Valid. Actions run after the field/tag write-back.
Unsubscribe
Sets the member to subscribed=no.
Bounce Feed Setup
The webhook URL is shown on the integration page in the dashboard and has the form:
Copy the webhook URL shown on the integration page in the dashboard.
In Mailgun open Sending → Webhooks for the sending domain and add the URL for the Permanent failure, Temporary failure and Spam complaints events.
Paste the domain's HTTP webhook signing key into the integration settings. Deliveries are checked against it; replays and deliveries older than 12 hours are rejected.
- Permanent failure → hard bounce, temporary failure → soft bounce, complained → complaint.
- With a sending domain set, RocketVerifier also reads the domain's bounces and complaints once a day.
- Hard bounces and complaints are added to your auto-managed suppression list Bounces & complaints (auto); soft bounces are recorded only. Hard bounces of addresses we verified as deliverable are refunded under the bounce guarantee.
Beta: the Mailgun connector is new. Sync reports list every contact that could not be updated; please tell us if something looks wrong.
Need Help?
Having trouble connecting Mailgun? We're here to help.
