Handle stable, predictable public errors.
phoneveriflo returns standard HTTP status codes accompanied by structured, provider-neutral JSON error envelopes designed for programmatic recovery without leaking sensitive backend details.
HTTP/1.1 400 Bad Request
Content-Type: application/json
X-Request-Id: req_01j73b88fe991a
{
"error": {
"code": "INVALID_INPUT",
"message": "The 'inputs' array must contain between 1 and 100,000 valid strings.",
"docs": "https://phoneveriflo.com/docs/errors#INVALID_INPUT",
"requestId": "req_01j73b88fe991a"
}
}All requests require Bearer authorization with high-entropy secret tokens.
Bearer pv_live_...→Prevent duplicate jobs and safe automatic retries using 24h unique keys.
Idempotency-Key: uuid→Predictable Token Bucket model at 100 req/s with standard Retry-After headers.
100 req/s burst→Strict date-based compatibility guarantees with 12-month deprecation windows.
v1 (2026-08-11)→Test API Requests in Real Time
Build and simulate verification requests directly in your browser. Generates live code snippets and previews the exact response schema.
Configure request parameters and click Send Request to preview live execution.
HTTP Status Code Reference
Status MatrixOverview of all possible HTTP status codes returned by the API.
phoneveriflo uses conventional HTTP response codes: 200 OK, 202 Accepted, 400 Bad Request, 401 Unauthorized, 402 Payment Required, 403 Forbidden, 404 Not Found, 409 Conflict, 422 Unprocessable, 429 Too Many Requests, 500 Internal Error, 503 Unavailable.
Error Code & Recovery Matrix
Click any error code to view the exact error JSON envelope and recommended recovery logic.
{
"error": {
"code": "INVALID_INPUT",
"message": "The request could not be processed due to validation errors.",
"docs": "https://phoneveriflo.com/docs/errors#INVALID_INPUT",
"requestId": "req_jlh3tc63"
}
}Common Integration Questions
How should my application handle 429 Too Many Requests?
Read the "Retry-After" response header (which contains the required delay in seconds) and sleep before retrying. Implement an exponential backoff algorithm with full jitter to avoid stampeding herds.
Related Guides & API References
Ready to build with phoneveriflo?
Generate your secret API key in 30 seconds. Test preflight quotes and receive provider-neutral results with full freshness auditability.