---
category: [Administration & Integrations, Administration & Integrations/Workday API, Platform and Product Extensions, Platform and Product Extensions/Integration]
keyword: [Extend, Integrate, REST API]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Concept: REST API External Integration Headers
layout: subsection
---

## <a id="external_integration_headers"></a>External Integration Headers

The external integration headers provide insight about web service transactions for analysis and troubleshooting. You can set these HTTP headers to values that identify the originating account, system, and transaction type of the web service request. Workday accepts these request headers and adds them to the Workday logs. The request headers help with filtering the logs to expedite troubleshooting with Customer Support.

<table><thead><tr><th>HTTP Header</th><th>Description</th><th>Header Value</th></tr></thead><tbody><tr><td><code>wd-external-request-id</code></td><td>Tracks web service requests.</td><td>A universally unique identifier (UUID). You can optionally use an alphanumeric string that clearly and uniquely identifies the request.</td></tr><tr><td><code>wd-external-application-id</code></td><td>Tracks external systems or applications that send the web service requests.</td><td>The name of the external integration, third-party tool, or software component that sends the web service request. Use a name that clearly identifies the initiating application.</td></tr><tr><td><code>wd-external-originator-id</code></td><td>Tracks originators that initiate the web service requests.</td><td>The user account or system account that initiated the web service request.</td></tr></tbody></table><br/>

Consider these guidelines when you set the HTTP header values:

-   Although Workday doesn't validate the header values, we strongly recommend that you use unique values to track the requests clearly. For API calls made by Workday partners, we recommend using the wd-external-application-id header. Workday might reject requests without this header.
-   Limit the length to 50 characters to enable efficient searching, debugging, and tracking in the logs. We truncate header values greater than 50 characters.
-   Don't include sensitive information.


We log all external integration headers you send with each web service request. If you don't send any of the external integration headers with a web service request, we don't log the request headers.

<a id="section_1"></a>
Example: You can use the external integration headers to measure performance impact with the Effective Changes REST API in the Global Payroll REST service.