Workday staffing
Browse all Workday APIsOfficial vendor OpenAPI document · agent-readySocial MediaSocial Managementoauth2144 EndpointsREST
For Agents
Programmatically returns the location information for the specified job change id., initiates an organization assignment change for a specific worker.. Covers 144 operations with oauth2 authentication.
Use for: I need to returns the location information for the specified job change id., I want to initiates an organization assignment change for a specific worker., Search for workers_createskillitem, Find all workers_getskillitems
Not supported: Does not handle payments, communications, or crm - use for social media only.
The Staffing REST APIs enable you to get and manage staffing information, such as jobs, job families, job profiles, supervisory organizations, worker check-ins, and job changes. The Staffing service also includes the /workers resource to access staffing information for non-terminated workers. Related Information: - Administrator Guide: Setup Considerations: Job Changes. The API exposes 144 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the staffing to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the staffing, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fworkday.com%2Fstaffing" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fworkday.com%2Fstaffing" | 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 staffing API.
Returns the location information for the specified job change ID.
Initiates an organization assignment change for a specific worker.
Workers_createSkillItem
Workers_getSkillItems
Retrieves the start details for the specified job change ID.
Partially updates the startDetails options for the specified change job ID.
Use Cases
Patterns agents use staffing API for, with concrete tasks.
★ Social Media Operations
Use the staffing to perform social media operations programmatically. The API provides 144 endpoints covering core functionality including returns the location information for the specified job change id., initiates an organization assignment change for a specific worker., workers_createskillitem.
Call GET /jobChanges/{ID}/location to returns the location information for the specified job change id.
Automated Prompt Values Management
Automate prompt values operations by combining multiple staffing endpoints. Agents can initiates an organization assignment change for a specific worker. and then workers_createskillitem in a single workflow.
Call POST /workers/{ID}/organizationAssignmentChanges to initiates an organization assignment change for a specific worker., then verify the result
AI Agent Integration via Jentic
AI agents discover and call staffing endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'returns the location information for the specified job change id.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
144 endpoints — the staffing rest apis enable you to get and manage staffing information, such as jobs, job families, job profiles, supervisory organizations, worker check-ins, and job changes.
METHOD
PATH
DESCRIPTION
GET
/jobChanges/{ID}/location
Returns the location information for the specified job change ID.
POST
/workers/{ID}/organizationAssignmentChanges
Initiates an organization assignment change for a specific worker.
POST
/workers/{ID}/skillItems
Workers_createSkillItem
GET
/workers/{ID}/skillItems
Workers_getSkillItems
GET
/jobChanges/{ID}/startDetails/{subresourceID}
Retrieves the start details for the specified job change ID.
PATCH
/jobChanges/{ID}/startDetails/{subresourceID}
Partially updates the startDetails options for the specified change job ID.
GET
/organizationAssignmentChanges/{ID}/region
Retrieves a region for the specified organization assignment change ID.
POST
/workers/{ID}/workContactInformationChanges
Workers_createWorkContactInformationChanges
GET
/jobChanges/{ID}/location
Returns the location information for the specified job change ID.
POST
/workers/{ID}/organizationAssignmentChanges
Initiates an organization assignment change for a specific worker.
POST
/workers/{ID}/skillItems
Workers_createSkillItem
GET
/workers/{ID}/skillItems
Workers_getSkillItems
GET
/jobChanges/{ID}/startDetails/{subresourceID}
Retrieves the start details for the specified job change ID.
PATCH
/jobChanges/{ID}/startDetails/{subresourceID}
Partially updates the startDetails options for the specified change job ID.
GET
/organizationAssignmentChanges/{ID}/region
Retrieves a region for the specified organization assignment change ID.
POST
/workers/{ID}/workContactInformationChanges
Workers_createWorkContactInformationChanges
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Workday Staffing by hand means implementing its OAuth2 flow, resolving the per-tenant host that stands in for <tenantHostname>, and refreshing tokens across 144 operations yourself. Through Jentic you install once, import Workday Staffing from the API Directory, store the OAuth2 credential once, and your agent calls it.
Permission scoping
Workday Staffing puts the worker or job-change id in the URL path (/workers/{ID}/skillItems, /jobChanges/{ID}/location), so a rule can pin your agent to one worker or job change. You choose the operations it may call, so write actions like posting organization assignment changes or contact-information changes are not included unless you add them.
Credential isolation
Your Workday Staffing OAuth2 credential 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.
Intent-based discovery
Agents search Jentic by intent such as 'get the location for a job change' or 'add skill items to a worker', and Jentic returns the matching Workday Staffing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using staffing API through Jentic.
What authentication does the staffing use?
The staffing uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I returns the location information for the specified job change id. with the staffing?
Yes. Use the GET /jobChanges/{ID}/location endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the staffing?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I returns the location information for the specified job change id. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns the location information for the specified job change id.'. Jentic returns the matching staffing operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the staffing have?
The staffing exposes 144 endpoints covering prompt values, jobchanges, workers operations.
Can I limit what my agent is allowed to do with the Workday Staffing API?
Yes. Because Jentic One is self-hosted, your own rules decide which Workday Staffing operations and which OAuth2 credential the agent may use, and you can restrict it to a specific set of endpoints. Since the worker or job-change ID sits in the URL path, such as /workers/{ID}/skillItems and /jobChanges/{ID}/location, a rule can pin the agent to a single worker or job change. Read-only calls stay separate from write actions like posting organization assignment changes or contact-information changes, so those run only if you explicitly allow them.
GET STARTED