Skip to content

Rate limits

How many requests each satellite's APIs take, what each limit is counted on, what a 429 answer looks like, and the GraphQL and body size limits they share.

Reference8 min read

Each satellite limits its own APIs. The limits are the same on every plan. When you go over one, the API answers 429 with the code rate_limited: wait, then try again.

How the limits count

Most satellites count with a bucket that refills: you can send a burst of requests at once, and the bucket then fills up again at a steady rate. "120, then 120 a minute" means up to 120 requests at once, then two a second. CMS and Insights Orbit count per calendar minute instead.

Limits are counted on our servers as requests arrive. Treat the numbers as what you can rely on, plan to stay below them, and always handle a 429.

CMS Orbit

Delivery API and GraphQL
Limit
60,000 a minute
Counted on
Each key
Limit
15,000 a minute
Counted on
Each IP address, for requests from browsers. Requests from a server with a key, or with a cms_sk_ key, aren't counted on the address
Experiment results from browsers
Limit
Share the 15,000 a minute
Counted on
Each IP address
MCP server
Limit
60 a minute, or what the agent key is set to, from 1 to 600. Connections signed in with OAuth get 60
Counted on
Each agent key or connection
Management API
Limit
No limit

The delivery API sends X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset with every answer, and Retry-After with a 429. See CMS Orbit's delivery API.

Careers Orbit

Delivery API and GraphQL
Limit
120, then 120 a minute
Counted on
Each key and IP address
Applications, talent pool sign-ups and interview answers
Limit
6, then 2 a minute
Counted on
Each organisation and IP address
Job view counts
Limit
30, then 30 a minute
Counted on
Each IP address
Candidate portal: sign-in codes
Limit
5, then 1 a minute
Counted on
Each IP address
Candidate portal: checking a code
Limit
10, then 5 a minute
Counted on
Each IP address
Candidate portal: everything else
Limit
60, then 30 a minute
Counted on
Each IP address
Management API
Limit
120, then 120 a minute
Counted on
Each token and IP address
MCP server
Limit
No limit

Commerce Orbit

Storefront reads (shop, products, collections) and GraphQL
Limit
120, then 120 a minute, shared between REST and GraphQL
Counted on
Each shop and IP address. GraphQL with a key and no organisation counts on the key
Starting a cart, asking for a return
Limit
10, then 5 a minute
Counted on
Each IP address
Checkout, service points, orders, returns, customer profiles and addresses, downloads, gift cards on a cart
Limit
20, then 20 a minute
Counted on
Each IP address
Personal prices
Limit
30, then 30 a minute
Counted on
Each IP address
Sign-in codes, cart codes, account deletion and link requests
Limit
5, then 1 a minute
Counted on
Each IP address. Sign-in codes are also limited per email address
Checking a code, gift card balances
Limit
10, then 2 a minute
Counted on
Each IP address
MCP server
Limit
No limit

Travel Orbit

Trips, departures, guides and destinations, and GraphQL, from a browser or without a key
Limit
120, then 120 a minute
Counted on
Each booking name and IP address
The same from your own server, with an API key
Limit
6,000, then 6,000 a minute
Counted on
Each API key, and each IP address
Prices (quote, REST or GraphQL)
Limit
30, then 30 a minute
Counted on
Each organisation and IP address
Making a booking
Limit
10, then 5 a minute
Counted on
Each IP address
Checking a booking
Limit
20, then 20 a minute
Counted on
Each IP address
Traveller portal: sign-in codes
Limit
5, then 1 a minute
Counted on
Each IP address
Traveller portal: checking a code
Limit
10, then 2 a minute
Counted on
Each IP address
MCP server
Limit
No limit

Booking Orbit

Location, services, staff and free times
Limit
120, then 120 a minute
Counted on
Each location and IP address
Holding a time
Limit
20, then 10 a minute
Counted on
Each location and IP address
Booking an appointment or joining a waiting list
Limit
10, then 5 a minute, shared
Counted on
Each location and IP address
Managing a booking: viewing, cancelling, moving, offers
Limit
20, then 10 a minute
Counted on
Each location and IP address
Paying
Limit
20, then 20 a minute
Counted on
Each IP address
Booking assistant
Limit
8, then 6 a minute
Counted on
Each location and IP address
MCP server
Limit
No limit

Presence Orbit

Review widget
Limit
120, then 120 a minute, for all businesses together. A 429 carries Retry-After: 60
Counted on
Each IP address
Feedback and survey forms
Limit
5, then 2 a minute
Counted on
Each IP address
Review requests API and MCP server
Limit
No limit. A call takes up to 100 requests

Insights Orbit

Events from browsers (/insights/v1/collect)
Limit
120 a minute
Counted on
Each visitor's IP address
Server API (/insights/v1/server/events)
Limit
600 a minute
Counted on
Each key
Raw event API (/insights/v1/events)
Limit
60 a minute
Counted on
Each key
GraphQL
Limit
60 a minute
Counted on
Each key
MCP server
Limit
No limit

A 429 from the server API, the raw event API and GraphQL carries Retry-After: 60.

OAuth and the Orbit app

Registering an OAuth app (/oauth/register) in Careers, Commerce, Travel, Booking and Presence Orbit
Limit
20, then 10 a minute. A 429 answers slow_down
Counted on
Each IP address
Registering an OAuth app (/oauth/register) in CMS Orbit and Insights Orbit
Limit
10 a minute. A 429 answers slow_down; CMS Orbit adds Retry-After
Counted on
Each IP address
The Orbit app's token and revoke endpoints
Limit
30 a minute. A 429 answers slow_down
Counted on
Each IP address
The Orbit app's API
Limit
240 a minute
Counted on
Each signed-in device

What a 429 looks like

REST APIs answer:

JSON
{ "error": { "code": "rate_limited", "message": "Too many requests; try again shortly" } }

GraphQL APIs answer with errors, and the code in extensions.code:

JSON
{ "errors": [{ "message": "Too many requests. Wait a minute and try again.", "extensions": { "code": "rate_limited" } }] }

The CMS Orbit MCP server answers in JSON-RPC, with error.code -32001.

Wait for Retry-After seconds when the answer has it, and a minute when it doesn't. Then try again, waiting longer each time if it happens again. The CMS Orbit SDKs don't retry a 429 themselves: they throw a rate-limit error that carries how many seconds to wait.

GraphQL and body limits

Every GraphQL API (CMS, Careers, Commerce, Travel and Insights Orbit) takes the same queries at most:

20,000 characters
Answer when over it
413, query_too_large
10 levels deep
Answer when over it
400, query_too_deep
300 fields
Answer when over it
400, query_too_complex

Bodies:

CMS Orbit MCP server
Largest body
5 MB
Other MCP servers
Largest body
1 MB
CMS Orbit experiment results
Largest body
16 KB
Insights Orbit events from browsers
Largest body
64 KB, up to 50 events
Insights Orbit server API
Largest body
256 KB, up to 100 events

Pages of results are at most 100 items in the CMS and Careers delivery APIs, 250 products in the Commerce storefront API and 1,000 events in the Insights raw event API.

Stay under the limits

  • Cache answers. A website that caches CMS Orbit's pages for a minute makes a handful of requests, however many visitors it has.
  • Call from your server where you can, with a key, so your visitors' requests don't all count against one address.
  • Use webhooks to hear about changes instead of asking again and again. See Verify webhooks from Bifröst Orbit.
  • Ask for what you need in one GraphQL query instead of many REST calls.

Was this page helpful?

Read next