> 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

# Trust Records API 101

> Learn fundamental concepts of the tryst records API and get pointers to more information.

The Trust Records API enables Docusign customers to retrieve third-party Trust Service Provider (TSP) evidence data of the agreement participants.

Two categories of API calls can be made with the Trust Records API:

**List Evidence URLs**: The outcome of this API call is a list of URLs from which the TSP evidence artifacts can be downloaded. It should be noted that multiple artifacts may be generated for each recipient. The recipient id is to be obtained from the envelope.

**Download artifact files**: Once the list of artifacts has been obtained, they can be downloaded directly using the `file_url` field. With the file URL and context data, the partner evidence file can be downloaded completely for the recipient.

#### [Access tokens](/docs/trust-records-api/trustrecords101/access-tokens)

See how to use OAuth to request an access token and call the Trust Record API.