7shifts Restaurant Scheduling API

Name: 7shifts Restaurant Scheduling API API
Brand: 7shifts Restaurant Scheduling API
Availability: InStock

★ Only Publicly Available SpecHR recruitingEmployee Managementoauth212 EndpointsREST

For Agents

Look up 7shifts companies and locations, manage shifts and schedules, and pull labor settings for restaurant scheduling and reporting integrations.

Quickstart

Get started with 7shifts Restaurant Scheduling API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list 7shifts companies and locations"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with 7shifts Restaurant Scheduling API API.

Identify the authenticated user and tenant via /v2/whoami

List companies and the locations under each company

Retrieve labor settings, including overtime and break enforcement, per company

Look up configured inactive reasons used when removing employees

GET STARTED

Start building with 7shifts Restaurant Scheduling API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for 7shifts Restaurant Scheduling API, keeping it validated and agent-ready.

Jentic 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.

Use Cases

Patterns agents use 7shifts Restaurant Scheduling API API for, with concrete tasks.

★ Multi-Location Schedule Reporting

Restaurant groups using 7shifts pull location and labor settings data to feed weekly operations reports. The /v2/company/{company_id}/locations and /v2/company/{company_id}/labor_settings endpoints return everything needed to scope a report to the right tenant and apply the correct overtime rules. A first reporting integration is typically two to three days.

Call /v2/companies, then for each company call /v2/company/{company_id}/locations and /v2/company/{company_id}/labor_settings and emit a labor-settings summary by location.

OAuth-Based Partner Integration

Partners building integrations such as POS sync or payroll exports use this curated spec to wire OAuth, identify the tenant, and start working with locations before scaling up to additional endpoints. The /oauth2/token and /v2/whoami calls give a clean entry point that avoids learning the full 138-endpoint partner API at once. Initial setup is typically a half-day to a day.

Call POST /oauth2/token to exchange the partner credentials, then call /v2/whoami to confirm the company ID and proceed with location-level work.

Lightweight Restaurant Operations Dashboard

Operators that just need to monitor their existing 7shifts setup — labor settings, location list, inactive reasons — build a lightweight dashboard against this curated spec rather than the full API. The endpoints return all the configuration data needed for an operations overview. A single-page dashboard build is around two days.

Pull /v2/companies, /v2/company/{company_id}/locations, and /v2/company/{company_id}/inactive_reasons and render a single-page configuration overview.

AI Agent Restaurant Configuration Assistant via Jentic

An AI assistant connected through Jentic can answer configuration questions like 'what overtime rules are applied at our Toronto location' by calling /v2/company/{company_id}/labor_settings and /v2/company/{company_id}/locations. Jentic stores the OAuth token in the vault and exposes operations by intent. End-to-end response time is under ten seconds per query.

Search Jentic for '7shifts labor settings for a company', load /v2/company/{company_id}/labor_settings, and execute it for the company ID returned by /v2/whoami.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for 7shifts restaurant scheduling api, keeping it validated and agent-ready.

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 the credential can access

GET

/v2/companies/{id}

Retrieve details for a specific company

GET

/v2/company/{company_id}/locations

List locations under a company

GET

/v2/company/{company_id}/locations/{location_id}

Retrieve a specific location

GET

/v2/company/{company_id}/labor_settings

Retrieve labor settings for a company

GET

/v2/company/{company_id}/inactive_reasons

List configured inactive reasons

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 the credential can access

GET

/v2/companies/{id}

Retrieve details for a specific company

GET

/v2/company/{company_id}/locations

List locations under a company

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

7shifts OAuth client credentials and access tokens are stored encrypted in the Jentic vault (MAXsystem). Tokens are refreshed automatically and attached to requests at execution time, so the agent never sees raw secrets in its context.

Intent-based discovery

Agents search Jentic with intents like 'list 7shifts locations' or 'get labor settings for a company' and Jentic returns the matching v2 operation with its input schema, so the agent calls the right endpoint without reading the developer portal.

Time to first call

Direct integration with the 7shifts v2 surface takes about a day for OAuth and a basic location query. Through Jentic the search-load-execute flow takes under thirty minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

7shifts API (full)

Full 138-endpoint 7shifts API for partner integrations

Use the full spec when the agent needs shift CRUD, time punches, time off, or engagement features beyond the core v2 surface.

Alternative

Deputy API

Workforce and shift scheduling platform serving multiple industries

Choose Deputy when the user needs a multi-industry scheduling tool; choose 7shifts for restaurant-specific workflows.

Complementary

Asana API

Project management API for restaurant operational projects

Pair Asana with 7shifts when restaurant operations runs project work in Asana while staff scheduling stays in 7shifts.

Complementary

HubSpot CRM Contacts API

CRM commonly used for restaurant guest contact records

Pair HubSpot with 7shifts when guest CRM is separate from the staff scheduling system.

FAQs

Specific to using 7shifts Restaurant Scheduling API API through Jentic.

Why is there no official OpenAPI spec for 7shifts Restaurant Scheduling API?

7shifts publishes documentation at developers.7shifts.com but does not distribute a downloadable v2 OpenAPI specification scoped to this curated subset. Jentic generates and maintains this spec so AI agents and developers can call the core scheduling operations through structured tooling. It is validated against api.7shifts.com and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the 7shifts Restaurant Scheduling API use?

The API uses OAuth 2.0. Call POST /oauth2/token with your client credentials to receive an access token, then send it on subsequent requests. When called through Jentic the credentials are stored encrypted in the vault and the access token is refreshed automatically, so secrets never appear in the agent's prompt.

Can I list all locations for a company with this API?

Yes. Call GET /v2/company/{company_id}/locations to list every location under a company. Each location record includes name, address, and operational metadata used for scheduling.

What are the rate limits for the 7shifts Restaurant Scheduling API?

7shifts applies per-token rate limits that scale with integration tier rather than publishing a single public number. Back off on HTTP 429 responses with the Retry-After header. For dashboards, cache /v2/companies and /v2/company/{company_id}/labor_settings results since they change infrequently.

How do I retrieve labor settings through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for '7shifts labor settings', load /v2/company/{company_id}/labor_settings, and execute it with the company ID. Jentic injects the OAuth access token automatically.

How is this spec different from the full 7shifts API spec?

This curated v2 spec covers twelve core endpoints — OAuth, whoami, companies, locations, labor settings, and inactive reasons — suitable for most light integrations. The 7shifts/7-shifts spec available alongside it covers the full 138-endpoint partner surface including shift CRUD, time punches, time off, and engagement features.