specification: API Commons RateLimits
specificationVersion: '0.1'
provider: Contentstack
providerId: contentstack
generated: '2026-09-17'
method: searched
source: https://www.contentstack.com/docs/developers/apis/content-management-api#rate-limiting (markdown twin, HTTP
  200), read 2026-09-17
description: Contentstack enforces per-organization rate limits on the Content Management API and publishes them
  with the two response headers it returns. Reads and writes are each 10 requests per second per organization, bulk
  actions 1 per second, and stack creation 1 per minute. Limits are configurable per plan through support. Exceeding
  a limit returns HTTP 429.
docs: https://www.contentstack.com/docs/developers/apis/content-management-api
limit_count: 4
headers:
  limit: X-RateLimit-Limit
  remaining: X-RateLimit-Remaining
  reset: null
  retry_after: null
  documentation: The published header table lists X-RateLimit-Limit ("the maximum number of requests a client is
    allowed to make per second per organization") and X-RateLimit-Remaining ("the number of requests remaining in
    the current time period") and nothing else. There is no reset timestamp and no Retry-After, so a throttled client
    is told how many calls are left but never when the window reopens — it has to guess the backoff.
status_on_exhaustion: 429
limits:
- name: Content Management API reads
  scope: organization
  method_group: GET
  limit: 10
  window: second
  burst: null
  note: Default; configurable per plan via Contentstack support.
- name: Content Management API writes
  scope: organization
  method_group: POST / PUT / DELETE
  limit: 10
  window: second
  burst: null
  note: Default; configurable per plan via Contentstack support.
- name: Bulk actions
  scope: organization
  method_group: bulk endpoints
  limit: 1
  window: second
  burst: null
  note: Bulk actions do not follow the standard 10 req/s CMA limit. Each bulk publish request also carries a maximum
    of 10 items, so publishing 100 items is 10 requests over at least 10 seconds.
- name: Stack creation
  scope: organization
  metric: stacks
  limit: 1
  window: minute
  burst: null
plan_configurable: true
monthly_quotas:
  note: Monthly API-call quotas are a separate ceiling set by the pricing tier — 100K on Free, 1M on Growth, 6M+
    on Enterprise. See plans/contentstack-plans-pricing.yml.
guidance:
- 'On 429, back off exponentially with jitter: no Retry-After is returned, so the client must choose the delay.'
- Limits are enforced per ORGANIZATION, not per stack or per API key — teams sharing an org share the 10 req/s ceiling
  and will throttle each other.
- Bulk endpoints have their own 1 req/s budget, separate from the 10 req/s read/write budget.
- Because there is no idempotency mechanism (conventions/contentstack-conventions.yml), a retry after a 429 on a
  write is not safe to fire blindly — confirm the first call did not land.