> 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

# TSP API 101 Overview

The Docusign Trust Service Providers (TSP) API enables signature providers to integrate with the Docusign signing experience. TSP customers can now benefit from the Docusign platform as well as the TSP trusted signing technology.

![TSP API flow](/_fern-files/_img/243700b5622b1ea3f08e82a3b5a222ad3129a4bc748250c518bc0f9b85e4ebb6.webp)

## How does the TSP API work?

The TSP API connects the Docusign Digital Transaction Management (DTM) platform with a Trust Service Provider (TSP) signing solution. While signers access documents through Docusign, the TSP is performing the signature.

When a signer requests the signature of a document, Docusign redirects them to the TSP. The Trust Service Provider uses the TSP API to get signers' information and retrieve the hash of the documents to sign. They also run their flow to capture the consent of the signer to use their private signing key. Next, the Trust Service Provider signs the hash and returns the signed attributes in a Cryptographic Message Syntax (CMS). Docusign embeds the resulting CMS in the document as a
[PAdES](https://en.wikipedia.org/wiki/PAdES) signature and delivers it to signers and senders through the DTM platform.

#### [Get started](/docs/tsp-api/tsp101/get-started)

learn about how to build your integration with Docusign

#### [Authentication](/docs/tsp-api/tsp101/tsp-authentication)

Learn about how to authenticate to use the TSP API

#### [Design standards](/docs/tsp-api/tsp101/design-standards-overview)

Learn about Design standards for building Docusign integrations

## Docs

- [Trust Service Provider Concepts](https://developers.docusign.com/docs/tsp-api/tsp101/concepts.md)
- [Getting started with your TSP integration](https://developers.docusign.com/docs/tsp-api/tsp101/get-started.md)
- [TSP API Flow](https://developers.docusign.com/docs/tsp-api/tsp101/api-flow.md)
- [Long term validation of PDF signatures](https://developers.docusign.com/docs/tsp-api/tsp101/long-term-signature-validation.md)
- [CMS service API](https://developers.docusign.com/docs/tsp-api/tsp101/cms-service-api.md)
- [Authentication](https://developers.docusign.com/docs/tsp-api/tsp101/tsp-authentication.md): The TSP Partner program enables Trust Service Providers to integrate their solution directly into the Docusign eSignature experience.
- [Design Standards Overview](https://developers.docusign.com/docs/tsp-api/tsp101/design-standards-overview.md)
- [Design Standards Requirements](https://developers.docusign.com/docs/tsp-api/tsp101/design-standards-requirements.md)