Verify your lemlist campaign leads without exporting

How it works

1. Ask for beta access (email support@simpleverifier.com from the address you sign in with), then sign in and open Integrations in your dashboard.
2. In lemlist, click your profile picture, open Settings > Integrations and click Generate a new API key.
3. Copy it straight away: lemlist shows the key only once.
4. Paste it and click Connect. We check it with lemlist before saving it.
5. Pick one of your campaigns. They are read live from your account.
6. Keep the default, writing each result into each lead's sv_status custom variable, or untick it to only check. Pause invalid leads in this campaign and Delete invalid leads from this campaign and Add invalid addresses to your lemlist unsubscribe list 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 lemlist API endpoints are used. To check a campaign, SimpleVerifier reads:

• GET /api/team checks the key when you connect and shows your team name. docs
• GET /api/campaigns lists your campaigns, 100 at a time. docs
• GET /api/v2/campaigns/{campaignId}/export/leads?state=all&format=json reads the campaign's leads (email, name, company and lead id) in one export. docs

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

• PATCH /api/leads/{leadId}/variables?sv_status=… updates the lead's sv_status variable; when the lead has none yet, POST on the same path adds it. docs
• POST /api/leads/pause/{leadId}?campaignId=… pauses an invalid lead in this campaign only, if you chose to. docs
• DELETE /api/campaigns/{campaignId}/leads/{leadId}?action=remove deletes an invalid lead from this campaign, if you chose to. docs
• POST /api/v2/unsubscribes/variables adds invalid addresses to your team's unsubscribe list, if you chose to. docs

• lemlist authenticates with HTTP Basic: an empty user name and your API key as the password, as its docs describe.
• lemlist allows 20 API requests every 2 seconds per key. We stay near 9 a second, so your other lemlist tools keep working; tagging makes one call per lead.
• Pausing and deleting act on the campaign you picked only. The unsubscribe list covers your whole lemlist team; lemlist lets you re-subscribe an address. All three are off by default and need a confirmation.
• Beta: not yet tested against a live lemlist account. The calls follow lemlist's published API reference, and lemlist'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 campaign leads in a lemlist campaign?

Connect your lemlist API key in the SimpleVerifier dashboard, pick the campaign and press Verify. SimpleVerifier reads the email addresses through the lemlist 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 lemlist?

Only what you pick for that run, and only after verification has completed. The default writes the result into each lead's sv_status custom variable and nothing else. Pause invalid leads in this campaign is opt-in: lemlist stops their steps in this campaign only. You can resume a lead in lemlist. Delete invalid leads from this campaign is opt-in: lemlist deletes those leads from the campaign you picked. Other campaigns are not touched. Add invalid addresses to your lemlist unsubscribe list is opt-in: The unsubscribe list covers your whole lemlist team, so no campaign contacts them. lemlist lets you re-subscribe an address 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 campaign 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 lemlist key stored?

It is checked with lemlist, 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.

Is the lemlist integration live?

It is in beta. It is built on lemlist's published API reference and the same verification and billing path as our other integrations, but it has not been tested against a live lemlist account yet, so the Connect button is only switched on for accounts on the beta list. To join, email support@simpleverifier.com from the address you sign in with. Until then, export the list as a CSV and upload it.

Does this use lemlist's own email verification credits?

No. SimpleVerifier reads the leads and checks each address itself, billed like a CSV upload on your SimpleVerifier plan. lemlist's own verifier and credits are not touched.