canonical: https://jentic.com/apis/workday.com/workday-absence-management # Workday Absence Management 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. ## For AI agents Query worker time-off balances, retrieve leave-of-absence records, and submit time-off requests for any worker in a Workday tenant. ## Scope Does not handle payroll processing, recruiting, compensation planning, or performance reviews - use for absence and time-off management only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Retrieve all eligible absence types for worker ID W001 and filter for types that allow half-day increments ## Key endpoints | 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 | ## Key resources - **Balances** — Time-off balance records showing accrued, used, and remaining hours per absence plan - **Workers** — Worker profiles with sub-resources for leaves, eligible types, time-off details, and requests - **Leaves of Absence** — Leave records including type, status, dates, and return expectations - **Prompt Values** — Lookup values for leave status and time-off status enumerations ## Why Jentic - **Setup:** Wiring Workday Absence Management by hand means running its OAuth2 flow against a tenant-specific authorization host, building your tenant hostname into the absenceManagement/v2 base, and threading the worker id through every path yourself. Through Jentic you install once, import Workday Absence Management from the API Directory, store the OAuth client once, and your agent calls it. - **Permission scoping:** Workday puts the worker and balance ids in the URL path (/workers/{ID}/timeOffDetails), so a rule can pin your agent to reading a worker's balances and time-off details. You choose the operations it may call, so writes like requesting time off are not included unless you add them. - **Credential handling:** Your Workday OAuth client is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check a worker's time-off balance' or 'request time off', and Jentic returns the matching Workday Absence Management operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **BambooHR API** — Full HR platform with time-off management plus employee records, onboarding, and payroll - **HiBob API** — Modern HRIS with time-off tracking, employee profiles, and lifecycle management - **Personio API** — European HR platform covering absence, attendance, payroll, and recruiting ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Workday Absence Management API? Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. Workday puts the worker and balance IDs in the URL path, such as /workers/{ID}/timeOffDetails, so you can pin the agent to read-only operations like GET /balances or GET /workers/{ID}/leavesOfAbsence for a specific worker. Write operations such as POST /workers/{ID}/requestTimeOff stay out of reach unless you explicitly allow them.