7shifts API
Browse all 7shifts APIs★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementoauth2,apiKey,basic138 EndpointsREST
For Agents
Manage restaurant scheduling, shifts, time punches, employees, and labor settings across the full 7shifts platform. Useful for agents that operate or report on restaurant workforce data.
Use for: List all locations under a 7shifts company, Create a new shift for a server at the downtown location next Friday, Find employees who clocked in late yesterday, Approve a pending time-off request for a specific user
Not supported: Does not handle POS sales data, food inventory, or customer-facing reservations — use for restaurant workforce scheduling, time tracking, and labor settings only.
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.
Install Jentic One Beta
Connect the 7shifts API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 7shifts API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 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 | sh2
Step 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.
Capabilities
What an agent can do with 7shifts API.
Provision and manage 7shifts companies, locations, departments, and roles
Create, publish, and update shift schedules for restaurant locations
Record and edit time punches against published shifts
Manage employees, including hires, terminations, and role assignments
Track time-off requests with approval workflows
Pull labor settings, including overtime rules and break enforcement, for payroll integrations
Push engagement events such as announcements and tasks to the in-app feed
Use Cases
Patterns agents use 7shifts API for, with concrete tasks.
★ Restaurant Schedule Automation
Restaurant operators automate weekly schedule creation by combining the schedules and shifts endpoints with their own forecasting. The API exposes /v2/company/{company_id}/locations and the shift CRUD endpoints needed to publish a schedule for hundreds of employees in a single run, replacing manual entry in the 7shifts UI. A first working integration takes a developer three to five days end to end.
For each location returned by /v2/company/{company_id}/locations, create the next week's shifts via the shifts endpoints based on a forecasted demand input.
Payroll and Time Punch Integration
Payroll providers pull approved time punches and labor totals from 7shifts to feed restaurant payroll runs. The time punches and labor settings endpoints return the hours, breaks, and overtime data needed to calculate pay accurately, replacing CSV exports or scraped UI reports. Building a payroll-grade integration is typically a two-week project including reconciliation tooling.
Pull time punches for a given company over the previous pay period, group by employee and location, and emit a payroll-ready CSV with regular, overtime, and break minutes.
Workforce Reporting Across a Restaurant Group
Multi-location restaurant groups build internal dashboards on top of 7shifts to monitor labor cost percentage, no-shows, and overtime by location. The companies, locations, shifts, and time punches endpoints provide the source data for these reports without manual exports. A first dashboard is roughly a one-week build for a single restaurant group.
Pull all locations for a company, fetch published shifts and time punches for the trailing four weeks, and compute labor cost percentage by location.
Time-Off and Engagement Workflows
Operators use the time-off endpoints to manage approvals from outside the 7shifts UI — for example, syncing time-off into Slack or auto-approving requests under a certain length. Engagement endpoints similarly push announcements into the in-app feed for shift staff. A typical integration is two to three days for a single workflow.
List pending time-off requests for a location, approve any under three days that do not conflict with critical shifts, and post a confirmation to the engagement feed.
AI Agent Restaurant Operations Assistant via Jentic
An AI assistant connected through Jentic can answer questions like 'who is scheduled to close tonight at the downtown location' by chaining the locations, schedules, and shifts endpoints. Jentic stores the OAuth credential in the vault and exposes operations by intent, so the agent never needs to read the 7shifts API reference. End-to-end response time is under ten seconds per query.
Search Jentic for 'list scheduled shifts for a location tonight', load the matching 7shifts schedules operation, and return the list of employees with start and end times.
Key Endpoints
138 endpoints — the 7shifts api is the full developer interface to 7shifts, a team management platform built for restaurants.
METHOD
PATH
DESCRIPTION
POST
/oauth2/token
Exchange credentials for a 7shifts OAuth access token
GET
/v2/whoami
Identify the authenticated user and tenant
GET
/v2/companies
List companies accessible to the credential
GET
/v2/company/{company_id}/locations
List locations under a company
GET
/v2/company/{company_id}/labor_settings
Retrieve labor enforcement settings for a company
POST
/v2/partner_company_creation
Create a 7shifts company on behalf of a partner
GET
/v2/company/{company_id}/inactive_reasons
List configured reasons for marking employees inactive
POST
/oauth2/token
Exchange credentials for a 7shifts OAuth access token
GET
/v2/whoami
Identify the authenticated user and tenant
GET
/v2/companies
List companies accessible to the credential
GET
/v2/company/{company_id}/locations
List locations under a company
GET
/v2/company/{company_id}/labor_settings
Retrieve labor enforcement settings for a company
POST
/v2/partner_company_creation
Create a 7shifts company on behalf of a partner
GET
/v2/company/{company_id}/inactive_reasons
List configured reasons for marking employees inactive
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
7shifts OAuth tokens, marketing API keys, and basic auth credentials are stored encrypted in the Jentic vault (MAXsystem) and attached to each request at execution time. Agents receive scoped access — raw secrets never enter the prompt.
Intent-based discovery
Agents search Jentic with intents like 'list scheduled shifts' or 'pull time punches for payroll' and Jentic returns the matching 7shifts operation with its input schema, so the agent calls the right endpoint across 138 operations without browsing the developer portal.
Time to first call
Direct integration with the 7shifts API takes one to two weeks for a payroll-grade flow including OAuth, multi-tenant handling, and reconciliation. Through Jentic the search-load-execute flow takes under thirty minutes for a single operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 7shifts API through Jentic.
What authentication does the 7shifts API use?
The API supports multiple schemes — OAuth 2.0 for partner integrations, marketing API keys for marketing endpoints, and basic auth for legacy clients. The /oauth2/token endpoint exchanges client credentials for an access token. When called through Jentic these credentials are held in the encrypted vault and attached at execution time, so they never appear in agent context.
Can I create and publish a shift schedule with the 7shifts API?
Yes. The API exposes shift CRUD endpoints scoped to a company and location. After listing locations via /v2/company/{company_id}/locations you can create individual shifts and then publish them as a schedule. The API supports both single-shift and bulk operations.
What are the rate limits for the 7shifts API?
7shifts applies per-token rate limits that vary by integration tier; the documentation describes them as fair-use rather than a single public number. Back off on HTTP 429 with the Retry-After header. For payroll integrations that pull large amounts of time-punch data, batch by location and pay period rather than polling continuously.
How do I pull time punches for payroll through Jentic?
After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'pull time punches for payroll', load the 7shifts time punches operation, and execute it scoped to the company and pay period. Jentic injects the OAuth token automatically.
Does the 7shifts API include POS or sales data?
No. 7shifts focuses on workforce data — schedules, shifts, time punches, employees, and labor settings. Sales and POS data come from the partner POS systems that integrate with 7shifts. To compute labor cost percentage you typically join 7shifts labor data with sales pulled from the POS API separately.
Where does this OpenAPI specification come from?
This 7shifts spec was published as part of a third-party OpenAPI examples collection rather than directly by 7shifts. Jentic mirrors and validates it against the live API at api.7shifts.com so it stays usable for agent and developer tooling. Get started at https://app.jentic.com/sign-up.
GET STARTED