> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Docusign Time Track header

The Docusign Time Track header is an optional line that can be added to your API request header to return processing times for your requests.

When the X-Docusign-TimeTrack header is included in the API request, Docusign returns the header in the response with the start-time and the end-time of the associated API request.

For example, when the Time Track header is included in the request:

```
X-Docusign-TimeTrack
```

The response includes the header and times in the response:

```
X-Docusign-TimeTrack: SOAP_Start,2016-01-05T22:30:52.2522730Z;SOAP_End,2016-01-05T22:30:52.3182730Z
```

Additionally you must add your own value on the request and that information is preserved in the response.

For example, you could add the time your application starts a process (such as MySendApp,) and then check the round-trip network time for an action.

**`Request header example`**

```javascript title="Request header example"
X-DocuSign-TimeTrack: MySendApp,2016-01-05T22:30:52.2522666Z
```

**`Response example`**

```javascript title="Response example"
X-DocuSign-TimeTrack: MySendApp,2016-01-05T22:30:52.2522666Z;SOAP_Start,2016-01-05T22:30:52.2522730Z;SOAP_End,2016-01-05T22:30:52.3182730Z
```