Read normalized results without provider-specific fields.
All verification outputs are standardized into clear, provider-neutral schemas with explicit validity flags, carrier metadata, and checked-at freshness timestamps.
# Stream canonical CSV results directly to a local file
curl https://api.phoneveriflo.com/api/v1/jobs/job_01j73a6e2jq9bk8ze7yv2vmR/results \
-H "Authorization: Bearer pv_live_your_key" \
-o results.csvAll 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.
Canonical Result Schema
Universal StructureStandardized column headers and data types across all verification outputs.
Regardless of whether you verify phone numbers, messaging reachability, carrier data, or email deliverability, the output schema adheres to a consistent first-party structure.
| Field | Type | Description | Example Values |
|---|---|---|---|
| row | integer | 1-based row number in the original upload order | 1, 2, 3 |
| input | string | Normalized E.164 phone or lowercase email | +14155552671 |
| phone | string | E.164 phone value | +14155552671 |
| e164 | string | E.164 phone value | +14155552671 |
| status | string | Range/validation status returned by the provider | valid, ASSIGNED, UNAVAILABLE |
| line_type | string | Telecom line classification | mobile, landline, voip, toll_free, premium |
| carrier | string | Network carrier or email domain authority | Verizon Wireless, O2, Google, Microsoft |
| country | string | ISO-3166-1 alpha-2 country code | US, GB, AU, CA, DE, JP |
| region | string | Allocation region | CA, NY |
| locality | string | Allocation locality | LOSANGELES, DIR ASST |
| source | string | Numbering source that produced the result | NANPA_CO, CNA_BLOCK |
| confidence | integer | null | Range match confidence score | 90 |
| generation_basis | string | How the number was generated (generation services) | allocated_or_designated_range |
| … | string | number | boolean | null | One column per remaining provider response field; blank when a field does not apply to a row | any |
Common Integration Questions
In what order are the result rows returned?
Results strictly maintain the exact 1-to-1 row ordering of your original inputs array, making it effortless to map results directly back to your internal database IDs.
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.