> 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

# Resource tokens

The Docusign ID Evidence API uses [OAUTH Authentication](/platform/auth) to make secure API calls just as all Docusign APIs do. However, the ID Evidence API takes this one step further to secure access to the specific resources within an account with a resource token.

An OAuth token is used to request a resource token, which you then supply as a bearer token in the next request to ID Evidence to retrieve events or media. A resource token is valid for 2 minutes. For more information about how to use resource tokens and the ID Evidence API to retrieve events and media, see the [ID Evidence How-tos](/docs/idevidence-api/how-to).