canonical: https://jentic.com/apis/workday.com

# Workday APIs

Workday is a human capital management (HCM) platform. This vendor covers four Workday REST APIs on the Jentic API Directory that let AI agents work with worker data inside a Workday tenant: Staffing manages jobs, job changes, organization assignments, and worker skill items across 144 operations; Person reads and updates worker personal information, contact details, home and work addresses, and country name configuration across 112 operations; Performance Enablement reads feedback badges, feedback events, and worker goals across 23 operations; and Workday Absence Management, the only OpenAPI specification Jentic publishes for it, covers time-off balances, leave-of-absence records, and time-off requests across 14 operations. All four are tenant-scoped and secured with OAuth 2.0.

## For AI agents

An agent can read and update worker records in a Workday tenant across staffing, personal and contact information, performance feedback and goals, and absence management, including submitting job changes, updating contact details, retrieving feedback and goals, and filing time-off requests. Every call is tenant-scoped and authorized with the same Workday OAuth 2.0 model.

## Scope

Use for: Reading and updating worker records in a Workday tenant across staffing, personal and contact data, performance feedback and goals, and absence and time-off management, all through tenant-scoped OAuth 2.0 REST APIs.

Not supported:
- payroll processing
- compensation planning
- recruiting
- benefits enrollment
- financial management

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| staffing | social-media | 144 | Programmatically returns the location information for the specified job change id., initiates an organization assignment change for a specific worker.. |
| person | developer-tools | 112 | Programmatically validates phone number data to ensure it is valid for workday., retrieves a collection of personal information.. |
| performanceEnablement | social-media | 23 | Programmatically retrieves a collection of active feedback badges., retrieves a single self-requested feedback event instance for the specified work. |
| Workday Absence Management | hr-recruiting | 14 | Query worker time-off balances, retrieve leave-of-absence records, and submit time-off requests for any worker in a Workday tenant. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Manage jobs, job changes, organization assignments, and worker skill items | workday-staffing | Staffing covers job changes, organization assignment changes, supervisory organizations, and worker skill items across 144 operations |
| Read or update worker personal, name, and contact information | workday-person | Person handles personal information, home and work addresses, additional names, phone validation, and country name configuration across 112 operations |
| Read feedback badges, feedback events, and worker goals | workday-performance-enablement | Performance Enablement exposes feedback badges, requested and given feedback events, and worker goals across 23 operations |
| Check time-off balances or file leave and time-off requests | main | Workday Absence Management covers balances, eligible absence types, leaves of absence, valid time-off dates, and time-off requests across 14 operations |

## Cross-API use cases

### Onboard a worker's job change and profile

When a worker moves into a new role, an agent initiates the organization assignment change through Staffing, then updates the worker's home and work contact information and additional names through Person so the tenant record reflects the move.

Example prompt: Initiate an organization assignment change for worker W001 via Staffing, then update the worker's home address and phone number via Person

### Assemble a worker performance snapshot

An agent gathers a worker's staffing context, including current job change and skill items from Staffing, alongside their feedback badges, feedback events, and goals from Performance Enablement to build a review-ready summary.

Example prompt: Read skill items for worker W001 from Staffing and their goals and active feedback events from Performance Enablement, then compile a snapshot

### Verify eligibility before filing time off

Before submitting a leave request, an agent reads the worker's personal and contact details from Person, then checks eligible absence types and valid time-off dates through Absence Management and submits the time-off request only when it qualifies.

Example prompt: Confirm worker W001's personal record via Person, check eligible absence types and valid dates via Absence Management, then submit a time-off request

### Reconcile leave against staffing changes

An agent pulls active leaves of absence and time-off balances from Absence Management and cross-references them with pending job changes and organization assignment changes from Staffing to flag coverage gaps during transitions.

Example prompt: List active leaves of absence and balances via Absence Management, then read pending job changes via Staffing and flag workers on leave with open changes

## Why Jentic

- **Setup:** Wiring Workday by hand means running the OAuth 2.0 flow against a tenant-specific authorization host and building your tenant hostname into four separate service bases (staffing/v6, person/v4, performanceEnablement/v5, absenceManagement/v2). Through Jentic you install Jentic One once, add the Workday APIs you need from the Jentic directory, store the OAuth client once, and your agent calls all four.
- **Permission scoping:** Workday puts the worker, person, or job-change id in the URL path, so your own rules in Jentic One can pin an agent to reading one worker's data, and you choose which operations it may call so writes like job changes, contact updates, or time-off requests are excluded 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, and the same credential serves all four Workday services.
- **Discovery method:** Agents search the Jentic directory by intent such as 'initiate a job change', 'update a worker's home address', 'read a worker's goals', or 'submit a time-off request', and Jentic returns the matching Workday operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **BambooHR** — HR platform combining employee records, time-off, and onboarding as an alternative when an organization does not run Workday
- **HiBob** — Mid-market HRIS covering time-off tracking, employee profiles, and lifecycle management
- **Personio** — European HR platform covering absence, attendance, payroll, and recruiting
- **SAP SuccessFactors** — Enterprise HCM suite covering staffing, performance, and employee data as a direct alternative to Workday

## FAQ

### Which Workday APIs are covered here and what do they do?

Four tenant-scoped REST APIs: Staffing for jobs, job changes, organization assignments, and worker skill items; Person for worker personal, name, and contact information; Performance Enablement for feedback badges, feedback events, and worker goals; and Workday Absence Management for time-off balances, leaves of absence, and time-off requests.

### Does one credential work across all four Workday APIs?

Yes. All four use the same OAuth 2.0 model against your tenant-specific authorization host, so a single Workday OAuth client authorizes Staffing, Person, Performance Enablement, and Absence Management for that tenant.

### Do these APIs share the same tenant host?

Each API is reached through your Workday tenant hostname followed by a service-specific path and version, such as staffing/v6, person/v4, performanceEnablement/v5, or absenceManagement/v2. The tenant host is the same across services; only the path and version differ.

### Why is Workday Absence Management marked jentic-generated while the others are vendor-official?

Workday does not publish an OpenAPI specification for Absence Management, so Jentic generates and maintains one, validated against the live API. The Staffing, Person, and Performance Enablement specs come from Workday itself.

### Can agents write data back to Workday or only read it?

Both. Read operations cover balances, personal information, feedback, and goals, while write operations include job changes, organization assignment changes, contact information changes, skill items, and time-off requests. You choose which operations an agent may call.

### What can an agent build by combining these APIs?

Because they share one worker model and one tenant, an agent can chain them into workflows such as processing a job change in Staffing and then updating contact details in Person, or checking absence eligibility before filing a time-off request.
