Rate Limits & Quotas

Rate limiting restricts the number of requests that can be made within a specific time period to ensure that API services operate securely and sustainably. Limits may vary depending on the API group, service, environment, or customer account.

Rate Limit

Rate limit refers to the maximum number of requests that can be sent within a specific period. Limits for PIM API endpoints are applied on a per-minute basis.

When the limit is exceeded, the API returns a 429 Too Many Requests response.

Endpoint and AppKey Limits

Each endpoint has a separate endpoint limit on a per-minute basis. In addition, a separate limit is applied for requests that can be made with the same AppKey.

In integrations, request volume should be planned by considering both the endpoint limit and the AppKey limit.

Endpoint	Endpoint Limit	AppKey Limit
POST /products	600 requests/min	60 requests/min
POST /variants	600 requests/min	60 requests/min
POST /categories	1,200 requests/min	120 requests/min
POST /trademarks	1,200 requests/min	120 requests/min
POST /documenttypes	1,200 requests/min	120 requests/min
POST /product-media-list	1,200 requests/min	120 requests/min
POST /variant-media-list	1,200 requests/min	120 requests/min
POST /search	120 requests/min	40 requests/min
POST /documents	Default	Default
POST /properties	Default	Default
POST /options	Default	Default

Rate Limit Response Example

{
  "type": "Error",
  "code": "429",
  "message": "Too Many Requests",
  "errors": []
}

Recommended usage: In case of rate limit exceeded, an automatic wait and retry mechanism should be implemented on the integration side. The same request should be prevented from being sent repeatedly within a short period; for high-volume operations, pagination and controlled batch strategies should be preferred.