Workday Absence Management
Browse all Workday APIs★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementoauth214 EndpointsREST
For Agents
Query worker time-off balances, retrieve leave-of-absence records, and submit time-off requests for any worker in a Workday tenant.
Use for: I need to check a worker's remaining vacation balance, I want to submit a time-off request for an employee, List all eligible absence types for a specific worker, Retrieve the leave-of-absence history for a team member
Not supported: Does not handle payroll processing, recruiting, compensation planning, or performance reviews — use for absence and time-off management only.
Jentic publishes the only available OpenAPI specification for Workday Absence Management, keeping it validated and agent-ready. Access worker leave-of-absence records, time-off balances, and eligible absence types through a tenant-scoped REST interface. Submit time-off requests on behalf of workers, retrieve valid time-off dates, and query leave status across the organisation. Supports 14 endpoints covering balance retrieval, leave-of-absence history, and time-off request workflows.
Install Jentic One Beta
Connect the Workday Absence Management to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Workday Absence Management, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Workday Absence Management API.
Retrieve current time-off balances for individual workers or across the organisation
Submit time-off requests with date ranges and absence type selection
Query eligible absence types available to a specific worker
Track leave-of-absence status including start dates, expected return, and approval state
Pull valid time-off dates to prevent scheduling conflicts before submission
Export time-off detail history for payroll reconciliation and reporting
Use Cases
Patterns agents use Workday Absence Management API for, with concrete tasks.
★ AI Agent Leave Management
AI agents use the Workday Absence Management API through Jentic to automate time-off workflows without direct Workday tenant access. An agent searches for absence operations, loads the schema for the requestTimeOff endpoint, and submits leave requests with the correct absence type and date range. The agent verifies valid dates first via the validTimeOffDates endpoint, preventing rejected submissions.
Check valid time-off dates for worker ID W001, then submit a 3-day vacation request starting next Monday using the requestTimeOff endpoint
Time-Off Balance Reporting
Pull real-time time-off balances for all workers or specific individuals to feed into dashboards, payroll systems, or manager portals. The balances endpoint returns accrued, used, and remaining hours for each absence plan assigned to a worker. Integrations typically poll balances weekly for reconciliation with payroll or surface them in self-service portals.
Retrieve the time-off balance for worker ID W001 and return the remaining hours for each absence plan
Leave of Absence Tracking
Track active and historical leaves of absence across the workforce. The leavesOfAbsence sub-resource under each worker provides leave type, start date, expected return date, and current status. HR teams integrate this data with workforce planning tools to manage coverage during extended absences.
List all active leaves of absence for worker ID W001 and return the leave type, start date, and expected return date
Absence Eligibility Verification
Before submitting a time-off request, verify which absence types a worker is eligible for based on their employment status, tenure, and plan enrolment. The eligibleAbsenceTypes endpoint returns the full list of available leave categories for a specific worker, enabling self-service portals and chatbots to present only valid options.
Retrieve all eligible absence types for worker ID W001 and filter for types that allow half-day increments
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for workday absence management, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/balances
List all time-off balances
GET
/balances/{ID}
Get a specific balance record
GET
/workers/{ID}/eligibleAbsenceTypes
List eligible absence types for a worker
GET
/workers/{ID}/leavesOfAbsence
List leaves of absence for a worker
POST
/workers/{ID}/requestTimeOff
Submit a time-off request
GET
/workers/{ID}/timeOffDetails
Get time-off details for a worker
GET
/workers/{ID}/validTimeOffDates
Get valid dates for time-off requests
GET
/balances
List all time-off balances
GET
/balances/{ID}
Get a specific balance record
GET
/workers/{ID}/eligibleAbsenceTypes
List eligible absence types for a worker
GET
/workers/{ID}/leavesOfAbsence
List leaves of absence for a worker
POST
/workers/{ID}/requestTimeOff
Submit a time-off request
GET
/workers/{ID}/timeOffDetails
Get time-off details for a worker
GET
/workers/{ID}/validTimeOffDates
Get valid dates for time-off requests
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Workday OAuth 2.0 tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens tied to a specific tenant — raw client secrets and authorization URLs never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'check worker time off balance') and Jentic returns matching Workday Absence Management operations with their input schemas, so the agent can call the right endpoint without navigating Workday's tenant-specific documentation.
Time to first call
Direct Workday integration: 3-7 days for OAuth setup, tenant configuration, and endpoint discovery. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Workday Absence Management API through Jentic.
Why is there no official OpenAPI spec for Workday Absence Management?
Workday does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Workday Absence Management 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 Workday Absence Management API use?
The API uses OAuth 2.0 with an implicit grant flow. Each request requires a valid access token obtained from the tenant-specific authorization hostname. Through Jentic, OAuth tokens are managed in the MAXsystem vault so agents never handle raw credentials directly.
Can I submit time-off requests through the Workday Absence Management API?
Yes. The POST /workers/{ID}/requestTimeOff endpoint accepts a time-off request with the absence type, date range, and optional comments. Before submitting, call GET /workers/{ID}/validTimeOffDates to confirm the dates are available and GET /workers/{ID}/eligibleAbsenceTypes to verify the worker qualifies for the selected leave type.
What are the rate limits for the Workday Absence Management API?
Workday enforces tenant-level rate limits that vary by subscription tier, typically allowing 30-60 requests per minute per integration. The API returns HTTP 429 with a Retry-After header when limits are exceeded. Jentic handles automatic retry with exponential backoff for agent-initiated calls.
How do I retrieve a worker's time-off balance through Jentic?
Search Jentic for 'check worker time off balance', load the schema for GET /balances/{ID} or GET /workers/{ID}/timeOffDetails, and execute the call with the worker's Workday ID. The response includes accrued hours, used hours, and remaining balance per absence plan. Install with pip install jentic and authenticate at https://app.jentic.com/sign-up.
Does the API support querying multiple workers' absence data at once?
Yes. The GET /workers endpoint returns a paginated list of all workers with absence data. The GET /balances endpoint similarly returns balances across all workers. Both support query parameters for filtering by specific criteria, enabling bulk reporting and dashboard integrations.
GET STARTED