Every standard Workday HCM and Financials tenant already includes the authentication and data APIs needed to answer employee questions live inside Claude, ChatGPT, and Gemini—without signing a Workday Flex Credits policy, activating Agent System of Record, or licensing Workday Extend. By pairing Workday’s built-in Register API Client task (Authorization Code Grant with PKCE) with tenanted REST, WQL, SOAP, and Reports-as-a-Service (RaaS) endpoints, IT teams can roll out governed Workday AI on the core subscription they already pay for.
Why Teams Assume Workday AI Requires Extra SKUs
When HRIS leaders search Workday’s documentation for “Connect an External Agent with Workday MCP” or “Sana Workspace,” they immediately encounter a stack of commercial and contractual prerequisites:
- Transitioning from a Main Service Agreement (MSA) to the Universal Main Subscription Agreement (UMSA), or opting into Innovation Services and AI data contributions.
- Signing the Workday Flex Credits and Platform Entitlement Policy once complimentary credits run out, with usage metered in blocks on the Platform Consumption Console.
- Setting up Agent System of Record (ASOR), Agent Management Hub, and Agent System User (ASU) credentials.
- Meeting the explicit note in Workday’s external MCP setup guide stating that Workday’s native MCP server functionality is restricted to Extend Professionals.
Those requirements apply specifically to Workday’s own Agent Gateway (us.agent.workday.com and regional equivalents) and Workday-built agents. They do not apply to Workday’s core tenanted web services, which thousands of enterprises have used in production for over a decade.
What Already Ships Inside Every Standard Workday Tenant
Without buying a single add-on module, a core Workday HCM or Financial Management tenant provides five native building blocks:
| Core Workday Capability | Task or Endpoint Surface | What It Delivers for Live AI Assistants |
|---|---|---|
| Core Workday CapabilityUser-delegated OAuth 2.0 | Task or Endpoint SurfaceRegister API Client (Authorization Code Grant, PKCE) |
What It Delivers for Live AI AssistantsAuthenticates each employee via Workday SSO/MFA and scopes API calls to that worker’s own security groups |
| Core Workday CapabilityWorkday REST APIs | Task or Endpoint Surface/ccx/api/{service}/{version}/{tenant} |
What It Delivers for Live AI AssistantsClean JSON reads and business-process actions across common, staffing, absenceManagement, timeTracking, expense, and more |
| Core Workday CapabilityWorkday Query Language (WQL) | Task or Endpoint Surface/ccx/api/wql/v1/{tenant}/data & /dataSources |
What It Delivers for Live AI AssistantsSQL-like ad-hoc queries, GROUP BY aggregations, and live schema discovery across 1,400+ Workday data sources |
| Core Workday CapabilityReports as a Service (RaaS) | Task or Endpoint SurfaceEdit Custom Report → Enable As Web Service |
What It Delivers for Live AI AssistantsExposes your existing custom reports—including complex calculated fields—as parameterized JSON or XML endpoints |
| Core Workday CapabilityWorkday Web Services (SOAP) | Task or Endpoint Surface/ccx/service/{tenant}/{service}/v45.1 |
What It Delivers for Live AI AssistantsDeep functional reads across Human_Resources, Compensation, Recruiting, Payroll, and Financial_Management |
Because all five surfaces honor Workday’s configurable security framework natively, a user-delegated token issued through Register API Client never elevates an employee’s privileges.
How User-Delegated OAuth Works Without Agent System of Record
In Workday’s System functional area (secured by the Security Administration domain), Workday provides two distinct OAuth registration tasks that solve completely different problems:
- Register API Client for Integrations: Built for headless background jobs, Studio integrations, and middleware. It binds to a single Integration System User (
ISU) with non-expiring credentials and static tenant-wide permissions. Never use this for employee AI chat. - Register API Client: Built for interactive user applications. When configured with
Client Grant Type: Authorization Code Grant,Access Token Type: Bearer, and PKCE verification, Workday prompts each employee to sign in on Workday’s own authentication screen and issues a token tied strictly to that individual’s Workday account.
GET https://{workday-host}/{tenant}/authorize?response_type=code&client_id={client_id}&redirect_uri={https_callback}&code_challenge={s256_hash}&code_challenge_method=S256 HTTP/1.1On Register API Client, the administrator selects the Scope (Functional Areas) ceiling—for example, Staffing, Absence, Time Tracking, Compensation, and System (for WQL and custom report execution). Even if Compensation is listed in the client’s functional scope, an ordinary employee querying through that client still sees only the fields permitted by their Employee As Self domain policies. Scope acts as an outer ceiling; the worker’s own security groups enforce row-level and field-level truth.
Combining REST, WQL, RaaS, and SOAP for Complete Tenant Coverage
Relying on a single Workday API surface leaves blind spots. Combining all four core interfaces on a standard tenant gives AI assistants broader reach than preset self-service chatbots—again without Extend or Flex Credits:
- Use REST for standard self-service transactions: Checking time-off balances (
absenceManagement), viewing worker summaries (common), or looking up expense reports (expense). - Use Workday WQL for analytical and cross-object questions: Answering manager and HR Partner prompts like “Group active headcount in my supervisory hierarchy by location and job family” in one JSON round-trip using
SELECT ... GROUP BYwithLIMITandOFFSETpagination. - Use RaaS custom reports for tenant-specific calculated fields: If your HRIS team already spent months perfecting a
Lookup Related ValueorEvaluate Expressioncalculated field on an advanced report, enablingEnable As Web Serviceexposes that exact logic in?format=jsonwithout rewriting business rules in code. - Use SOAP reads where REST coverage stops: Querying specialized structures in
Human_Resources,Recruiting, orFinancial_Managementthat Workday has not yet mirrored into public REST resources.
Notice what Workday’s Platform Consumption Console documentation states explicitly about API requests: on tenants that have not signed the Flex Credits and Platform Entitlement Policy, API request counts appear on the dashboard strictly for informational purposes and do not consume Flex Credits.
Two Ways to Put Standard Workday APIs to Work: Chat and Custom Screens
Once you recognize that core Workday tenants already carry full user-delegated APIs, two practical employee experiences open up without buying Workday Extend or a Workday AI bundle:
- Inside Claude, ChatGPT, and Gemini (Kiweely Bridge, coming next): Bridge is a remote MCP connector that links any standard Workday tenant to Claude, ChatGPT, and Gemini across desktop, web, and mobile. An AI admin agent helps configure
Register API ClientFunctional Areas in Sandbox, sets in-memory field redaction rules, and tests role boundaries as real personas. Bridge is read-only by default, pauses enabled writes for an out-of-band browser approval card, stores zero Workday payloads, and is priced flat per company by employee count (from $499/mo up to 1,000 employees with unlimited calls, or free on a personal developer tenant; compare options on /bridge/compare). - Clean custom screens outside Workday (Kiweely Leaf, coming next): When frontline staff or occasional managers need a purpose-built web portal, Teams/Slack/DingTalk/Lark approval view, or a three-button phone app in the Kiweely Leaf mobile app rather than a chat prompt, Leaf’s AI agents build and host custom pass-through UIs on those exact same standard Workday OAuth, REST, WQL, and RaaS APIs—with zero HR data stored at rest and no Workday Extend subscription required. (And for teams that do license Workday Extend and want PMD/AMD apps inside Workday, Kiweely Vine builds and tests those today.)
Pre-Flight Checklist for Connecting a Standard Tenant
Before scheduling a procurement call for AI add-ons, verify what your current tenant already supports in Sandbox:
- Check domain access: Confirm your security administrator holds the
Security Administrationdomain in theSystemfunctional area to open Register API Client. - Test WQL availability: Verify your target user roles have domain permission to query
/api/wql/v1/{tenant}/dataSourcesand the underlying report data sources they already use in Workday UI reports. - Inventory reusable RaaS reports: Identify 5 to 10 existing advanced reports that answer frequent manager or finance questions and check whether
Enable As Web Serviceis selected. - Verify network policies: Review Maintain IP Ranges and Manage Authentication Policies so your security team knows whether your remote connector will use Kiweely Cloud, a dedicated static outbound IP, or a self-hosted VPC container.
Frequently asked questions
Does Workday charge Flex Credits for standard REST, WQL, SOAP, or RaaS API calls?
On a standard Workday tenant without signing the Flex Credits and Platform Entitlement Policy for Agent Gateway offers, standard tenanted REST, WQL, SOAP, and RaaS calls use your core tenant entitlement rather than consuming agent Flex Credit blocks.
Why does Workday's native MCP documentation say Extend Professionals only?
Workday's own Agent-Ready MCP Server routes through the Workday Agent Gateway and Agent System of Record (ASOR), which Workday gates behind UMSA / Innovation Services, Flex Credits, and Extend Professional access.
Can a standard Workday tenant enforce per-employee permissions over APIs without ASOR?
Yes. Registering an OAuth 2.0 client with the standard Register API Client task (Authorization Code Grant with PKCE) issues user-delegated tokens that enforce each signed-in worker's exact Workday security groups, domains, and constrained organizations.