Verify your Mailchimp subscribed contacts without exporting

How it works

1. Sign in (free accounts work) and open Integrations in your dashboard.
2. In Mailchimp, click your profile icon, then Profile > Extras > API keys, and click Create A Key.
3. Copy the whole key, including the part after the dash (like -us21): that is your account's datacenter.
4. Paste it and click Connect. We check it with Mailchimp before saving it.
5. Pick one of your audiences and segments. They are read live from your account.
6. Keep the default, writing each result into the sv_status merge field, or untick it to only check. Unsubscribe invalid contacts and Archive invalid contacts stay off until you tick them and confirm.
7. Read the confirmation, which shows what the run costs on your plan, and press Verify. Follow it in History and download the results there.

What we read and what we change

Only documented Mailchimp API endpoints are used. To check a audience or segment, SimpleVerifier reads:

• GET /3.0/ping checks the key when you connect. docs
• GET /3.0/lists lists your audiences with their size. docs
• GET /3.0/lists/{list_id}/segments lists each audience's segments and tags. docs
• GET /3.0/lists/{list_id}/members?status=subscribed pages through an audience's subscribed contacts, 1,000 at a time. docs
• GET /3.0/lists/{list_id}/segments/{segment_id}/members pages through a segment's contacts; only subscribed ones are checked. docs
• GET /3.0/lists/{list_id}/merge-fields checks whether the SVSTATUS merge field exists. docs

Only for the actions you choose, and only once verification has completed, it calls:

• POST /3.0/lists/{list_id}/merge-fields creates the hidden text merge field sv_status (tag SVSTATUS) the first time, only when you ticked the merge field option. docs
• POST /3.0/batches sends the changes in batches of 500: a PATCH of SVSTATUS per contact, a PATCH to unsubscribed, or a DELETE (which archives) for invalid contacts you chose to act on. docs
• GET /3.0/batches/{batch_id} waits for Mailchimp to finish each batch and counts failed operations. docs

• Only subscribed contacts are pulled. Unsubscribed, cleaned, pending and archived contacts are not checked and not changed.
• Unsubscribing is hard to undo: Mailchimp does not let an API resubscribe someone without their consent. Archiving is gentler: archived contacts stop counting toward your plan and can be added back. Both are off by default and need a confirmation.
• A new merge field uses one of your audience's merge field slots. Build a segment where sv_status is invalid to exclude those contacts from campaigns without changing their status.
• Mailchimp allows 10 simultaneous API connections per account; we use one, so your other apps keep working.
• Not yet tested against a live Mailchimp account: the calls follow Mailchimp's published Marketing API reference, and Mailchimp's real API rejects a wrong key as expected. If something behaves differently in your account, write to support@simpleverifier.com.

Common questions

How do I verify the subscribed contacts in a Mailchimp audience or segment?

Connect your Mailchimp API key in the SimpleVerifier dashboard, pick the audience or segment and press Verify. SimpleVerifier reads the email addresses through the Mailchimp API and checks each one with its mail server, as a normal list job: results show in History as valid, risky or invalid with a reason, with the same downloads as an uploaded CSV.

What does SimpleVerifier change in Mailchimp?

Only what you pick for that run, and only after verification has completed. The default writes the result into the sv_status merge field and nothing else. Unsubscribe invalid contacts is opt-in: Mailchimp marks them unsubscribed in this audience, so campaigns skip them. Mailchimp does not let an API resubscribe them later without their consent. Archive invalid contacts is opt-in: Mailchimp archives them in this audience: they stop counting toward your contact limit and keep their history, and you can add them back later. These act on invalid contacts only, never risky ones, and the dashboard asks you to confirm first. Only a confirmed mailbox is written as valid; anything unconfirmed is written as risky.

What does it cost?

The same as uploading the addresses as a CSV: one check per distinct address. Free accounts use their free checks (if the audience or segment is bigger than what is left, the first addresses are checked and the rest stay unchecked and untouched). Paid plans use their monthly allowance or full-speed volume. Up to 100,000 contacts per run. Paid plans can also auto-verify new contacts once a day, up to 10,000 a day.

How is my Mailchimp key stored?

It is checked with Mailchimp, encrypted with AES-256-GCM using a server-side key and stored on our server. It is never shown again, never sent back to your browser and never written to logs. Removing it in the dashboard deletes it and skips any pending write-back.

Why a pasted key and not a one-click Connect button?

A one-click OAuth app needs a listed Mailchimp app, which we have not published yet. Until then you paste a key from your own account, which you can revoke in Mailchimp at any time. OAuth is a planned upgrade.

Why was my Mailchimp key rejected?

Mailchimp keys end in a datacenter like -us21; without it we cannot reach your account, so paste the whole key. A 401 means the key is wrong or was disabled under Profile > Extras > API keys.