FAQs

To replace your existing integration of Email Validation v1 to Email Validation v2 using the same deployment (product purchased earlier)

1. Login to Self-Service Portal.
2. Go to account and deployment where the existing Email Validation v1 is used.
3. Copy existing token.​
4. Replace v1 end point with new v2 end point.​
5. Input the copied token into the header when using the API.
6. Update the request body and response inline with new API specification.

To replace existing integration of Email Validation v1 (Legacy) to Email Validation v2 (New) using new deployment with newly purchased product

1. Login to Self-Service Portal.
2. Go to account and deployment and retriEmail Validatione the token generated.
3. Use this token to integrate with the Email Validation v2 end point.
4. Update the request body and response inline with new API specification.

The API can validate email addresses from most email service providers.

However, there are some scenarios where the API is unable to validate the email address provided. On such occasions, the confidence level and verbose details returned in the response body will help you understand why the service was unable to conclusively verify the specified email address.

To check service availability, go to the service status page. There you can see if there are any current issues and you can subscribe to updates, so you're always informed about the API's uptime and downtime.

To check if your token is working correctly, you need to test it, by sending an API request.

If you get a response code of 403, check out My token.

Check out Timeouts to find out more about the API's response time.

The API is designed to validate one email address at a time.

If you enter multiple email addresses when you submit a request:

Only the last email address in the list will be validated, provided the data format is application/json or application/x-msgpack.
Only the first email address in the list will be validated, provided the data format is application/xml.