Email Verification
Verify email addresses for deliverability before sending campaigns to reduce bounce rates and protect sender reputation.
Email Verification lets you check whether an email address is deliverable before you send to it. Bounce rates kill sender reputation, and dead sender reputation means your emails land in spam for everyone on your list. This tool prevents that at the source.
What This MCP Tool Does
This tool validates email addresses in real-time by checking whether the mailbox exists and can receive messages. Run verification before importing contact lists, before sending campaigns, or as part of a data hygiene routine to keep your CRM clean.
Endpoint Reference
Verify an email address:
POST /emails/verify
Submit an email address and receive a verification result indicating deliverability status.
Authentication
Requires a Private Integration Token (PIT) with the emails scope enabled.
Key Parameters
Request:
email— the email address to verify
Response includes:
- Deliverability status (valid, invalid, risky, unknown)
- Reason for the determination
- Risk scoring where applicable
Important Notes
Email verification is not instant for all addresses. Some mail servers respond quickly; others use greylisting or other techniques that can delay verification. Build your integration to handle both immediate and delayed responses.
Verification tells you whether the mailbox exists and accepts mail. It does not tell you whether the person will open or engage with your messages. Valid does not mean interested.
Run verification on imported lists before they enter your CRM. Catching bad addresses before they become contacts saves you from bounce damage later. This is especially important after CSV imports where data quality is unpredictable.
Rate limits apply. If you are verifying a large batch, space out your requests to avoid hitting limits. For bulk verification of thousands of addresses, consider a dedicated verification service alongside the GHL API.
Common Questions
Should I verify every email that enters my CRM? For manually entered or form-submitted emails, verification is optional since the person just typed it. For imported lists, purchased data, or scraped sources, always verify first.
What does a “risky” result mean? Risky typically means the email exists but has characteristics that suggest it might bounce or be a catch-all address. Proceed with caution — consider excluding risky addresses from large campaigns.
How often should I re-verify existing contacts? Email addresses go stale over time as people change jobs, close accounts, or abandon addresses. Running a quarterly verification pass on your active contact list helps maintain deliverability.
Does verification count against my GHL email sending limits? Verification is a separate operation from sending. Check the API documentation for verification-specific rate limits and quotas.
Related MCP Tools
- Contact CRUD — Update contact records based on verification results
- Email Send — Send emails with confidence after verification
- Email Campaigns — Campaign performance depends on list quality
- Contact Tags — Tag contacts based on verification status for segmentation