KPMG · Rate Limits

Kpmg Rate Limits

KPMG does not publish a public developer API at the corporate network level, so no public network-wide rate limits exist. Throughput and SLAs on any KPMG-built API inside a client engagement, a managed-services arrangement, or an AI Technology deployment are negotiated bilaterally and owned by the client or engagement contract. KPMG Origins (the Australian IWTS platform) is the only KPMG-branded public API; its production and sandbox REST surfaces use API-key authentication, but no public per-key rate-limit numbers are documented on the help center pages surveyed. Limits are governed by the operator / software-provider agreement.

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

It captures 2 rate-limit definitions, measuring not_applicable and not_disclosed.

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

Tagged areas include Consulting, Professional Services, Big Four, and Rate Limiting.

2 Limits Throttle: 429
ConsultingProfessional ServicesBig FourRate Limiting

Limits

No public rate limits (network-level) account
not_applicable
not applicable
KPMG Origins (operator-agreement governed) api_key
not_disclosed
not publicly disclosed

Policies

Engagement-defined
Throughput, concurrency, and SLAs on any KPMG-built API inside a client engagement are defined in the engagement contract or managed-services agreement, not by a public developer-portal policy.
Origins product-defined
KPMG Origins per-key throughput, quotas, and SLAs are governed by the operator / software-provider agreement; the public help center does not document numeric per-key limits.

Sources