Cold email compliance check
contact_checkIs it legal to send a cold or marketing email to this person? Check before the first email to any new lead, prospect or contact who is not already a customer, one call per address: a compliance check for B2B sales outreach, prospecting and lead lists. Whether it is allowed, or needs consent first, turns on facts you cannot see in the address, such as whether a UK recipient is a limited company or a sole trader, so it looks them up live (UK Companies House) and applies UK PECR and GDPR, US CAN-SPAM, Canadian CASL, German UWG, French CPCE, Australia's Spam Act, Ireland's ePrivacy Regulations, the Dutch Telecommunicatiewet, Spain's LSSI, Italy's Privacy Code, Latvia's Information Society Services Law and the UAE's PDPL. Returns a verdict (ok_to_email, consent_needed, blocked or unknown), the rule quoted with its source, the footer requirements (who you are, a postal address, an unsubscribe or opt-out), the next step and a signed receipt id to show a client or auditor. Each charged call uses one check from your allowance (free daily allowance, no sign-in); unknown-country answers and one qualifying re-check within a day are free, up to a combined limit of 50 a day. Nothing is sent to the recipient. Not for transactional emails such as invoices, receipts or password resets. To check the email itself, send the draft as email ({ subject, body, from_name, from_email }); the answer then gains email_check, saying whether the footer has an opt-out, the sender's identity and, where the rule needs one, a postal address. The draft is not stored. Addresses on the key's opt-out list (see suppress_contact) come back blocked and free.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | The draft email, if you want the answer to say whether its footer meets the rule for the recipient's country. The body is not stored. | ||
| pitch | No | What the email offers, in a few words, for example 'bookkeeping software for dental practices'. Used to judge relevance to the recipient's role. | |
| suppressed | No | True if the recipient is on your own do-not-contact list. | |
| company_name | No | The recipient's company or organisation name if you know it, for example from your CRM. For UK recipients it is used to search Companies House when the domain alone does not find the company. A company is only used when other evidence links it to the recipient, such as one of its officers matching the recipient or the website naming it. | |
| address_source | No | Where the address came from: 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 affects the verdict, so do not assume published. Default unknown. | |
| company_number | No | UK company number if known (8 characters), so the register can confirm the company. | |
| pitch_relevant | No | True if the pitch relates to the recipient's job or business, false if it does not. | |
| recipient_name | No | The recipient's full name if you know it, for example Jane Smith. For UK recipients it is matched against a company's current officers at Companies House. Precleared does not store it. | |
| sender_country | No | Country the sending business is based in: GB, US, AE (United Arab Emirates) or CA (Canada). Canadian senders must also meet CASL. Not the recipient's country. Default GB. | |
| recipient_email | No | The recipient's email address. Give this or recipient_domain. | |
| recipient_domain | No | The recipient's domain when you have no email address, for example acme.co.uk. | |
| existing_customer | No | True if the recipient has bought from you before. Default false. | |
| recipient_country | No | Two-letter country code of the recipient if known, for example GB or DE. Otherwise it is worked out from the domain, company records and the company's website. | |
| default_recipient_country | No | Two-letter country code to use only when the recipient's country can't be worked out from recipient_country, the domain, company records or the company's website, for example US if all your prospects are in the US. recipient_country always wins. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| facts | No | Facts gathered about the recipient. | |
| usage | No | Allowance left for the caller. | |
| charged | No | ||
| reasons | No | The rule that matched, with its text and source, then any notes. | |
| receipt | No | Signed receipt for this check. | |
| verdict | Yes | The answer for this recipient. | |
| next_step | No | What to do next. | |
| confidence | No | high, medium or low. | |
| disclaimer | No | Fixed disclaimer line. | |
| email_check | No | Present when you sent email: whether the draft's footer has what the rule needs. | |
| footer_text | No | What the email's footer must include, if the rule sets requirements. | |
| held_because | No | ||
| rules_applied | No | Rule keys used. | |
| rules_version | No | Version of the rule set used. | |
| free_recheck_of | No | ||
| possible_company | No |