What They Are and Why They Matter
Clients are asked to limit calls to 10 PT API requests per second w/ burst 20 requests.
What this means in practice:
The sustained limit (10 req/sec) governs steady, continuous use. A client running ongoing monitoring queries operates within this tier.
The burst limit (20 req/minute) gives clients room to send a small batch of requests — for example, submitting a group of verifications at once — without triggering a throttle on every call.
Together, these limits support both continuous monitoring workflows and batch submission patterns, which cover the majority of how clients interact with our API.
Why does ProviderTrust API enforce Rate Limiting?
Rate limits are a standard feature of any enterprise-scale API. Rate limiting protects:
Platform stability. APIs run on shared infrastructure. Without limits, a single client — or a single misconfigured integration — can consume resources that affect everyone. Rate limits act as a circuit breaker.
Cost predictability. Every API call has a cost. Rate limits protect both sides: ProviderTrust from runaway infrastructure spend, and clients from accidental overuse that could trigger unexpected charges or service degradation.
Fair access. Limits ensure no single tenant degrades performance for others. This is especially important in a multi-tenant SaaS environment where clients share underlying resources.
In short: ProviderTrust enforces rate limiting to protect data accessibility and service reliability our clients depend on.