name: commercetools rate limits
generated: '2026-10-12'
method: searched
source: https://docs.commercetools.com/api/history/overview
sources:
- https://docs.commercetools.com/api/history/overview
- https://docs.commercetools.com/dev-tooling/mcp/knowledge-mcp
- https://docs.commercetools.com/api/general-concepts
- https://docs.commercetools.com/api/limits
note: commercetools does not publish a general request-rate limit for the Composable Commerce HTTP API; it publishes resource/object limits (api/limits) and asks clients to ramp up traffic and retry 502/503 with backoff. The prior generated row of "200 requests per second" was not found on any provider
  page and was removed. Limits stated on other pages (Knowledge MCP per-IP limit, burst 502/503 guidance) are under related_limits with their own source and verbatim quote.
headers:
- X-RateLimit-Limit
- X-RateLimit-Remaining
- X-RateLimit-Request-Cost
- Retry-After
status_on_exhaustion: 429
limits:
- name: Change History query tokens
  scope: project
  endpoint: Query Records
  limit_text: Change History queries are rate-limited. Each Query Records request consumes tokens based on the amount of data queried. The tokens are limited to each Project, and automatically replenish over time.
  source: https://docs.commercetools.com/api/history/overview
related_limits:
- name: Knowledge MCP and docs REST API
  scope: ip
  window: 15 minutes
  max: 100
  source: https://docs.commercetools.com/dev-tooling/mcp/knowledge-mcp
  quote: Each IP address is limited to **100 requests per 15 minutes**.
- name: Bursty load
  scope: project
  kind: burst
  source: https://docs.commercetools.com/api/general-concepts
  quote: During exceptionally high or bursty load, requests can transiently fail with `502 Bad Gateway` or `503 Service Unavailable` responses.