Workday Extend
Workday Extend is a platform that enables developers to build custom applications that integrate seamlessly with Workday. It provides APIs, development tools, and a runtime environment for creating tailored solutions that extend Workday's core functionality.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Workday Extend the way a machine reads it — 88 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Workday Extend scores 72.9/100 (exemplar), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Workday Extend
Each block below is one kind of artifact we hold for Workday Extend. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Workday Orchestrate Insights API
API for accessing orchestration execution data and monitoring information. Provides insights into orchestration performance, run history, and operational metrics for troubleshoo...
Workday Illuminate AI API
AI-powered APIs within Workday Illuminate that provide skills and sentiment analysis, document intelligence, natural language WQL queries, and machine learning forecasting capab...
Workday Extend App Configurations API
Operations for managing application configuration settings and environment-specific parameters.
Workday Extend App Deployments API
Operations for deploying and managing Extend application instances within a tenant.
Workday Extend App Versions API
Operations for managing application versions and release lifecycle.
Workday Extend Apps API
Operations for managing Extend applications including registration, deployment, and configuration.
Workday Extend Custom Object Definitions API
Operations for defining and managing custom object types including their schemas, attributes, and relationships to standard Workday objects.
Workday Extend Custom Object Fields API
Operations for managing the fields and attributes defined within custom object schemas.
Workday Extend Custom Object Instances API
Operations for creating, reading, updating, and deleting custom object data instances attached to Workday business objects.
Workday Extend Graph Query API
Operations for querying Workday business objects using the Graph API. Supports flexible field selection and relationship traversal.
Workday Extend Orchestration Executions API
Operations for triggering orchestration runs, monitoring execution status, and retrieving execution results.
Workday Extend Orchestration Steps API
Operations for managing individual steps within an orchestration flow, including connectors, transformations, and conditions.
Workday Extend Orchestration Triggers API
Operations for configuring orchestration triggers including event-based, scheduled, and API-triggered orchestrations.
Workday Extend Orchestrations API
Operations for managing orchestration definitions including creation, configuration, versioning, and lifecycle management.
Workday Extend Schema Introspection API
Operations for discovering available business objects, their fields, relationships, and query capabilities through the Graph API.
Workday Extend WQL Query API
Operations for executing Workday Query Language (WQL) queries against the Workday data model. WQL provides SQL-like syntax for complex data retrieval across business objects.
Scroll within the panel for all 16 ·
Postman Collections 4
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Workday Extend Workday Custom Objects API
OPEN COLLECTIONWorkday Extend Workday Graph API
OPEN COLLECTIONWorkday Extend Workday Orchestration API
OPEN COLLECTIONWorkday Extend REST API
OPEN COLLECTIONArazzo Workflows 12
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Workday Extend Update Application Configuration
Confirm an Extend app exists, read its current configuration, then replace the configuration values.
ARAZZOWorkday Extend Cancel a Running Orchestration Execution
Find the most recent running execution of an orchestration, cancel it, and confirm cancellation.
ARAZZOWorkday Extend Create and Activate Orchestration
Create an orchestration, attach a trigger, and activate it for execution.
ARAZZOWorkday Extend Define a Custom Object With Fields
Create a custom object definition, add a field to it, and list the resulting field schema.
ARAZZOWorkday Extend Discover Schema and Run a Graph Query
Find a queryable business object type, inspect its schema, then run a graph query against it.
ARAZZOWorkday Extend Inspect an Orchestration
Resolve an orchestration by search, then list its steps and triggers to build a full picture.
ARAZZOWorkday Extend Launch Orchestration and Poll Execution
Confirm an orchestration, launch an execution with inputs, and poll until it completes.
ARAZZOWorkday Extend Publish a New Application Version
Confirm an app, create a new version, and verify the version was recorded.
ARAZZOWorkday Extend Register and Deploy Application
Register an Extend app, publish a version, deploy it, and poll until the deployment settles.
ARAZZOWorkday Extend Safely Update an Orchestration
Deactivate an active orchestration, apply changes, and reactivate it.
ARAZZOWorkday Extend Upsert Worker Custom Object Data
Confirm a custom object definition, check whether a worker already has data, then create or update it.
ARAZZOWorkday Extend WQL Query Into a Worker Custom Object
Run a WQL query to retrieve worker data, then write the result into a worker's custom object.
ARAZZOScroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Workday Extend Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Workday Extend Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Workday Extend Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Workday Extend API Rules
SPECTRALWorkday Extend API Rules
SPECTRALJSON Schema 35
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Workday Extend Application
JSON SCHEMAAppConfiguration
JSON SCHEMAAppConfigurationUpdate
JSON SCHEMAAppCreate
JSON SCHEMAAppDeployment
JSON SCHEMAAppDeploymentCreate
JSON SCHEMAAppUpdate
JSON SCHEMAAppVersion
JSON SCHEMAAppVersionCreate
JSON SCHEMAWorkday Custom Object Definition
JSON SCHEMACustomObjectData
JSON SCHEMACustomObjectDefinition
JSON SCHEMACustomObjectDefinitionCreate
JSON SCHEMACustomObjectDefinitionUpdate
JSON SCHEMACustomObjectField
JSON SCHEMACustomObjectFieldCreate
JSON SCHEMACustomObjectInstance
JSON SCHEMAErrorResponse
JSON SCHEMAGraphQueryRequest
JSON SCHEMAGraphQueryResponse
JSON SCHEMAGraphSchema
JSON SCHEMAWorkday Orchestration
JSON SCHEMAOrchestrationCreate
JSON SCHEMAOrchestrationExecution
JSON SCHEMAOrchestrationLaunch
JSON SCHEMAOrchestrationStep
JSON SCHEMAOrchestrationTrigger
JSON SCHEMAOrchestrationTriggerCreate
JSON SCHEMAOrchestrationUpdate
JSON SCHEMAResourceReference
JSON SCHEMASchemaField
JSON SCHEMASchemaRelationship
JSON SCHEMASchemaType
JSON SCHEMAWqlQueryRequest
JSON SCHEMAWqlQueryResponse
JSON SCHEMAScroll within the panel for all 35 ·
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Workday Extend App Structure
JSON STRUCTUREWorkday Extend Orchestration Structure
JSON STRUCTUREWorkday Extend Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Workday Extend — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 15
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 15 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/workday-extend · machine-readable index on apis.io