Storyblok · Rate Limits

Storyblok Rate Limits

Storyblok publishes per-second rate limits on the Content Delivery API that vary by request type. Cached CDN requests get the highest ceiling (1,000 RPS); uncached single content entries and small listings allow 50 RPS, with limits scaling down as listing page size grows. Limits are per token/space. Beyond steady-state limits the API returns HTTP 429 and clients are expected to back off.

Storyblok Rate Limits is the machine-readable rate-limit profile for Storyblok on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions, measuring requests_per_second.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include CMS, Content Delivery, Headless CMS, REST API, and Rate Limiting.

6 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
CMSContent DeliveryHeadless CMSREST APIRate Limiting

Limits

Cached CDN Requests token
requests_per_second · second
1000
Cached responses served from the CDN.
Single Content Entry token
requests_per_second · second
50
Single uncached content entry retrieval.
Listings up to 25 Entries token
requests_per_second · second
50
List endpoints returning 25 or fewer entries per page.
Listings 25-50 Entries token
requests_per_second · second
15
Listings 50-75 Entries token
requests_per_second · second
10
Listings 75-100 Entries token
requests_per_second · second
6
Per-second cap is reduced proportionally as page size increases beyond 25 entries.

Policies

Throttling Response
When the rate limit is exceeded the API returns HTTP 429; clients should pause and retry with backoff.
Caching
Storyblok recommends prioritizing cached requests, which have a 20x higher per-second ceiling than uncached single-entry requests.
Exponential Backoff
Use exponential backoff with jitter on retry to avoid synchronized retry storms.
Plan Quotas
Beyond per-second limits, monthly API request totals are bound by the subscribed plan (100k Starter, 1M Growth, 4M Growth Plus); overages above plan caps are billed at $10 per 1M extra requests.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/storyblok-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.