Workday publishes three different doors, and teams keep collapsing them into “the API.”
Agent Gateway is the regional HTTPS front door. Third-party agents must send Workday API traffic through it, under an Agent System User (ASU), after the agent is registered in Agent System of Record (ASOR).
MCP on Workday’s setup page is how a registered external agent talks to Workday’s MCP server. Workday labels that page for Extend Professionals only.
A2A (Agent2Agent) is how an assistant that runs outside Workday, Workday’s example is Google Gemini Enterprise, discovers and calls Self-Service Agent for an authorized user.
Sana Enterprise is a fourth, product-specific path: administrators can add custom MCP connectors with OAuth. That is Sana’s connector list, not the Agent Gateway MCP setup page. This post stays with the admin-guide pages.
What Agent Gateway actually exposes
Fetched from the concept page (last updated 2026-08-21):
| Included | Not stated on that page |
|---|---|
| IncludedAll public REST operations | Not stated on that pageA numeric rate limit |
| IncludedWorkday Graph API | Not stated on that pageAd-hoc access without ASOR registration |
| IncludedWQL | Not stated on that pageA user-delegated employee login as the default security principal |
| IncludedRaaS | Not stated on that page |
| IncludedAgent Definition Registry API | Not stated on that page |
Calls use the regional host (us, eu, uk, ca, au, sg, in, or jp, each as https://<region>.agent.workday.com) and the header wd-agent-tenant-alias. SOAP goes to https://<region>.agent.workday.com/soap/{version}/{serviceName}. OAuth 2.0 authorization-code grant is the flow Workday tells you to use when the agent platform supports OAuth 2.0. Activation and deactivation in Workday can take up to a minute to appear on Agent Gateway and MCP gateway requests. Changing region resets Agent Management Hub analytics.
The authenticate topic adds: register with the agent registration API, keep client id, client secret, redirect URI for delegate agents, and the x509 public key for ambient agents, then exchange an authorization code at https://<region>.agent.workday.com/auth/oauth2/<tenant alias>/token.
Security is the ASU, not “whoever is logged into the browser.” ASOR still requires the human’s security groups on delegate skills, and tool APIs still enforce their own domain policies. Ambient skills run as the agent, without an interaction group.
MCP, as Workday documents it
Prerequisites on the MCP page: Agent System of Record, discover the agent-ready MCP tools, register the external agent, configure it, and configure security policies for its skills. UMSA customers get the feature without the MSA Innovation Services opt-in. MSA customers enable it through Innovation Services. UMSA tenants do not show those Innovation Services tasks.
The connection check Workday publishes is a JSON-RPC tools/list POST to https://us.agent.workday.com/mcp with a bearer token. A tools list in the response means the registered tools are visible. Platforms Workday names as MCP clients of that same endpoint: Google Agentspace, Amazon Bedrock AgentCore, Microsoft Copilot Studio, and others. The page also shows a Cursor MCP entry whose URL shape is https://{agentGatewayRegionEndpoint}/{tenantName}/mcp.
Token lifetimes on that page: access tokens expire after 4 hours. Refresh tokens last 30 days. The authorize example is GET https://us.agent.workday.com/auth/authorize/ with client id, redirect URI, and response_type=code, then a token POST. Those are ASU tokens for the external agent. They are not a per-employee Workday session.
Workday does not say this MCP server includes every SOAP operation, every custom report, or arbitrary WQL you could run as yourself. It says you confirm the tools you registered. Discover the tool list in the tenant before you tell a pilot that “MCP means all of Workday.”
A2A, as Workday documents it
The A2A page (last updated 2026-09-18) is narrower than MCP. You register a third-party client in ASOR so it can call Self-Service Agent. The registration payload Workday shows includes provider Self-Built, a platform id, and one skill: ssa-agent-as-a-tool, execution mode Delegate, resource id 6bfadd7c014610000dffae8d77c00000.
You then:
- Create or reuse an integration system user and Register API Client for Integrations, functional area Agent System of Record, including Workday-owned scopes.
- Mint a refresh token for that ISU and exchange it for a bearer token at the gateway token endpoint.
GET https://{{agent-gateway-hostname}}/v1/a2a/{{tenant-alias}}/{{agent-wid}}/.well-known/agent-card.json.- Import that Agent Card into the external platform.
- On that platform, set client secret, enable PKCE, and point authorize and token URLs at
<region>.agent.workday.com. - Put end users in the Workday security groups from agent configuration, and assign the agent in the external platform.
Workday’s detailed click-path for Gemini Enterprise is a separate topic, Set Up Sana From Workday for Gemini Enterprise, which this page only names.
A2A here is “outside assistant calls Self-Service Agent.” It is not a general license to invoke Financial Audit Agent, Planning Agent, or a partner agent. If the skill id in your registration is not ssa-agent-as-a-tool, you are outside what this page demonstrates.
Which door to use
| Need | Documented path | Security principal | Watch-out |
|---|---|---|---|
| NeedPartner or external agent calls REST, Graph, WQL, or RaaS | Documented pathAgent Gateway | Security principalASU | Watch-outRegister in ASOR first. Header must carry the tenant alias. |
| NeedExternal agent platform that speaks MCP | Documented pathWorkday MCP server | Security principalASU access token, 4-hour access, 30-day refresh | Watch-outExtend Professionals. Only registered tools. |
| NeedGemini Enterprise or similar should answer as Self-Service Agent | Documented pathA2A Agent Card | Security principalISU bearer to fetch the card; end users still need skill security groups; PKCE on the client | Watch-outOne published skill: Self-Service Agent as a tool. |
| NeedEmployees in Sana Enterprise reach a long-tail system | Documented pathSana custom MCP connector | Security principalOAuth controlled by the Sana administrator | Watch-outSana Enterprise SKU, not Sana Core. |
A path that is not Agent Gateway
Kiweely Bridge is coming next. Its published setup is a user-delegated Workday API client (Authorization Code with PKCE), not an integration system user, and it does not require UMSA, ASOR, or Flex Credits. Employees call as themselves, so Workday’s own domain security applies. Pricing on the product page is a company band by employee count: $499, $1,499, or $3,999 per month through 20,000 employees, and a quote above that. That is a different product decision from Workday’s ASU gateway: per-user OAuth and no Workday AI agreement, versus a governed agent identity inside ASOR. Use Gateway, MCP, or A2A when the agent must be an ASOR citizen. Use a user-delegated connector when the worker should simply act as themselves in Claude, ChatGPT, or Gemini.
Frequently asked questions
Does MCP replace A2A?
No. MCP lists and calls tools on Workday’s MCP server for a registered external agent. A2A publishes an Agent Card so an external assistant can invoke Self-Service Agent. Gateway is the host both rely on.
Can any developer open the MCP endpoint?
The setup page says the functionality is for Extend Professionals, and the agent has to be registered and configured first. A bearer token without that registration is not what the page demonstrates.
Will Copilot Studio see custom reports automatically?
Workday says Copilot Studio can use the same OAuth credentials and endpoint, then tells you to follow that platform’s MCP steps. It also tells you to verify tools/list. Assume the list is the contract.
Sources checked
Agent Gateway, MCP connection, A2A connection, gateway authentication, and About Workday Agents, fetched 2026-11-16. Kiweely Bridge statements are from Kiweely’s published Bridge copy, and Bridge is coming next.