API Rate Limits
Account and IP limits for API requests.
Account Rate Limits
Rate limits depend on your account tier. All active API keys on the same account share the single-request allowance across GET and POST, both API hostnames, and endpoints. Bulk requests share a separate allowance. Funding your account enables the funded limits below.
| Tier | Single-lookup endpoints CNAM, LRN, Trust, Spam, Messaging |
Bulk endpoints up to 1,000 numbers per request |
Basis |
|---|---|---|---|
| Free trial credit, no funds added |
20 / minute · 200 / hour | 5 / minute · 20 / hour | Per account |
| Funded any balance added |
6,000 / minute | 300 / minute | Per account |
The same account counters apply on verirouteintel.com and api-service.verirouteintel.io. Changing keys, HTTP methods, endpoints or IP addresses does not create another allowance. Requests to usage and analytics endpoints also consume the shared single-request allowance; report exports consume the bulk allowance.
Separately, API traffic is capped at 120 requests per second per public IP, with a short burst allowance. This protection applies even when a request supplies an API key. Customers sharing a public IP share this edge limit. Missing or invalid credentials receive tighter IP-based application limits. Website and free-lookup protections remain separate.
These are request ceilings, not guaranteed processing speeds. Spread requests evenly. For lists, use a bulk endpoint rather than issuing a separate request for each number.
Headers & 429 Behavior
A limit breach returns HTTP 429. Application and edge responses can differ:
- HTTP 429 Too Many Requests when limits are exceeded.
- Honor
Retry-Afterwhen present. An edge rejection may not include application rate-limit headers or a JSON body. - Back off and retry after the indicated interval. Exponential backoff is recommended for clients that may spike.
Best Practices
Follow these guidelines to optimize your API usage and avoid rate limiting:
- Implement Caching: Cache responses to reduce redundant API calls
- Batch Requests: Use bulk endpoints when available for multiple lookups
- Monitor Headers: Check rate limit headers in responses to track usage
- Implement Retry Logic: Use exponential backoff for failed requests
- Optimize Timing: Spread requests evenly rather than bursting
- Upgrade Plans: Consider higher tiers for increased limits
Product prices · public rates
Each selected product adds its per-number cost. Estimates do not submit lookups or charge your wallet.
- lrn
- $0.000500 per number
- enhanced_lrn
- $0.000000 per number
- messaging_provider
- $0.000900 per number
- cnam
- $0.006000 per number
- spam
- $0.007000 per number