Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Workday / person
person logo

Workday person

Browse all Workday APIs
46
AI ReadinessFoundational (D)46/100
See full scorecard
Official 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.

Jentic One on GithubView OpenAPI Document

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" | sh
2

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 instance

Jentic 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.

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

P

person

- Foundational (D)
46/100
70
Foundational Compliance
69
Developer Experience & Jentic Compatibility
25
AI-Readiness & Agent Experience
81
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
70

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4
80%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

69

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
13%

Example Density

How richly the API is illustrated with examples.

93%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

25

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
66%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

33%

Summary Coverage

Coverage of summaries across operations/tags/info.

81

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1
81%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

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

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab 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

Start building with person API

Explore with Jentic One
View OpenAPI Document