Do you have a question about our Email Verification API? We got you covered! Check out our frequently asked questions below!
How to get started using Email Verification?
Please see our getting started help article here.
What is the difference between private and public verification endpoint?
The public endpoint is meant to be used within front-end applications (and is only available on version 3 of the Validations API). To protect the public API Key it has an initial monthly limit that can be adjusted. The private endpoint is meant for back-end applications and does not have this limitation.
How can I limit the number of public verifications my account can perform?
By navigating to your Account Settings, you can set the Public Verification Limit field as pictured below:
What is the difference between is_valid and mailbox_verification?
is_valid is the result of the ESP-specific syntax check, while mailbox_verification makes a call to the ESP to see if the mailbox actually exists.
Why is mailbox_verification null?
Mailbox Verification by default is disabled. It needs to be enabled in the API call by passing the parameter "mailbox_verification=true".
If mailbox_verification is disabled it will return null, true if mailbox_verification passes, and false if it does not pass. It will also return unknown if the SMTP session could not be completed or if the ESP does not support mailbox verification.
Why is is_valid true and mailbox_verification false?
The mailbox verification results do not have an impact on is_valid. Is_valid returns true if the address is parsable, passes known syntax checks and has a valid SMTP server, regardless of the outcome of mailbox verification.