7shifts
7shifts is a restaurant employee scheduling, time-tracking, and team management platform that helps restaurant operators forecast labor, build schedules, manage shift trades, run payroll integrations, and communicate with hourly staff. The platform integrates with major POS systems for sales data and labor forecasting and supports multi-location operations across quick-service, full-service, and franchise concepts. The 7shifts API v2 is a REST API authenticated via long-lived access tokens (Bearer) for internal use or OAuth 2.0 client credentials for technology partners, exposing employees, schedules, shifts, time punches, departments, locations, and wages.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles 7shifts the way a machine reads it — 63 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — 7shifts scores 58.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile 7shifts
Each block below is one kind of artifact we hold for 7shifts. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
7shifts Availability API
Employee availability records.
7shifts Companies API
Company resources for 7shifts accounts.
7shifts Departments API
Departments within a location.
7shifts Identity API
Identity introspection for the authenticated token.
7shifts Locations API
Physical restaurant locations within a company.
7shifts OAuth API
Token issuance for Partner OAuth applications.
7shifts Reporting API
Sales, labor, and worked-hours reporting.
7shifts Roles API
Job roles within a department.
7shifts Sales API
Sales receipts and POS-integrated sales data.
7shifts Shifts API
Scheduled shifts assigned to users.
7shifts Time Off API
Time off requests and approvals.
7shifts Time Punches API
Clock-in and clock-out time tracking records.
7shifts Users API
Users (employees) scoped to a company.
7shifts Wages API
Hourly and salary wage records for users.
7shifts Webhooks API
Company-level webhook subscriptions.
Scroll within the panel for all 15 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
7shifts API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
7Shifts Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
7Shifts Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
7Shifts Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
7shifts API Rules
SPECTRAL7shifts API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Availability
JSON SCHEMACompany
JSON SCHEMADepartment
JSON SCHEMALocation
JSON SCHEMAReceipt
JSON SCHEMARole
JSON SCHEMAShift
JSON SCHEMATime Off
JSON SCHEMATime Punch
JSON SCHEMAUser
JSON SCHEMAWage
JSON SCHEMAWebhook
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
7Shifts Availability Structure
JSON STRUCTURE7Shifts Company Structure
JSON STRUCTURE7Shifts Department Structure
JSON STRUCTURE7Shifts Location Structure
JSON STRUCTURE7Shifts Receipt Structure
JSON STRUCTURE7Shifts Role Structure
JSON STRUCTURE7Shifts Shift Structure
JSON STRUCTURE7Shifts Timeoff Structure
JSON STRUCTURE7Shifts Timepunch Structure
JSON STRUCTURE7Shifts User Structure
JSON STRUCTURE7Shifts Wage Structure
JSON STRUCTURE7Shifts Webhook Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
7Shifts Availability Example
EXAMPLE7Shifts Company Example
EXAMPLE7Shifts Department Example
EXAMPLE7Shifts Location Example
EXAMPLE7Shifts Receipt Example
EXAMPLE7Shifts Role Example
EXAMPLE7Shifts Shift Example
EXAMPLE7Shifts Timeoff Example
EXAMPLE7Shifts Timepunch Example
EXAMPLE7Shifts User Example
EXAMPLE7Shifts Wage Example
EXAMPLE7Shifts Webhook Example
EXAMPLEScroll within the panel for all 12 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for 7shifts — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/7shifts · machine-readable index on apis.io