Make retries safe with idempotency keys.
phoneveriflo supports client-specified idempotency keys to guarantee that network timeouts, client retries, and duplicate API requests never create accidental duplicate jobs or double charges.
# Pass a unique UUID v4 in the Idempotency-Key header
curl -X POST https://api.phoneveriflo.com/api/v1/jobs \
-H "Authorization: Bearer pv_live_your_key" \
-H "Idempotency-Key: e8c68f6d-74be-4f51-a9f9-5f216263b65e" \
-H "Content-Type: application/json" \
-d '{"service":"phone-validation","inputs":["+14155552671"]}'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.
How Idempotency Keys Work
DeduplicationDeterministic transaction tracking across distributed networks.
When your client sends a POST /api/v1/jobs request with an Idempotency-Key header, subsequent retries within 24 hours return the exact original 202 Accepted response without double-charging.
Common Integration Questions
What format should I use for Idempotency-Key?
We strongly recommend standard UUID v4 strings (e.g. "e8c68f6d-74be-4f51-a9f9-5f216263b65e") or high-entropy alphanumeric strings (up to 200 characters).
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.