> 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 with the Notary API.

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

* [Authentication Code Grant](/platform/auth/authcode/confidential-authcode-get-token)
* [Implicit Grant](/platform/auth/implicit/implicit-get-token)
* [JSON Web Token (JWT) Grant](/platform/auth/jwt/jwt-get-token)

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

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

The list of Docusign Notary API scopes that you can request and the types of operations that require it are listed below:

| Scope        | Description                         |
| ------------ | ----------------------------------- |
| notary_write | Required to update Notary API data. |
| notary_read  | Required to get Notary API data.    |

Additionally, some additional scopes introduced in other APIs are required to make calls to some Notary API endpoints, listed below:

| Scope             | Description                                                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------------- |
| organization_read | Required to call endpoints for interacting with notary pools, pool users, pool invites, and bulk actions. |
| signature         | Required to call Jurisdiction POST and PUT endpoints.                                                     |

**Important:** If the required Docusign Notary scopes were not explicitly requested, calls to the Docusign Notary API will fail.

## Next Steps

* See [API rules and resource limits](/docs/notary-api/notary101/rules-and-limits) for the Notary API.

* See [How-tos](/docs/notary-api/how-to) that provide walkthroughs for common Notary API scenarios.

* Learn how to get an access token with any authentication flow by viewing these guides:

* [How to get an access token with Authorization Code Grant](/platform/auth/authcode/authcode-get-token)

* [How to get an access token with Implicit Grant](/platform/auth/implicit/implicit-get-token)

* [How to get an access token with JSON Web Token (JWT) Grant](/platform/auth/jwt/jwt-get-token)