The 7shifts API is the full developer interface to 7shifts, a team management platform built for restaurants. This third-party-published spec covers 138 endpoints across companies, locations, departments, roles, employees, schedules, shifts, time punches, time off, labor settings, and engagement features. Restaurant operators, payroll integrations, and POS partners use it to provision locations, assign shifts, capture clock-ins and clock-outs, and pull labor data for payroll runs. Authentication supports OAuth 2.0, marketing API keys, and basic auth depending on the integration type.
138 endpointsJentic publishes the only available OpenAPI specification for 7shifts Restaurant Scheduling API, keeping it validated and agent-ready. This curated v2 spec covers twelve core endpoints from the 7shifts platform — companies, locations, departments, roles, users, shifts, schedules, time punches, and labor settings — focused on the operations a typical restaurant integration needs without the full surface of the partner API. Authentication uses OAuth 2.0 with tokens issued through the /oauth2/token endpoint.
12 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.