pVerify · Rate Limits

Pverify Rate Limits

pVerify publishes no rate limits. Its commercial model is per-transaction rather than quota-based, and throughput allowances — where they exist — are written into the account contract, which is why no figure appears publicly. The only runtime signals a client actually gets are the token's expires_in from POST /Token and the in-envelope APIResponseCode 2 (NoFunds), which is a BALANCE condition rather than a throttle. The dimensions in limits[] below are the axes a pVerify contract is negotiated on; none carries a published value. pVerify markets a batch eligibility product for high-volume work, but no batch endpoint appears in its public Postman collection, so no batch throughput contract could be read either.

Pverify Rate Limits is the machine-readable rate-limit profile for pVerify on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, concurrent_requests, transactions, and seconds.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and throttled_note.

Tagged areas include Healthcare, Insurance, Eligibility, Claims, and EDI.

4 Limits
HealthcareInsuranceEligibilityClaimsEDI270/271Rate LimitingQuotasThrottling

Limits

Real-Time Requests account
requests
Synchronous eligibility / claim status / estimation throughput, account specific.
Concurrency account
concurrent_requests
Maximum simultaneous in-flight real-time transactions, account specific.
Batch Eligibility account
transactions
High-volume verifications routed through the Batch API for async processing.
Access Token Lifetime account
seconds
OAuth2 bearer tokens expire (expires_in) and must be re-requested from /Token.

Policies

Tiered Limits
Throughput allowances are set per contract and rise with committed volume.
Batch Routing
High-volume eligibility should use the Batch API rather than real-time calls.
Backoff Strategy
API Evangelist guidance, not a pVerify-published policy. Because there is no idempotency key, a retry of an inquiry POST is a NEW billable transaction — clients must poll GET /API/GetPendingInquiries and the matching retrieval endpoint instead of resubmitting, and refresh the bearer token when expires_in elapses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/pverify-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.