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 phone number being validated.
In most cases you'll receive a response quickly. However, some phone number 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 phone number per request.
If multiple phone numbers are included in a single request, only the last phone number in the list is validated for data format application/json.
This API provides mobile and landline coverage across 200+ countries and territories.
If your licence is limited to one or more country‑specific datasets, you'll need to use an earlier version of the API that matches your licensed coverage. Refer to the release notes to identify the appropriate version.
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.
