Workday APIs for AI Agents
Social MediaSocial ManagementSource ControlMixed ProvenanceOAuth 2.0Agent Ready
Workday API Catalog
4 APIs across 3 product groups. All share one credential.
Social Media2
staffingProgrammatically returns the location information for the specified job change id., initiates an organization assignment change for a specific worker..~144 endpointsperformanceEnablementProgrammatically retrieves a collection of active feedback badges., retrieves a single self-requested feedback event instance for the specified work.~23 endpoints
Which Workday API should I use?
| I want to... | Use | Why |
|---|---|---|
| Manage jobs, job changes, organization assignments, and worker skill items | 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 | 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 | performanceEnablement | 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 | Workday Absence Management | Workday Absence Management covers balances, eligible absence types, leaves of absence, valid time-off dates, and time-off requests across 14 operations |
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
FAQs
Specific to using Workday APIs through Jentic.
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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
