Email marketing

Check email domains, links and domain age in ActiveCampaign

Screen the domains on your ActiveCampaign contacts so lists stay clean of disposable and role addresses before a campaign or automation sends to them.

Why the data matters in ActiveCampaign

ActiveCampaign sends campaigns and automation emails to whatever sits on a list, so bad addresses show up as bounces and unopened mail that lower how your sending looks across every later send. A disposable sign-up also enters an automation, takes a tag and moves down a path that was meant for a real buyer.

What LookValid checks

LookValid checks for ActiveCampaign
Product	What it does here	Credits
Email Domain Check	Returns a good, risky or undeliverable signal from the domain records behind an address, with the reasons. It never contacts a mail server. Flags disposable domains, free providers and role mailboxes so a tag or a branch in an automation can keep them apart.	1 credit per address checked
Link Safety Check	Checks the domain of a link you plan to send against a list of reported malicious domains. A clean result is not a guarantee of safety.	1 credit per URL checked (a check that cannot run is free)
Domain Age	Returns the registration date and age of a sender or lead domain, useful when you review brand-new domains in a sign-up list.	2 credits per registered domain (unregistered domains are free)

Connect it in four steps

Create a LookValid account, then make a key in the dashboard under API keys.
Store the LookValid key as a secret in the automation tool that runs the HTTP step and send it in the Authorization header. Your ActiveCampaign key is separate: each user has one under Settings, Developer, and it travels in a header named Api-Token.
Send the contact email in the JSON body to the email-domain-check endpoint, and branch the flow so a found:false answer or an error response ends the path without changing the contact.
Send the three values with PUT /contacts/{id} on your account api-us1.com address, inside contact.fieldValues as pairs of a numeric field id and a value, so create the three custom fields first and look up their ids. Automation conditions can then read those fields.

An HTTP request step in an automation tool, started by an ActiveCampaign webhook for a new or updated contact and followed by a call that updates that contact. The call is POST https://YOUR_API_HOST/v1/email-domain-check and costs 1 credit per address checked.

HTTP request step

1POST https://YOUR_API_HOST/v1/email-domain-check
2Authorization: Bearer {{LOOKVALID_API_KEY}}
3Content-Type: application/json
4
5{
6  "email": "{{value}}"
7}

Where to read each value in the LookValid response
Response field	Goes into
data.deliverability_signal	EMAIL_SIGNAL
data.disposable	DISPOSABLE_DOMAIN
data.free_provider	FREE_PROVIDER

The recipe returns nothing when the lookup finds nothing, which costs no credits for this product, and stops with the error code and fix on a failed request.

Without code

This route needs no code and no dedicated app, only a generic HTTP request step in the automation platform you already use. ActiveCampaign webhooks can fire on the subscribe and update events, so point one at that platform, call the LookValid endpoint in an HTTP step, then send the result to the contact fields so your next automation can tag or exclude the risky ones.

REST and MCPOne shared credit balance

Questions

How many credits does one contact use?

One email-domain-check lookup at the rate on the pricing page. Contacts you do not send to cost nothing.

Does this replace list hygiene by mailbox?

No. It checks the domain and some address patterns, and cannot prove a particular inbox exists. Treat it as a first filter.

Where should the keys go?

The LookValid key in the secret or credential field of the tool that runs the HTTP step, and the ActiveCampaign Api-Token in its own header value. Never type either into a contact field or a campaign.

Can a webhook fire twice for one contact?

ActiveCampaign states webhooks arrive at least once and are never retried, so a repeat is possible and a miss is too. Make the update safe to run twice and rerun the check for contacts you suspect were missed.

Sources

ActiveCampaign Developer Hub, Update a contact https://developers.activecampaign.com/reference/update-a-contact-new, read 2026-10-18
ActiveCampaign Developer Hub, Authentication https://developers.activecampaign.com/reference/authentication, read 2026-10-18
ActiveCampaign Developer Hub, Webhooks https://developers.activecampaign.com/reference/webhooks, read 2026-10-18
LookValid API reference: Email Domain Check https://lookvalid.com/docs/api/email-domain-check, read 2026-10-18

LookValid is run by Meralume Labs. It is not connected to, endorsed by or a partner of any company or product named on this page, and every product name belongs to its owner.

LookValid bills every lookup in credits from one shared balance, so the same key works for each check above.

See Email Domain Check