7shifts is a workforce management platform built for the restaurant industry, providing employee scheduling, shift management, time tracking, tip pooling, payroll integration, and team communication in one place. Restaurants use it to reduce labor costs, improve scheduling efficiency, and keep teams aligned. Its API exposes scheduling, labor, and employee data for integration with your data ecosystem.
Power end-to-end data operations for your 7shifts API with Nexla. Our bi-directional 7shifts connector is purpose-built for 7shifts, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to 7shifts or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your 7shifts workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to 7shifts, you need a 7shifts access token and your 7shifts Company ID. Both are available from the 7shifts web application. Only Admins can generate access tokens.
7shifts access tokens are long-lived bearer tokens used to authenticate API requests. They are generated from the Developer Tools section of the 7shifts web application.
Sign in to your 7shifts account at app.7shifts.com as an Admin.
In the left navigation bar, go to Settings > Developer Tools.
Click the + Create Access Token button.
Enter a descriptive name for the token in the Access Token Name field (for example, Nexla Integration).
Select an Admin user as the Technical Contact for this token.
Click Create Access Token. Your new access token will be displayed.
Important
Copy and store your access token immediately after creation. For security reasons, you will not be able to view the full token value again after closing the dialog. If you lose the token, you will need to generate a new one.
Access tokens in 7shifts are associated with the Admin account that creates them. Only the creating Admin can view and manage the token after it is generated. For complete details, refer to the 7shifts access token documentation.
The Company ID is a numeric identifier for your 7shifts company account, used to scope API requests to your specific organization.
While signed in to your 7shifts account, navigate to Settings > Developer Tools.
Your Company ID is displayed on the Developer Tools page alongside your access tokens.
Alternatively, you can retrieve your Company ID by calling the 7shifts API endpoint https://api.7shifts.com/v2/companies using your access token — the response will contain your company's numeric ID.
The Company ID is required for most 7shifts API endpoints. It appears as the {company_id} path segment in API URLs (for example, https://api.7shifts.com/v2/company/{company_id}/shifts).
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
7shifts uses Bearer token authentication. The access token you generated in Prerequisites is supplied here as the API Key credential field and will be sent in the Authorization header of every API request as Bearer {token}. Enter the access token in the API Key field.
Enter your numeric 7shifts Company ID in the Company ID field. This value is used as the {company_id} path parameter in API endpoint URLs and scopes all requests to your specific 7shifts organization.
To verify that your credentials are valid before saving, Nexla will make a test call to the https://api.7shifts.com/v2/whoami endpoint. A successful response confirms that the access token and company ID are correct.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Select the 7shifts connector tile from the list of available connectors, then select the credential that will be used to connect to the 7shifts instance, and click Next; or, create a new 7shifts credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common 7shifts endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Get Company
Retrieves details of a specific company by its ID. Use this endpoint to pull your 7shifts company profile information, including company name, settings, and configuration details. This is useful for auditing company configuration or seeding reference data in downstream systems.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. Nexla will automatically use the Company ID from your 7shifts credential to scope the request to your organization.
The response data is returned under the $.data path, which Nexla uses automatically for this template.
Returns the identity and details of the currently authenticated user or token. Use this endpoint to verify which 7shifts user is associated with the active credential, or to retrieve the authenticated user's profile data for auditing or downstream processing.
This endpoint requires no additional parameters. It calls the https://api.7shifts.com/v2/whoami endpoint using the access token in your credential.
The response includes fields such as the user's ID, name, email, and role within the company.
This endpoint is also used by Nexla to validate your 7shifts credential on creation. For more details, see the 7shifts authentication documentation.
Get Labor Settings
Returns labor configuration settings for your company, including overtime rules, break policies, and pay period settings. Use this endpoint to replicate labor policy data into analytics platforms or to verify that your 7shifts labor configuration aligns with your payroll system.
This endpoint requires no additional parameters beyond the Company ID stored in your credential.
The response data is returned under the $.data path.
Labor settings govern how overtime, breaks, and pay calculations are applied to your workforce. For more details on each field, refer to the 7shifts Labor Settings documentation.
Get Tip Pool Settings
Returns tip pool configuration settings for your company. Use this endpoint to retrieve tip distribution rules and policies for downstream payroll or financial reporting systems.
This endpoint requires no additional parameters beyond the Company ID stored in your credential.
The response data is returned under the $.data path.
Returns details for a specific role within your company, such as role name, location association, and pay settings. Use this endpoint when you need to retrieve the full profile of a specific job role for HR or scheduling analytics.
Enter the numeric ID of the role to retrieve in the Role ID field. This is the unique identifier assigned to the role in 7shifts.
Role IDs can be obtained by first running the List Roles endpoint, which returns all roles for your company along with their IDs.
The Role ID is not required — if left blank, the endpoint will attempt to retrieve without a specific role filter, but providing it ensures you retrieve the correct record.
The response data is returned under the $.data path.
Retrieves details of a single shift by its ID, including the assigned employee, location, department, role, start and end times, and any notes. Use this endpoint when you need to fetch full details for a specific known shift.
Enter the numeric ID of the shift to retrieve in the Shift ID field.
Shift IDs can be obtained by first running the List Shifts endpoint to get a list of shifts with their corresponding IDs.
The response data is returned under the $.data path.
Returns details for a single time punch record, including clock-in and clock-out times, break duration, and the associated employee and location. Use this endpoint when you need to retrieve a specific time punch record for payroll verification or audit purposes.
Enter the numeric ID of the time punch record to retrieve in the Time Punch ID field.
Time punch IDs can be obtained by first running the List Time Punches endpoint, which returns all time punch records for your company.
The response data is returned under the $.data path.
Retrieves detailed profile information for a single user in your company, including name, contact information, employment status, and assigned roles. Use this endpoint when you need the complete profile of a specific employee.
Enter the numeric ID of the user to retrieve in the User ID field.
User IDs can be obtained by first running the List Users endpoint, which returns all users for your company along with their IDs.
The response data is returned under the $.data path.
Retrieves the location, department, and role assignments for a specific user in your company. Use this endpoint to understand where an employee is assigned to work and what roles they hold across locations and departments.
Enter the numeric ID of the user whose assignments you want to retrieve in the User ID field.
User IDs can be obtained from the List Users endpoint or the Get User endpoint.
The response data is returned as an array under the $.data[*] path, with each element representing a separate assignment.
Retrieves all location, department, and role assignments for a specified user. Use this endpoint to get a complete view of an employee's cross-location responsibilities and role assignments for HR reporting or access auditing.
Enter the numeric User ID in the User ID field. This parameter is required.
User IDs are available from the List Users endpoint.
The response data is returned as an array under the $.data[*] path.
Retrieves all companies accessible via your API key. This is useful when your access token is associated with multiple companies, such as in multi-location franchise or enterprise scenarios, and you need to enumerate available company IDs.
This endpoint requires no additional parameters. It uses cursor-based pagination to handle large result sets, automatically fetching up to 100 companies per page.
The response data is returned as an array under the $.data[*] path, with pagination handled automatically by Nexla.
This endpoint is particularly useful for identifying the correct Company ID to use in your 7shifts credential. For more details, see the 7shifts List Companies API reference.
List User Department Assignments
Retrieves all department assignments for a specific user. Use this endpoint to see which departments an employee is assigned to within your company, which is useful for scheduling analysis, HR records, and cost center reporting.
Enter the numeric User ID in the User ID field. This parameter is required.
User IDs are available from the List Users endpoint.
The response data is returned as an array under the $.data[*] path.
Retrieves all departments for your company. Departments in 7shifts represent sub-groups within a location (for example, Front of House or Back of House). Use this endpoint to build organizational hierarchies, map employees to cost centers, or replicate department structures into downstream systems.
This endpoint requires no additional parameters. It uses cursor-based pagination, automatically fetching up to 100 departments per page.
The response data is returned as an array under the $.data[*] path.
Returns a paginated list of calendar events for your company, including holidays and manager notes. Use this endpoint to synchronize scheduling events with external calendars or labor planning tools.
The following optional filter parameters are available for this endpoint:
Location ID: Filter events to a specific location. Leave blank to retrieve events across all locations.
Start Date (Greater Than or Equal): Filter to events starting on or after this date. Use ISO 8601 format (e.g., 2024-01-01).
Start Date (Less Than or Equal): Filter to events starting on or before this date. Use ISO 8601 format.
Modified Since: Return only events modified after this timestamp. Useful for incremental data loads.
Limit: Set the maximum number of events returned per page. If left blank, the endpoint uses its default page size.
Cursor: Pagination cursor for fetching subsequent pages. Nexla manages this automatically when pagination is enabled.
The response data is returned as an array under the $.data[*] path, with pagination handled automatically using cursor-based pagination.
Returns a paginated list of external user mappings between 7shifts users and external system identifiers. Use this endpoint to retrieve the linkage between 7shifts employee records and user IDs in connected external systems such as payroll platforms or POS systems.
The following optional filter parameters are available:
Modified Since: Return only mappings modified after this timestamp. Useful for incremental sync scenarios.
Limit: Set the maximum number of mappings returned per page.
Cursor: Pagination cursor. Nexla manages this automatically.
The response data is returned as an array under the $.data[*] path with cursor-based pagination.
External user mappings are typically used in payroll and POS integrations to associate 7shifts employees with their counterparts in other systems. For more details, refer to the 7shifts External User Mappings documentation.
List Inactive Reasons
Returns the list of valid inactive (departure) reason codes for your company. These codes are used when deactivating users to categorize the reason for their departure (for example, resignation, termination, or leave of absence). Use this endpoint to populate picklist values in HR systems or to enrich employee departure records.
This endpoint requires no additional parameters beyond the Company ID stored in your credential.
The response data is returned as an array under the $.data[*] path.
Retrieves all location assignments for a specific user. Use this endpoint to determine which physical locations an employee is authorized to work at across your organization.
Enter the numeric User ID in the User ID field. This parameter is required.
User IDs are available from the List Users endpoint.
The response data is returned as an array under the $.data[*] path.
Retrieves all locations for your company. Locations represent physical restaurant or business sites in 7shifts. Use this endpoint to replicate location data into analytics platforms, reporting systems, or to map shifts and employees to physical sites.
This endpoint requires no additional parameters. It uses cursor-based pagination, fetching up to 100 locations per page automatically.
The response data is returned as an array under the $.data[*] path.
Retrieves all role assignments for a specific user. Use this endpoint to see which job roles an employee holds across your company's locations and departments, which is useful for pay rate analysis and scheduling optimization.
Enter the numeric User ID in the User ID field. This parameter is required.
User IDs are available from the List Users endpoint.
The response data is returned as an array under the $.data[*] path.
Retrieves all roles defined for your company. Roles in 7shifts represent job positions such as Server, Bartender, or Cook, and are associated with departments and locations. Use this endpoint to synchronize role data into HR or payroll systems.
This endpoint requires no additional parameters. It uses cursor-based pagination, fetching up to 100 roles per page automatically.
The response data is returned as an array under the $.data[*] path.
Returns a paginated list of shift feedback submissions from employees for your company. Shift feedback is collected after employees complete their shifts and can include ratings and comments. Use this endpoint to analyze employee satisfaction, identify scheduling issues, or feed engagement metrics into workforce analytics platforms.
The following optional filter parameters are available:
Location ID: Filter feedback to a specific location.
Modified Since: Return only feedback modified after this timestamp. Useful for incremental data sync.
Limit: Set the maximum number of feedback entries returned per page.
Cursor: Pagination cursor. Nexla manages this automatically.
The response data is returned as an array under the $.data[*] path with cursor-based pagination.
Retrieves a paginated list of all shift records for your company, including shift start and end times, assigned employees, locations, departments, and roles. Use this endpoint for labor analytics, payroll processing, schedule auditing, or syncing shift data into external workforce management systems.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. It uses cursor-based pagination, fetching up to 100 shifts per page automatically.
The response data is returned as an array under the $.data[*] path.
For a full description of shift fields and filtering options available via the API, refer to the 7shifts Shifts documentation.
List Time Punches
Retrieves a paginated list of time punch records for your company, including clock-in and clock-out times, break information, and associated employee and location details. Use this endpoint to feed actual hours worked into payroll systems, conduct labor cost analysis, or compare scheduled versus actual hours.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. It uses cursor-based pagination, fetching up to 100 records per page automatically.
The response data is returned as an array under the $.data[*] path.
Retrieves all users (employees) for your company, including their profile information, employment status, and account details. Use this endpoint to synchronize your employee roster into HR systems, payroll platforms, or workforce analytics tools.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. It uses cursor-based pagination, fetching up to 100 users per page automatically.
The response data is returned as an array under the $.data[*] path.
Retrieves wage information for a specific user, including pay rates across roles. Use this endpoint to feed compensation data into payroll systems, labor cost models, or HR reporting tools.
Enter the numeric User ID in the User ID field. This parameter is required.
User IDs are available from the List Users endpoint.
The response data is returned as an array under the $.data[*] path.
Returns a paginated list of all webhooks registered for your company. Use this endpoint to audit, monitor, or replicate your 7shifts webhook configuration into external documentation or change management systems.
The following optional filter parameters are available:
Modified Since: Return only webhooks modified after this timestamp.
Limit: Set the maximum number of webhooks returned per page.
Cursor: Pagination cursor. Nexla manages this automatically.
The response data is returned as an array under the $.data[*] path with cursor-based pagination.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
7shifts data sources can also be manually configured to ingest data from any valid 7shifts API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The 7shifts API base URL is https://api.7shifts.com/v2/. All endpoint paths are appended to this base URL — for example, https://api.7shifts.com/v2/company/{company_id}/shifts, where {company_id} is your numeric 7shifts Company ID. You do not need to add the Authorization header manually — Nexla adds it automatically using the Bearer token from your credential. Because all payload data is nested under a data key (with pagination metadata under meta), set the path to data to $.data[*] for list endpoints or $.data for single-object endpoints, and optionally set $.meta as the metadata path.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new 7shifts data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the 7shifts destination, and select the Send to Destination option from the menu. Select the 7shifts connector from the list of available destination connectors, then select the credential that will be used to connect to the 7shifts organization, and click Next; or, create a new 7shifts credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common 7shifts write endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Shift
Creates a new shift for a specific location and user. Use this endpoint to programmatically create shift records in 7shifts from external scheduling systems, HR platforms, or data transformation flows. This is the primary write operation for shift scheduling.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. Nexla will POST the Nexset data as a JSON body to the 7shifts Shifts API.
The data being sent must conform to the 7shifts shift creation schema. Key fields include:
location_id: The numeric ID of the location where the shift will take place (required).
user_id: The numeric ID of the employee assigned to the shift.
department_id: The numeric ID of the department for this shift.
role_id: The numeric ID of the role for this shift.
start: The shift start time in ISO 8601 format (e.g., 2024-06-01T09:00:00).
Updates an existing shift identified by its ID. Use this endpoint to modify shift details such as start/end times, assigned employee, location, or role. This is useful for syncing schedule changes from external systems into 7shifts.
Enter the numeric ID of the shift to update in the Shift ID field. This parameter is required.
Shift IDs can be obtained from the List Shifts or Get Shift source endpoints.
The Shift ID is appended to the API URL as a path parameter to identify the specific shift record to update.
Nexla will send the Nexset data as a JSON body using a PUT request, which replaces the full shift record with the provided data.
Creates a new department within your company. Use this endpoint to programmatically set up department structures in 7shifts when onboarding new locations or reorganizing your organizational hierarchy.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. Nexla will POST the Nexset data as a JSON body to the 7shifts Departments API.
Key fields for creating a department include:
location_id: The numeric ID of the location this department belongs to (required).
name: The display name of the department (required).
Updates an existing department identified by its ID. Use this endpoint to modify department names or settings when organizational structure changes occur.
Enter the numeric ID of the department to update in the Department ID field. This parameter is required.
Department IDs can be obtained from the List Departments source endpoint.
Nexla will send the Nexset data as a JSON body using a PUT request.
For a complete list of updatable department fields, refer to the 7shifts API documentation for departments.
Create Role
Creates a new role within your company. Roles represent job positions such as Server, Bartender, or Cook. Use this endpoint to programmatically create role definitions when setting up new locations or job classifications.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. Nexla will POST the Nexset data as a JSON body to the 7shifts Roles API.
Key fields for creating a role include:
department_id: The numeric ID of the department this role belongs to (required).
Updates an existing role identified by its ID. Use this endpoint to modify role names, pay settings, or department associations when job classification changes occur.
Enter the numeric ID of the role to update in the Role ID field. This parameter is required.
Role IDs can be obtained from the List Roles source endpoint or the Retrieve Role Details source endpoint.
Nexla will send the Nexset data as a JSON body using a PUT request.
Creates a new user (employee) within your company. Use this endpoint to onboard new employees into 7shifts programmatically from an HR system, payroll platform, or employee management tool.
This endpoint requires no additional parameters beyond the Company ID stored in your credential. Nexla will POST the Nexset data as a JSON body to the 7shifts Users API.
Key fields for creating a user include:
firstname: The employee's first name (required).
lastname: The employee's last name (required).
email: The employee's email address.
mobile_phone: The employee's mobile phone number.
employee_id: An external employee identifier for integration with payroll or HR systems.
For the complete list of user creation fields, including required fields and accepted values, refer to the 7shifts Create User API reference.
Update User
Updates an existing user identified by their ID. Use this endpoint to synchronize employee profile changes from HR systems into 7shifts, such as name changes, contact information updates, or employment status changes.
Enter the numeric ID of the user to update in the User ID field. This parameter is required.
User IDs can be obtained from the List Users or Get User source endpoints.
Nexla will send the Nexset data as a JSON body using a PUT request, replacing the full user record with the provided data.
For the complete list of updatable user fields, refer to the 7shifts Users API documentation. Ensure that required fields are included in the payload when performing a full PUT update.
Update Location
Updates an existing location identified by its ID. Use this endpoint to modify location details such as name, address, time zone, or operational settings when business information changes.
Enter the numeric ID of the location to update in the Location ID field. This parameter is required.
Location IDs can be obtained from the List Locations source endpoint.
Nexla will send the Nexset data as a JSON body using a PUT request.
7shifts destinations can also be manually configured to send data to any valid 7shifts API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The 7shifts API accepts JSON for all write operations. For update operations, include the ID of the resource to be updated at the end of the URL — for example, https://api.7shifts.com/v2/company/{company_id}/shifts/{shift_id}. You do not need to add the Authorization or Content-Type headers manually — Nexla adds these automatically using the Bearer token from your credential and the selected content format.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured 7shifts endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to 7shifts until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
