Toast · Rate Limits

Toast Rate Limits

Toast publishes its API rate limits openly in the developer guide, and returns runtime rate-limit signal on every response via three X-Toast-RateLimit-* headers. Limits are enforced per restaurant location when the Toast-Restaurant-External-ID header is present, and per source IP address when it is absent (for example, the partners API and authentication token requests, which carry no restaurant context). Requests over a limit are rejected with HTTP 429. This supersedes the 2026-05-04 bulk-sweep note that recorded Toast limits as "not publicly published" - they are published, on the rate limiting page of the developer guide.

Toast Rate Limits is the machine-readable rate-limit profile for Toast on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions.

The profile also includes 4 backoff/retry policies defined.

Tagged areas include Food Service, Point of Sale, Restaurants, Hospitality, and Rate Limiting.

5 Limits
Food ServicePoint of SaleRestaurantsHospitalityRate Limiting

Limits

Global rate limit per-client (all Toast APIs collectively)
20
Global rate limit (long window) per-client (all Toast APIs collectively)
10000
Default API rate limit per-api per-client
20
Menus API GET /menus endpoint limit per-endpoint per-client per-location
1
Orders API GET /ordersBulk endpoint limit per-endpoint per-client per-location
5

Policies

Per-restaurant vs per-IP enforcement
When Toast-Restaurant-External-ID is present on the request, the limit is applied per restaurant location, so exhausting Restaurant A's allowance does not block requests for Restaurant B. When the header is absent - the partners API and authentication token requests - the limit is applied per source IP address.
Account rate limits
An API account integrating with many restaurant locations may be given an additional account-specific limit that tracks total requests across all locations. Toast states it contacts the integration provider directly before applying one; the value is not published.
Authentication token reuse
Authentication tokens are typically valid for one day; the token response carries expires_in. Toast asks clients to request no more than one or two tokens per day and to reuse a token for at least 30 minutes. The authentication API enforces the global limit by IP address on token requests.
Custom per-API limits
Toast states there are currently no custom rate limits for specific APIs beyond the endpoint limits listed above.

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/toast-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.