---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Workday API]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Concept: Workday Web Services
layout: subsection
---

Workday Web Services (WWS) provide a programmatic public API for our On-Demand Workday Business Management Services. Web services are one of the central components of the Workday architecture and provide the core enablement tool to integrate with Workday.

WWS use industry-standards. These standards encompass WSDL, SOAP, REST, and the WS-* standards. In addition, we version WWS to ensure stability and backwards compatibility. Workday protects your investment in a specific version of our WWS as the business services of Workday evolve.

## <a id="section_N10028_N1001A_N10001"></a>Web Service Versioning

Workday provides a new version of the WWS API with each release and regular updates between releases. Example: Workday provided a v15 WWS API with Workday 15. Each update of the WWS API adds support for the new features introduced with the corresponding update of Workday.

You don't have to adopt the latest version of the WWS API. The WWS API is backward compatible. Example: A client application written to work with v14 of the WWS API will continue to work when v15 of the WWS API is available.

<b>Note:</b> Workday doesn’t guarantee that an application written against 1 API version will always work after updates. Certain object model changes and data representations require enhancements to the API.

Workday recommends using the most recent version of the WWS APIs for optimum performance and stability. Workday updates prior versions of the WWS APIs to maintain backward compatibility for all noncurrent versions of the WWS APIs that haven’t reached an end-of-life status. Workday doesn't generally enhance prior versions of WWS APIs.

We announce new WWS versions on Workday Developer Network. For supported WWS versions, see Workday Web Services (WWS) API Support Policy. For API documentation, see [SOAP Operation Directory](https://community.workday.com/sites/default/files/file-hosting/productionapi/index.html) or [SOAP API Explorer on the Developer Site](https://developer.workday.com/soap-api-explorer).

Workday can make backward compatible changes to an existing WWS version. Workday will make changes that aren't backward compatible in a new WWS version (Workday can change a Preview version).

Preview tenants provide one or more preview versions of the WWS API. The behavior of an operation or the WSDL for a service can change while a WWS version is in preview. Example: WWS versions v23.2 and v24.0 are available in Preview tenants while version v23.1 is the current version available in Production, Implementation, and Sandbox tenants.

## <a id="section_N10041_N1001A_N10001"></a>Unversioned Web Service Requests

Workday strongly discourages the use of unversioned web service requests, and their use is only for backward compatibility.

Workday interprets a versionless request as version 15 of the WWS API. Version 15 will continue to be the web service version applied to unversioned requests until version 15 reaches its End Of Life. However, the v15 WWS API might not support features introduced in subsequent Workday updates.

After version 15 reaches End of Life, Workday uses the earliest available version.

## <a id="section_N1004E_N1001A_N10001"></a>Deprecation and Retirement of Web Services

Workday provides communication through the WWS API Documentation when we no longer update an operation. Deprecated operations will continue to work until the operation reaches End-of-Life status.

Workday gives End of Life notice at least 18 months before an API version or operation ends. We provide notice through the Workday Developer Network. Workday will also directly notify customers using API versions or operations planned for removal.

## <a id="section_ut4_qzx_cjb"></a>Using a Single WSDL File for Multiple Web Services

You can combine Workday Web Services into a single WSDL or XML Schema (XSD) file. To combine the services, use the + character in between the services in your endpoint.

Example:

```
https://{endpoint}/ccx/service/{tenant}/Staffing+Human_Resources+Recruiting?wsdl
```

Alternatively, you can use the

```
?xsd
```

suffix to retrieve the XML Schema for multiple services.

Workday always returns the latest version of our WWS when combining services and schema. Workday interprets a versionless request for the WSDL of a single service or XML Schema as v15. If v15 of the WWS API isn't available, Workday uses the first version after v15.

## <a id="section_1"></a>Fully Qualified Domain Names in WSDL Files

If you use fully qualified domain names (FQDNs) that include your tenant name, the <b>soapbind:address</b> and <b>httpbind:address</b> locations in your WSDL support these FQDNs.

### Related Information

[Community: Workday Integrations](https://community-content.workday.com/en-us/collections/all-products/platform-and-product-extensions/integrations.html)

[Community: Constrained Security Support by Selected Operations](https://community-content.workday.com/content/workday-community/en-us/reference/products/platform-and-product-extensions/integrations/constrained-security-support-by-selected-operations.html)

[Workday Web Services (WWS) API Support Policy](https://community-content.workday.com/en-us/reference/products/platform-and-product-extensions/integrations/workday-web-services-wws-api-support-policy.html)

[Reference: Integrations and Web Service Limits](/wcp_docs/dan1370797408285.html)

