7shifts · Rate Limits

7Shifts Rate Limits

The 7shifts API v2 throttles requests on a per-access-token basis. Public and third-party developer references describe a limit on the order of 10 requests per second per access token, after which the API returns HTTP 429 Too Many Requests. Limits apply regardless of subscription plan. Developers should implement retry with exponential backoff. These figures are drawn from third-party developer documentation and should be reconciled against the official 7shifts developer reference (developers.7shifts.com) before relying on exact numbers.

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

It captures 1 rate-limit definition, 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 Rate Limiting, Restaurant, Scheduling, and Workforce Management.

1 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-02.
Written by API Evangelist on 2026-06-02 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingRestaurantSchedulingWorkforce Management

Limits

Requests per access token key
requests_per_second · second
10
Reported limit of approximately 10 requests/second per access token; exceeding it returns HTTP 429. Confirm against official docs.

Policies

Exponential backoff
On a 429 response, back off and retry with exponentially increasing delays rather than retrying immediately.
Per-token scoping
Rate limits are bound to the access token, so distributing work across multiple tokens (where allowed by partner agreements) increases aggregate throughput.
Cursor pagination
Collection endpoints use cursor-based pagination (cursor + limit, limit up to 500); page through results rather than requesting large unbounded sets.
Incremental sync
Use modified_since filters on companies, users, shifts, and time punches to fetch only changed records and reduce request volume.

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