Authenticate with 7shifts using OAuth 2.0, capturing the access token and x-company-guid for the restaurant company.
When an employee requests a swap, POST to the shift trade or swap endpoint in the 7shifts API (see the API reference for the current endpoint path) with the shift IDs of both employees and the requesting employee's user ID.
Retrieve pending swap requests via GET on the swap/trade resource filtered by status to surface requests requiring manager review.
PUT or PATCH the swap request object with status: approved or status: denied and include a manager user ID to record the approving manager.
On approval, the 7shifts system updates the schedule automatically; retrieve both affected shift records to confirm the employee assignments have been exchanged.
Trigger downstream notifications (e.g., via your own messaging system) to inform both employees and their manager of the confirmed swap outcome.
Known gotchas
7shifts enforces role and position matching for shift swaps; an API-approved swap between employees with incompatible roles may be rejected or may silently create a coverage gap.
Swap request endpoints and their payload schemas should be verified against the current 7shifts API reference at developers.7shifts.com, as endpoint paths can change between API versions.
The 7shifts API rate limit of 10 requests per second applies across all API calls for a given access token; high-frequency swap approval workflows in large restaurant groups can hit this limit.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp