---
title: "SOAP vs RaaS Basic Auth vs OAuth: which Workday…"
description: "Pick SOAP username@tenant, RaaS Basic Auth, or OAuth Bearer from what you are calling and where the call runs."
url: https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication
---

# SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?

API Gateway SOAP and Extend calls use OAuth Bearer. Classic SOAP web services still expect username@tenant when Workday returns Customer id was not specified. RaaS RSS and Basic Auth credentials use a Workday username and password. Match the credential to the endpoint, not to habit.

-   **Checked** against Workday on November 17
-   Applies to **Workday Web Services, RaaS, API Gateway**
-   5 min read
-   Published November 17
-   By Kiweely

Workday does not have one authentication method for every call. The credential you need depends on the surface you hit: the API Gateway SOAP path, a classic Workday Web Services SOAP endpoint, a Reports-as-a-Service URL, or an orchestration credential. Mixing those patterns is what produces `invalid username or password` and `Customer id was not specified`.

## Decision tree

| You are calling | Credential shape | Where Workday documents it |
| --- | --- | --- |
| SOAP through `https://api.workday.com/soap/{version}/{serviceName}` | OAuth 2.0 access token as `Authorization: Bearer {access-token}` | Call Workday SOAP APIs Using the API Gateway |
| Extend or Integration app SOAP through the API Gateway | Register an API client, then use an OAuth flow for the access token | SOAP API Authentication and Security |
| Integration app default SOAP credential | Access Token From Initiating User (the ISU on the integration system, or the launcher if none is set) | SOAP API Authentication and Security |
| Classic Workday Web Services SOAP with a username and password | Username must include the tenant: `ISU_benefits@my_tenant` | Workday Web Services Error Messages |
| RaaS RSS feed | HTTP Basic Auth with a Workday username and password | Concept: Reports as RSS Feeds |
| Orchestration outbound call that needs Basic Auth, OAuth, API Key, or ISU | Credential type on the orchestration Credentials tab | Create Orchestration Credentials |

Start from the URL and the product surface, not from “SOAP equals Basic Auth.”

## SOAP through the API Gateway

For orchestrations and external apps that authorize with the API Gateway, Workday’s documented SOAP path is:

```
POST https://api.workday.com/soap/{version}/{serviceName}
Content-Type: text/xml
Authorization: Bearer {access-token}
```

The body is the SOAP envelope. Workday’s sample uses `Human_Resources` and `Get_Workers_Request`. You get `{version}` and `{serviceName}` from the SOAP API Explorer. Presentation components cannot call SOAP APIs directly; a page launches an orchestration that makes the call.

Extend apps that call SOAP through the gateway register an API client on the Developer Site and choose an OAuth flow for the access token. Integration apps usually keep the default Access Token From Initiating User setting. That token is the integration system user when one is assigned, otherwise the user who launched the integration.

## Classic SOAP username and password

Older Workday Web Services clients still authenticate with a username and password on the SOAP request. Workday’s fault reference is explicit about the username format:

-   Fault `Customer id was not specified`: append the tenant name to the account. Example from Workday: if the account is `ISU_benefits` and the tenant is `my_tenant`, use `ISU_benefits@my_tenant`.
-   Fault `invalid username or password`: the password is wrong, or the username is missing the `@tenant` suffix.

Do not invent a gateway Bearer token for a classic WWS client that still expects username and password, and do not send a bare ISU name to a classic endpoint that requires `@tenant`.

## RaaS and Basic Auth

Reports-as-a-Service exposes advanced and search reports as web service URLs. The developer RaaS concept uses the namespace form `https://api.workday.com/raas/{user}/{report_name}` so you do not rewrite the host when the app moves tenants. Output options include CSV, JSON, RSS, Simple XML, and Workday XML.

For RSS, Workday says the feed reader must permit SSL/HTTPS or HTTP basic authentication. When the reader prompts for sign-in, you use a Workday username and password. Orchestration Builder also offers a Basic Auth credential type with username and password for outbound API requests.

RaaS still inherits Workday domain security. Integration App Security says custom reports invoked as RaaS endpoints are covered by the same configurable security model as REST, SOAP, and WQL. A 403 from a RaaS endpoint is a domain grant problem, not a wrong auth scheme.

## OAuth when the subject is a system user

Client Credentials and other OAuth2 flows return an access token. For service-to-service calls through the gateway, that token is what you put on the SOAP or REST `Authorization` header. Studio integrations should use their own API client and Client Credentials rather than an Extend simplified-ISU API client; Workday says that explicitly under Concept: ISU Authentication.

