Deputy API

Name: Deputy API API
Brand: Deputy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer27 EndpointsREST

For Agents

Manage Deputy employees, rosters, timesheets, leave, locations, departments, and sales metrics, plus retrieve the signed-in user's own schedule.

Quickstart

Get started with Deputy 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:
"publish a deputy roster"

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

Capabilities

What an agent can do with Deputy API API.

Add, update, terminate, and re-activate employees through the supervise/employee endpoints

Publish rosters and list scheduled shifts via /v1/supervise/roster endpoints

Start and end timesheets to drive a clock-on and clock-off flow

Add and read employee leave records via /v1/supervise/leave

GET STARTED

Start building with Deputy API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Deputy API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Deputy API, keeping it validated and agent-ready. Deputy is a workforce management platform for shift-based businesses covering employee records, rostering, timesheets, leave, locations, and sales metrics. The API exposes 27 endpoints across employee lifecycle, roster publishing, time clock operations, leave management, sales metrics, and the authenticated user's own roster and timesheets. Authentication uses Bearer tokens and the base URL is parameterised by install and geographic region.

Use Cases

Patterns agents use Deputy API API for, with concrete tasks.

★ Employee Onboarding Automation

Push new joiners from an HRIS into Deputy by calling POST /v1/supervise/employee, then send the welcome invite via POST /v1/supervise/employee/{employeeid}/invite. Termination flows mirror this with the terminate endpoint, keeping Deputy in sync with the HR source of truth without manual data entry.

Call POST /v1/supervise/employee with the new hire details, then POST /v1/supervise/employee/{employeeid}/invite to send the app invite.

Roster Publishing Workflow

Build draft schedules in an external planner and publish them into Deputy via POST /v1/supervise/roster/publish, using GET /v1/supervise/roster to confirm the published shifts. This pattern is common for operations teams that prefer a custom forecasting tool but still want Deputy as the system of record for shifts.

Call POST /v1/supervise/roster/publish with the prepared schedule payload, then GET /v1/supervise/roster to verify the publish.

Time Clock for Custom Apps

Power a branded clock-on and clock-off experience by calling POST /v1/supervise/timesheet/start and POST /v1/supervise/timesheet/end from a kiosk app. GET /v1/supervise/timesheet/{timesheetid}/details closes the loop for confirmation and audit, replacing the default Deputy app where the use case demands a custom UI.

When the employee taps clock on, call POST /v1/supervise/timesheet/start with their employee id; on tap clock off, call POST /v1/supervise/timesheet/end.

Sales-Driven Forecasting

Feed sales metrics from the POS into Deputy via POST /v2/metrics, and pull historical data with GET /v2/metrics/raw to evaluate roster effectiveness. This closes the loop between revenue and labour planning for retail and hospitality operators.

Each evening, push the day's sales totals via POST /v2/metrics keyed by location id.

AI Agent Integration via Jentic

An ops agent can use Jentic to handle one-off Deputy tasks like terminating an employee, publishing a roster, or pulling the signed-in user's schedule for a question. Jentic resolves the Bearer token and the install/geo base URL parameters, so the agent does not need to manage tenant-specific URL building.

Use Jentic to search for 'publish a deputy roster', load POST /v1/supervise/roster/publish, and execute it with the prepared schedule.

Key Endpoints

27 endpoints — jentic publishes the only available openapi specification for deputy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/supervise/employee

Add a new employee

POST

/v1/supervise/employee/{employeeid}/invite

Invite an employee to Deputy

POST

/v1/supervise/roster/publish

Publish a roster

POST

/v1/supervise/timesheet/start

Start a timesheet (clock on)

POST

/v1/supervise/timesheet/end

End a timesheet (clock off)

POST

/v1/supervise/leave

Add leave for an employee

POST

/v2/metrics

Add a sales metric

GET

/v1/my/roster

Get my roster

POST

/v1/supervise/employee

Add a new employee

POST

/v1/supervise/employee/{employeeid}/invite

Invite an employee to Deputy

POST

/v1/supervise/roster/publish

Publish a roster

POST

/v1/supervise/timesheet/start

Start a timesheet (clock on)

POST

/v1/supervise/timesheet/end

End a timesheet (clock off)

Why though Jentic?

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

Credential isolation

Deputy Bearer tokens are stored encrypted in the Jentic vault. Agents reference operations and Jentic injects the Authorization header at execution time, keeping tokens out of prompts and logs.

Intent-based discovery

Agents search by intent such as 'publish a deputy roster' or 'clock an employee on' and Jentic returns the matching operation with its full input schema, so the agent does not need to read Deputy's documentation to act.

Time to first call

Direct Deputy integration: 2-3 days to wire auth, the install/geo base URL, and the employee or roster lifecycle. Through Jentic: under an hour to chain employee, roster, and timesheet calls.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

7shifts API

Restaurant-focused scheduling and labour platform with similar shift and timesheet endpoints.

Choose 7shifts when the operator is a restaurant brand using 7shifts rather than Deputy.

Alternative

Rippling API

Unified HR, payroll, and IT platform that overlaps with Deputy on employee records.

Choose Rippling when the customer needs payroll and IT alongside scheduling rather than a focused workforce-management product.

Complementary

Gusto API

US payroll provider that consumes timesheets exported from Deputy.

Use Gusto alongside Deputy when timesheet data needs to feed US payroll runs.

Complementary

BambooHR API

HRIS that owns employee records often synced into Deputy on hire.

Use BambooHR alongside Deputy when BambooHR is the source of truth for employee data and Deputy handles scheduling.

FAQs

Specific to using Deputy API API through Jentic.

Why is there no official OpenAPI spec for Deputy API?

Deputy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Deputy API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Deputy API use?

The Deputy API uses HTTP Bearer token authentication. Tokens are issued from your Deputy install and passed in the Authorization header. Through Jentic, tokens are stored encrypted in the vault and never exposed to the agent.

Can I publish a roster with the Deputy API?

Yes. POST /v1/supervise/roster/publish publishes a prepared schedule, and GET /v1/supervise/roster lists existing rosters so you can confirm what shifts are now live.

How do I clock an employee on and off through the Deputy API?

Call POST /v1/supervise/timesheet/start to clock the employee on and POST /v1/supervise/timesheet/end to clock them off. GET /v1/supervise/timesheet/{timesheetid}/details lets you fetch the resulting timesheet for review.

What is the base URL for the Deputy API?

Deputy uses a tenant-specific URL of the form https://{install}.{geo}.deputy.com/api, where install is your Deputy subdomain and geo is the regional cluster (for example au, na, or eu). Both placeholders must be substituted before calling any endpoint.

How do I add a new employee through Jentic?

Run `pip install jentic`, search for 'add a deputy employee', execute POST /v1/supervise/employee with the new hire payload, and follow up with POST /v1/supervise/employee/{employeeid}/invite. Jentic uses the stored Bearer token for both calls.