Docs · Recipes
Check leads in Amplemarket before the first email
Amplemarket's HTTP Request Stage calls a web address and lets the lead carry on only when the answer is a success. Make Precleared's gate the first stage of a sequence, and a lead reaches your first email only when a cold email to them is allowed. Leads that Duo adds to the sequence go through the same stage, so they're checked too.
How the gate answers
| Precleared's verdict | Gate answer | What Amplemarket does |
|---|---|---|
ok_to_email | 200 | Moves the lead to the next stage |
consent_needed, blocked or unknown | 422 | Removes the lead, with the reason "HTTP Request Failed" |
| No verdict: a bad key, checks used up or an error | 400, 401, 402, 429 or 500 | Removes the lead |
Amplemarket reads only the status code, so it can't show you why a lead was removed. Step 4 covers that.
1. Get a key
A sequence can check far more leads than the keyless allowance of 10 a day, so use a key. Every new key starts with 14 days at 100 checks a day, then 25 a day, no card needed. Get a free key. For more, £15 a month keeps 100 a day, or a pack adds checks that never expire.
When the day's checks run out, the gate answers 402 or 429 and Amplemarket removes the leads it couldn't check. Keep enough checks for the number of leads your sequences start each day.
2. Add the stage
- Open the sequence and add an HTTP Request stage as the first stage, before the first email.
- Method: POST.
- URL:
https://precleared.dev/api/v1/gate?src=amplemarket - Headers. Amplemarket needs at least one; add both.
| Header | Value |
|---|---|
| Authorization | Bearer pc_live_... |
| Content-Type | application/json |
- Body:
{
"email": "{{email}}",
"company_name": "{{company_name}}",
"sender_country": "GB",
"address_source": "unknown",
"pitch": "route-planning software for delivery firms"
}Change sender_country to US if your business is based in the US, or AE for the UAE, and pitch to what you offer. Set address_source to how you got the leads in this sequence: published (on their website, profile or a directory), bought (a purchased list), scraped (collected by a tool), given (the person gave it to you) or unknown. It changes the verdict, so only say published when the people put the addresses on their own website or a public listing.
- Leave the stage's advanced settings as they are, so a lead that fails the check is removed. If you let failed leads continue, the check does nothing.
3. Test it
Amplemarket's test sends a made-up lead, and Precleared holds a made-up address, so expect the test to fail with 422 or 400. That's the gate doing its job, not a setup problem. To see a pass, put one real lead you know is fine, such as a US company address, into a paused copy of the sequence and watch it move past the stage.
4. See why a lead was removed
Check the removed lead's address at precleared.dev, or send the same body to https://precleared.dev/api/v1/check. The answer gives the verdict, the rule with its source and the next step. For consent_needed that's usually asking for consent through their contact form or a call. For unknown, add a company number or recipient country, or try again in a few minutes if Companies House was busy.
Footers
A lead that passes still needs a lawful footer in every email: usually who you are, a postal address and a simple way to opt out. Set it once in your sequence's signature. The country guides say what each country requires.
Every check has a signed receipt. Open precleared.dev/r/ followed by its id to show a client why an email went out.
Decision support with sources, not legal advice.