7shifts APIs for AI Agents
HR recruitingEmployee ManagementMixed Provenanceoauth2,apiKey,basicOAuth 2.0Agent Ready
7shifts API Catalog
2 APIs across 1 product group.
HR recruiting2
7shifts APIManage restaurant scheduling, shifts, time punches, employees, and labor settings across the full 7shifts platform.~138 endpoints7shifts Restaurant Scheduling APILook up 7shifts companies and locations, manage shifts and schedules, and pull labor settings for restaurant scheduling and reporting integrations.~12 endpoints
Which 7shifts API should I use?
| I want to... | Use | Why |
|---|---|---|
| Create, publish, or edit shifts, capture time punches, manage employees, or run time-off and engagement workflows | 7shifts API | 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 | 7shifts Restaurant Scheduling API | 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. |
Install Jentic One Beta
Connect the 7shifts APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 7shifts APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2F7shifts.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F7shifts.com" | 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.
Once connected, ask your agent something like: “manage 7shifts restaurant schedules, time punches, and labor settings”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
FAQs
Specific to using 7shifts APIs through Jentic.
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?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
