7shifts API Documentation
This is the complete API documentation for connecting to the 7shifts API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet 7shifts: Restaurant workforce platform for scheduling, time punches, labor, user, role, department, and location data through the 7shifts API. Keep reading to get started.
Quickstart
Before you run your first 7shifts request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one 7shifts connection — create or choose one in Connections. Note its
connectionId.
Every 7shifts action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/shifts/latest/actions/{actionSlug}You need a MindCloud API Key and a 7shifts connection. Then call an action such as Get User Contacts:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/shifts/latest/actions/get-user-contacts" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected 7shifts account that should run the action. MindCloud stores and refreshes the 7shifts credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
7shifts actions
All 40 published actions for this 7shifts version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate Department
- POSTCreate Employment Record
- POSTCreate Location
- POSTCreate Role
- POSTCreate Role Assignment
- POSTCreate Shift
- POSTCreate Time Punch
- POSTCreate User
- POSTCreate User Wage
- DELETEDeactivate User
- DELETEDelete Shift
- GETGet User Contacts
- GETList Assignments
- GETList Companies
- GETList Departments
- GETList Employment Records
- GETList Locations
- GETList Role Assignments
- GETList Roles
- GETList Shifts
- GETList Time Punches
- GETList User Wages
- GETList Users
- GETList Users Authorized Locations
- GETRetrieve Company
- GETRetrieve Department
- GETRetrieve Identity
- GETRetrieve Labor Settings
- GETRetrieve Location
- GETRetrieve Role
- GETRetrieve Shift
- GETRetrieve Time Punch
- GETRetrieve User
- GETRetrieve User Contact
- PUTUpdate Department
- PUTUpdate Location
- PUTUpdate Role
- PUTUpdate Shift
- PUTUpdate Time Punch
- PUTUpdate User
Related apps
More Productivity apps on the Universal API, behind the same REST shape. Or browse all apps.