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, conforming to the API Commons Rate Limits specification.

It captures 1 rate-limit definition, measuring requests_per_second.

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 Throttle: 429
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