Workday person
Browse all Workday APIsOfficial vendor OpenAPI document · agent-readyDeveloper ToolsSource Controloauth2112 EndpointsREST
For Agents
Programmatically validates phone number data to ensure it is valid for workday., retrieves a collection of personal information.. Covers 112 operations with oauth2 authentication.
Use for: I need to validates phone number data to ensure it is valid for workday., I want to retrieves a collection of personal information., Search for retrieves a home address., Find all retrieves information about a country.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
The Person REST APIs enable you to access information about the worker person, including country-specific configuration information about name components. The API exposes 112 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the person to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the person, 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%2Fperson" | 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%2Fperson" | 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 person API.
Validates phone number data to ensure it is valid for Workday.
Retrieves a collection of personal information.
HomeContactInformationChanges_createWebAddress
Retrieve all existing web addresses staged for update by the parent business pro
Monitor person operational status and events
Use Cases
Patterns agents use person API for, with concrete tasks.
★ Developer Tools Operations
Use the person to perform developer tools operations programmatically. The API provides 112 endpoints covering core functionality including validates phone number data to ensure it is valid for workday., retrieves a collection of personal information., retrieves a home address..
Call POST /phoneValidation to validates phone number data to ensure it is valid for workday.
Automated people Management
Automate people operations by combining multiple person endpoints. Agents can retrieves a collection of personal information. and then retrieves a home address. in a single workflow.
Call GET /people/{ID}/personalInformation to retrieves a collection of personal information., then verify the result
AI Agent Integration via Jentic
AI agents discover and call person 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 'validates phone number data to ensure it is valid for workday.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
112 endpoints — the person rest apis enable you to access information about the worker person, including country-specific configuration information about name components.
METHOD
PATH
DESCRIPTION
POST
/phoneValidation
Validates phone number data to ensure it is valid for Workday.
GET
/people/{ID}/personalInformation
Retrieves a collection of personal information.
GET
/people/{ID}/homeAddresses/{subresourceID}
Retrieves a home address.
GET
/countries/{ID}
Retrieves information about a country.
POST
/homeContactInformationChanges/{ID}/webAddresses
HomeContactInformationChanges_createWebAddress
GET
/homeContactInformationChanges/{ID}/webAddresses
Retrieve all existing web addresses staged for update by the parent business pro
GET
/people/{ID}/additionalNames/{subresourceID}
Retrieves an additional name.
GET
/workContactInformationChanges/{ID}/phoneNumbers/{subresourceID}
A phone number as it exists staged for update by the parent business process.
POST
/phoneValidation
Validates phone number data to ensure it is valid for Workday.
GET
/people/{ID}/personalInformation
Retrieves a collection of personal information.
GET
/people/{ID}/homeAddresses/{subresourceID}
Retrieves a home address.
GET
/countries/{ID}
Retrieves information about a country.
POST
/homeContactInformationChanges/{ID}/webAddresses
HomeContactInformationChanges_createWebAddress
GET
/homeContactInformationChanges/{ID}/webAddresses
Retrieve all existing web addresses staged for update by the parent business pro
GET
/people/{ID}/additionalNames/{subresourceID}
Retrieves an additional name.
GET
/workContactInformationChanges/{ID}/phoneNumbers/{subresourceID}
A phone number as it exists staged for update by the parent business process.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Workday person API by hand means running its OAuth2 flow against a tenant-specific authorization host, building your tenant hostname into the person/v4 base, and threading person and subresource ids through every path yourself. Through Jentic you install once, import the Workday person API from the API Directory, store the OAuth client once, and your agent calls it.
Permission scoping
The person API puts the person and subresource ids in the URL path (/people/{ID}/homeAddresses/{subresourceID}), so a rule can pin your agent to reading one person's contact and personal information. You choose the operations it may call, so writes like posting a contact-information change are not included unless you add them.
Credential isolation
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.
Intent-based discovery
Agents search Jentic by intent such as 'validate a phone number' or 'read a person's home address', and Jentic returns the matching person 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.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using person API through Jentic.
What authentication does the person use?
The person 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 validates phone number data to ensure it is valid for workday. with the person?
Yes. Use the POST /phoneValidation endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the person?
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 validates phone number data to ensure it is valid for workday. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validates phone number data to ensure it is valid for workday.'. Jentic returns the matching person operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the person have?
The person exposes 112 endpoints covering people, workcontactinformationchanges, homecontactinformationchanges operations.
Can I limit what my agent is allowed to do with the Workday Person API?
Yes. Because you run Jentic One yourself, your own rules decide which Person operations and credentials the agent can use. Since person and subresource ids sit in the URL path, such as GET /people/{ID}/homeAddresses/{subresourceID}, you can pin the agent to reading one person's contact and personal information. Write operations like POST /homeContactInformationChanges/{ID}/webAddresses stay out of reach unless you explicitly add them to the allowed set.
GET STARTED