Prismic · Rate Limits
Prismic Rate Limits
Prismic Rate Limits is the machine-readable rate-limit profile for Prismic on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the rate_limit_headers, retry_after, and note response headers.
Tagged areas include GraphQL, Headless CMS, Content Management, Page Builder, and JAMstack.
4 Limits
rate_limit_headersretry_afternote
Transcribed from the provider's documentation on 2026-08-13 — prismic.io/docs/content-api.
View Source
GraphQLHeadless CMSContent ManagementPage BuilderJAMstackMarketingContent DeliveryDeveloper ToolsMCPWebhookLocalizationDigital Asset Management
Limits
Content API per-repository
200/1 second
Applies only to requests that miss the CDN. Prismic names three ways to hit it: writing a custom client that bypasses the CDN, manually invalidating the cache in rapid succession, or firing hundreds of distinct queries right after a publish.
Content API per-repository
unlimited/n/a
Cached queries have no rate limit AND do not consume the plan's monthly API-call quota. Host choice is therefore both a performance and a billing decision.
Asset API per-host
1/1 second
Migration API per-repository
1/1 second
One page per second is the binding constraint on any large migration. A 10,000-page migration is a ~3-hour floor before any other consideration. Separately, `writeClient.migrate()` and a migration release each cap at 1,000 pages at a time; Prismic recommends batching per locale beyond that.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.