Design around predictable API limits.
phoneveriflo applies deterministic Token Bucket rate limiting to guarantee high availability, low latency, and fair resource distribution across all customer tiers.
HTTP/1.1 202 Accepted
RateLimit-Limit: 100
RateLimit-Remaining: 94
RateLimit-Reset: 1
Content-Type: application/jsonAll 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.
Standard Tier Rate Limits
Token BucketCapacity thresholds allocated per organization.
Rate limits are enforced at the organization level: POST /api/v1/jobs: 100 req/s burst, 1,000 req/min sustained, 10 active concurrent jobs. GET status/results: 200 req/s.
Token Bucket Velocity Simulator
Adjust the client request velocity slider to see how rate limit headers and burst buckets behave.
RateLimit-Limit: 100
RateLimit-Remaining: 65
RateLimit-Reset: 1
Retry-After: 0Common Integration Questions
Do cache hits consume my rate limit quota?
Yes, API rate limits measure HTTP request velocity regardless of whether a job resolves via cache or live network checks. However, cache hits resolve in milliseconds and do not hold worker job slots.
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.