> 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 Overview

> Learn how the Trust Records API centralizes access to all of Docusign's Trust artifacts for data collected about an agreement participant.

The Trust Records API gives developers a single, standardized endpoint to access third-party Trust Service Provider (TSP) evidence collected about an agreement participant. Use the API to programmatically retrieve partner evidence files like KYC files —so you can automate compliance workflows, support audits, and connect trust data to your business systems without building and maintaining bespoke API integrations for every individual third-party provider.

## Places to start

* [Trust Records API 101](/docs/trust-records-api/trustrecords101)
* [How-to guides](/docs/trust-records-api/how-to)
* [API Reference](/docs/trust-records-api/reference)

![trustrecordsoverview](/_fern-files/_img/07438f910bb49c2fda5f61d64c6482755d105554e2a0971bb24ae7bb3d498441.webp)

## Features

#### Centralized access to trust artifacts

The Trust Records API consolidates third-party Trust Service Provider (TSP) evidence from multiple sources into a single API endpoint. No more building and maintaining separate integrations to third-party providers; retrieve all TSP trust artifacts for an agreement participant with one call.

#### Secure, standards-based authentication

The API uses Docusign's standard OAuth authentication to access the specific resources within an account. This layered security model ensures that only authorized users with the trust_records_read scope can retrieve sensitive TSP evidence.

#### Audit-ready evidence retrieval

Retrieve the full set of TSP evidence artifacts — including identification protocol files, verification event metadata, and associated media — in a structured, machine-readable format. Evidence is scoped to your account and retrieved directly from Docusign, making it straightforward to build compliant, audit-ready workflows that meet regulatory requirements like NOM 151 and GwG.