Docs · lemlist

Check leads before they enter lemlist

lemlist sends to whoever you add to a campaign. Put a Precleared check in front of it and only leads that are ok to cold email get added, each with a signed receipt.

Pick your builder

Builder	How
Clay	An HTTP API column, then Clay's Add Lead to Campaign, only run if the verdict is ok_to_email
Make	An HTTP module, a router, then an HTTP module to lemlist
Zapier	Webhooks by Zapier, a filter, then lemlist → Add Lead to Campaign
n8n	Download the lemlist workflow

Calling the APIs yourself

Check the address.

curl https://precleared.dev/api/v1/check \
  -H "Authorization: Bearer pc_live_..." \
  -H "Content-Type: application/json" \
  -d '{"recipient_email":"jane@acme.co.uk","address_source":"published","sender_country":"GB","pitch":"route-planning software"}'

Only if verdict is ok_to_email, add the lead.

curl "https://api.lemlist.com/api/campaigns/YOUR_CAMPAIGN_ID/leads/?deduplicate=true" \
  --user ":YOUR_LEMLIST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jane@acme.co.uk",
    "firstName": "Jane",
    "companyName": "Acme Ltd",
    "precleared_receipt": "cc_rcpt_..."
  }'

Your campaign id starts with cam_ and is in the campaign's URL in lemlist. lemlist keeps any extra field as a custom variable, so precleared_receipt is available as {{precleared_receipt}}. deduplicate=true refuses a lead who's already in another of your campaigns.

Before you send

Make sure your lemlist campaign covers what footer_text describes, usually who you are, a postal address and a simple way to opt out. Keep precleared_receipt with the lead: precleared.dev/r/ followed by the id shows why the email was allowed.

All recipes

Decision support with sources, not legal advice.