Coupa · Rate Limits

Coupa Rate Limits

Coupa enforces API rate limits per tenant on the per-instance Coupa hosts (instance.coupahost.com, instance.cso.coupahost.com, instance.ctm.coupahost.com), but specific per-second / per-minute numeric thresholds are documented in the Coupa Compass customer portal rather than on the public web. Coupa's documented behavior on throttling is HTTP 429 with a Retry-After header; long-running list and report endpoints additionally support pagination and ETag-based incremental sync to keep call rates low.

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

It captures 1 rate-limit definition, measuring varies.

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

Tagged areas include BSM, Business Spend Management, Cloud Platform, Enterprise, and Procurement.

1 Limits Throttle: 429
BSMBusiness Spend ManagementCloud PlatformEnterpriseProcurementRate LimitingQuotasThrottling

Limits

Per-tenant API request rate tenant
varies
see Coupa Compass portal
Coupa publishes per-endpoint rate limits inside the authenticated Compass documentation portal. Public docs do not expose numeric values. Limits typically apply per Coupa instance host and per integration user.

Policies

Authenticated docs
Detailed rate-limit numbers and bulk-API guidelines live in the Coupa Compass customer portal (compass.coupa.com), behind authentication. Customers should consult their Coupa integration docs for the exact thresholds in their contract.
Backoff Strategy
On HTTP 429, honor the Retry-After header and back off with jitter. Avoid tight retry loops as they accelerate further throttling.
Pagination and incremental sync
Use the documented pagination parameters and updated_at filters / ETags to drive incremental syncs rather than re-pulling full collections; this is the primary way to stay within tenant rate limits.
Bulk imports vs REST
For large data loads, use Coupa's bulk import / loader interfaces rather than per-record REST calls; bulk paths have separate, higher-throughput budgets.
Integration user scoping
Coupa rate limits are scoped per integration user and per Coupa host. Provision separate integration users per consuming system to isolate limits and audit usage.

Sources