For interactive or user-scoped work, prefer the initiating user’s access token. Workday recommends Access Token From Initiating User for integration apps unless you deliberately need a different ISU than the one that launches the integration.

## Failure modes

| Symptom | Likely cause | Fix from Workday docs |
| --- | --- | --- |
| `Customer id was not specified` | Classic SOAP username missing `@tenant` | Use `account@tenant` |
| `invalid username or password` | Wrong password, or username without tenant | Correct password; append tenant |
| Gateway SOAP rejects the call | Missing Bearer token or wrong Content-Type | Send `Authorization: Bearer` and `text/xml` |
| RaaS 403 | Domain policy, not auth scheme | Grant View/Get for the report’s domains on the ISU or user group |
| Page cannot call SOAP | PMD cannot call SOAP directly | Launch an orchestration |

## Frequently asked questions

### Is RaaS the same as SOAP authentication?

No. RaaS is a report web service URL with formats such as JSON or CSV. SOAP is an XML envelope against a service such as Human Resources. RSS RaaS uses HTTP basic authentication with a Workday username and password. API Gateway SOAP uses an OAuth Bearer token.

### Should every new SOAP client use username@tenant?

Only for classic Workday Web Services username/password clients. New Extend and gateway callers use OAuth Bearer against `api.workday.com/soap/...`.

### Which orchestration credential should I pick?

Orchestration Builder supports API Key, Basic Auth, OAuth, and ISU. Match the type to the endpoint. For Production OAuth, Workday recommends Cred Store Reference, and recommends refreshing credentials at least a week before expiry so old and new versions overlap.

### Does ISU membership replace domain grants?

No. The ISU still needs Get/Put or View/Modify on the domains that secure the operation. Authentication proves who is calling. Domain security decides what they can read or write.

## Sources checked

-   [Call Workday SOAP APIs Using the API Gateway](https://developer.workday.com/documentation/ouv1543606422515/CallWorkdaySOAPAPIsUsingtheAPIGateway)
-   [SOAP API Authentication and Security](https://developer.workday.com/documentation/GUID-4c354bdb-06cd-461d-a632-ea8303beaedb-enHYPHENus/SOAPAPIAuthenticationandSecurity)
-   [Reference: Workday Web Services Error Messages](https://developer.workday.com/documentation/hug1399941147933/ReferenceWorkdayWebServicesErrorMessages)
-   [Concept: Reports-as-a-Service (RaaS)](https://developer.workday.com/documentation/hto1529968349582/ConceptReportsasaServiceRaaS)
-   [Concept: Reports as RSS Feeds](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370797814879.html)
-   [Create Orchestration Credentials](https://developer.workday.com/documentation/uwh1613475703138/CreateOrchestrationCredentials)
-   [Concept: Integration App Security](https://developer.workday.com/documentation/GUID-3586727d-613d-4d19-a27b-7e51c70c9ca8/ConceptIntegrationAppSecurity)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How do I set an Integration System Security Group for an Integration System User? An Integration System Security Group is the security group built for an ISU. Create constrained or unconstrained ISSG, add the ISU as the only member type allowed, assign domain and business process permissions, and activate pending security policy changes before you run the integration.](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [### How do I secure Workday RaaS access for an internal LLM or AI agent? Split Integration System Users by data area, select Do Not Allow UI Sessions, grant only the report domains each agent needs, and prefer the initiating user’s access token when a person is in the loop. RaaS still obeys domain security.](https://kiweely.com/guides/workday-raas-for-ai-agents-security)
-   [### Should I use RaaS, WQL or the REST API to extract data from Workday? Use RaaS for a saved report’s output, WQL for a filtered, grouped or paged extract of up to 1 million rows, and REST for small, low-latency reads of one resource. Limits and sources are in the table.](https://kiweely.com/guides/workday-raas-wql-rest)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [Why does Object Transporter block single-instance migration from Production?](https://kiweely.com/guides/workday-ox-production-single-instance-limits)
-   [EIB spreadsheet mapping when an AI assistant drafts the load](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [Custom reports and RaaS when an AI assistant is helping you build them](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)
-   [What AI tools can a Workday consultant use to build reports, calculated fields and EIB loads faster?](https://kiweely.com/guides/ai-tools-for-workday-reports-calculated-fields-eib)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)
-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)
-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
