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 Deployments and select the deployment where the existing Email Validation v1 is used.
3. Copy existing token.​
4. In your integration, replace the existing v1 endpoint with new v2 endpoint.​
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 Deployments, select the new deployment and retrieve the newly generated token.
3. Use this token to integrate with the Email Validation v2 endpoint.
4. Update the request body and response inline with new API specification.

To check service availability, visit the service status page. You can see any current issues and subscribe to updates to stay informed about the API's uptime and downtime.

To confirm your token is working correctly, send a test API request.

If you receive a 403 Forbidden response, see My token for guidance on managing or regenerating your token.

Treat your authentication token like a password and secure both the token and the integration that uses it.

In the Self Service Portal, you can apply additional controls to limit where and how a token can be used. These include specifying CORS origin domains, defining permitted URLs, and whitelisting IP addresses or IP ranges.

You should also rotate tokens regularly and revoke any tokens that are no longer in use. You can manage all token security settings, including rotation and restrictions in the Self Service Portal.

You can view your licence, purchased credits, and remaining balance in the Self Service Portal.

Response times can vary depending on your API configuration and the type of email address being validated.

In most cases you'll receive a response quickly. However, some email address require additional checks to return an accurate result, which can take slightly longer. Timeout values are configurable to help you balance responsiveness with validation depth.

The real‑time API is designed to validate one email address per request.

If multiple email addresses are included in a single request, only the last email address in the list is validated for data format application/json.

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

In some cases, the service may be unable to conclusively validate an email address. When this happens, the confidence value and verbose details returned in the response explain why a definitive result could not be provided.

To check service availability, visit the service status page. You can see any current issues and subscribe to updates to stay informed about the API's uptime and downtime.

Real‑time validation is typically embedded into interactive user flows, such as forms and registration journeys, where quick setup and immediate feedback matter. SDKs make it easier to add this type of validation using familiar language‑specific tools.

Bulk validation follows a different pattern. It is designed for asynchronous, job‑based processing of large data sets, often as part of automated or scheduled workflows. For this reason, bulk validation is best integrated using the OpenAPI specification and generated clients, which give you flexibility and control over batch submission, monitoring, and result retrieval.

Both approaches are fully supported and designed to fit their intended use cases.

You can validate up to 10,000 email addresses per batch when using the bulk API. Batch requests that exceed this limit are not accepted and return a 400 Bad Request response.