> 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

# Authentication

> Learn how to authenticate to call the Connected Field API endpoint.

## Authentication

All calls to the Docusign Connected Fields API are authenticated using an access token that your app obtains using one of the standard OAuth 2.0 grants supported by Docusign:

* [Public Authorization Code Grant](/platform/auth/public-authcode-get-token)
* [Confidential Auth Code Grant](/platform/auth/confidential-authcode-get-token)
* [Implicit Grant](/platform/auth/implicit-get-token)
* [JWT Grant](/platform/auth/jwt-get-token)

**Note:** See [Choose an OAuth type](/platform/auth/choose) for details on when to use each authentication type.

The only difference between authenticating with the Connected Fields API and the eSignature API is that, when requesting the access token in your OAuth2 scenario, you must request a special scope in addition to your other Docusign eSignature [Authentication scopes](/platform/auth/reference/scopes).

| Scope                         | Description                                                                   |
| ----------------------------- | ----------------------------------------------------------------------------- |
| `adm_store_unified_repo_read` | Required to read agreement data from the Navigator and Connected Fields APIs. |
| `signature`                   | Used for operations on the Docusign eSignature API.                           |

**Important:** If the required Connected Fields API scope was not explicitly requested, calls to the Connected Fields API will fail.

## Next steps

* See [How to send an envelope with extension app data verification fields](/docs/connected-fields-api/send-envelope-with-data-verification-fields) for a detailed walkthrough of how to send an envelope and validate the values of its connected fields.
* Learn how to get an access token with any authentication flow by viewing these guides:

  * [Authenticate with Public Authorization Code Grant](/platform/auth/public-authcode-get-token)
  * [Authenticate with the Confidential Authorization Code Grant](/platform/auth/confidential-authcode-get-token)
  * [Authenticate with the Implicit Grant](/platform/auth/implicit-get-token)
  * [Authenticate with the JWT Grant](/platform/auth/jwt-get-token)