canonical: https://jentic.com/apis/7shifts.com

# 7shifts APIs

7shifts is a team management platform built for restaurants, covering scheduling, shifts, time punches, employees, and labor settings. Its APIs let restaurant operators, payroll providers, and POS partners provision companies and locations, build and publish schedules, capture clock-ins and clock-outs, manage time off, and pull labor data for reporting and payroll. Jentic exposes two 7shifts specifications: the full 138-endpoint partner surface and a curated 12-endpoint v2 subset for lighter scheduling and reporting integrations.

## For AI agents

An agent can provision 7shifts companies and locations, build and publish restaurant shift schedules, record and read time punches, manage employees and time off, and pull labor settings for payroll and reporting. It can work against the full 138-endpoint partner API or a curated 12-endpoint v2 subset for lighter integrations.

## Scope

Use for: Automating restaurant workforce operations in 7shifts: scheduling and publishing shifts, capturing and reading time punches, managing employees and time off, and pulling company, location, and labor-settings data for reporting or payroll.

Not supported:
- POS sales data
- food inventory
- customer reservations
- payroll processing
- real-time streaming

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| 7shifts API | hr-recruiting | 138 | Manage restaurant scheduling, shifts, time punches, employees, and labor settings across the full 7shifts platform. |
| 7shifts Restaurant Scheduling API | hr-recruiting | 12 | Look up 7shifts companies and locations, manage shifts and schedules, and pull labor settings for restaurant scheduling and reporting integrations. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Create, publish, or edit shifts, capture time punches, manage employees, or run time-off and engagement workflows | 7-shifts | The full 138-endpoint spec is the only one that exposes shift CRUD, time punches, employees, time off, and engagement features. |
| Look up companies and locations, read labor settings, and wire OAuth for a light scheduling or reporting integration | main | The curated 12-endpoint v2 subset covers the core read surface without the full partner API, so an agent has fewer operations to reason over. |

## Cross-API use cases

### Payroll export from time punches and labor settings

A payroll integration pulls approved time punches and overtime and break rules from 7shifts to build a pay run. The full API supplies time punches while either spec supplies the labor settings and company and location scoping needed to apply the correct rules.

Example prompt: Read labor settings and locations for a company, pull time punches for the previous pay period, and emit a payroll-ready summary grouped by employee and location with regular, overtime, and break minutes.

### Multi-location labor reporting dashboard

A restaurant group monitors labor cost, overtime, and no-shows across locations. The curated v2 subset lists companies, locations, and labor settings for a lightweight overview, while the full API adds published shifts and time punches for deeper labor-cost analysis.

Example prompt: Pull companies, locations, and labor settings from the v2 subset, then fetch published shifts and time punches from the full API for the trailing four weeks and compute labor cost percentage by location.

### Progressive onboarding from core to full API

A partner starts with OAuth and tenant lookup on the curated v2 subset, then graduates to the full API for shift creation, time off, and engagement once the base integration works, without re-authenticating.

Example prompt: Exchange partner credentials for a token and confirm the company via /v2/whoami on the v2 subset, then use the same token against the full API to create next week's shifts for each location.

## Why Jentic

- **Setup:** Wiring 7shifts by hand means managing OAuth 2.0 tokens from the oauth2 endpoint, threading the company id through every path, and choosing between the full 138-endpoint API and the curated v2 subset. With Jentic you install Jentic One once, add either 7shifts API from the Jentic directory, store the credential once, and your agent calls both.
- **Permission scoping:** Because you run your own Jentic One instance, your rules decide which 7shifts operations and credentials the agent may use. Since both APIs put the company id in the URL path, a rule can pin the agent to one company and to read-only calls like listing locations and reading labor settings, so writes such as shift creation are never available unless you add them.
- **Credential handling:** Your 7shifts OAuth credentials, and any API key or basic auth secrets for the full API, are stored once and encrypted by your own Jentic One instance and injected at execution time, so they never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search the Jentic directory by intent such as 'list a company's 7shifts locations' or 'read labor settings for a company', and Jentic returns the matching operation from whichever 7shifts spec fits, along with its input schema, so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **Deputy** — Workforce and shift scheduling platform serving multiple industries; an alternative when the need is not restaurant-specific.
- **HubSpot** — CRM often holding restaurant guest contact records alongside 7shifts staff and scheduling data.
- **Asana** — Project management used for restaurant opening checklists and operational projects while 7shifts handles staff scheduling.

## FAQ

### What can an agent do across the 7shifts APIs?

An agent can provision companies and locations, build and publish shift schedules, record and read time punches, manage employees and role assignments, handle time-off approvals, push engagement announcements, and pull labor settings. The full 138-endpoint API covers all of these, while the curated v2 subset handles the core company, location, and labor-settings reads.

### Why are there two 7shifts APIs in the Jentic directory?

The full spec exposes the complete 138-endpoint 7shifts partner surface, including shift CRUD, time punches, time off, and engagement. The curated v2 subset covers twelve core endpoints for companies, locations, labor settings, OAuth, and whoami, so an agent that only needs the core read surface has fewer operations to reason over.

### Which 7shifts API should an agent use?

Use the curated v2 subset for looking up companies and locations, reading labor settings, and wiring OAuth for a light scheduling or reporting integration. Use the full API when the task needs shift creation, time punch capture, time-off approval, employee management, or engagement features.

### Do both APIs share the same credentials?

Yes. Both call api.7shifts.com and authenticate with OAuth 2.0 tokens from the /oauth2/token endpoint, so a single OAuth credential works across both specs. The full API also accepts marketing API keys and basic auth for certain legacy or marketing integrations.

### Can 7shifts give an agent sales or POS data?

No. 7shifts focuses on workforce data such as schedules, shifts, time punches, employees, and labor settings. Sales and POS figures come from the partner POS systems that integrate with 7shifts, so computing labor cost percentage means joining 7shifts labor data with sales pulled from a separate POS API.

### How does an agent scope access to a single restaurant company?

Both APIs place the company id in the URL path, such as /v2/company/{company_id}/locations, so a rule in your own Jentic One instance can pin the agent to one company and to specific read operations like listing that company's locations and reading its labor settings, while blocking writes such as shift creation or partner company creation unless you add them.