Content Catalog Rate Limits and Quotas
The Content Catalog API observes a rate limit to ensure that all clients get sufficient service and that runaway applications don’t consume excessive resources. You’ll find general information about rate limits in APS Rate Limits and Quotas.
This rate limit applies across all of the Content Catalog API’s endpoints, although it’s separately set for each requesting application (specified by the client ID). Note that this rate is not a service guarantee. In the uncommon case where total service use is too high across all clients, accepted request rates may drop until traffic subsides.
All Endpoints
The same rate limit applies to every Content Catalog API endpoint. All public endpoints share this single limit; there are no separate limits per endpoint group.
Rate Limits for Content Catalog API Endpoints
The following table describes that limit:
| Endpoints | Limit (Requests/minute) | Scope |
|---|---|---|
| All endpoints | 200 | Per application (specified by client ID) |
Scope
The Content Catalog API measures requests per application as specified by the Client ID. Each application’s usage is tracked separately.
Violation Notification
If an application exceeds this rate limit for Content Catalog, the API returns an HTTP 429 error (described in detail in APS Rate Limits and Quotas).
Changing Limits
APS Rate Limits and Quotas describes how to request rate limit changes for APS APIs.