> 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

# Notary concepts

> Learn about concepts used by the Notary API, such as notary pools and journaling.

The Docusign Notary API process works by enabling you to connect notaries working with your organization to the envelopes and documents that need to be notarized.

## API endpoint base paths

The development (demo) and production endpoints for the Notary API use slightly different paths. The examples in this topic use the development (demo) paths; the following table shows the production version of the base path.

| Environment | Notary API base URI | eSignature API base URI          |
| ----------- | ------------------- | -------------------------------- |
| Development | ...                 |                                  |
| Production  | ...                 | https\://\{server}.docusign.net/ |

## Next Steps

* Learn about the [Notary pool](/docs/notary-api/notary101/concepts/notary-pool).
* Learn about [Jurisdiction](/docs/notary-api/notary101/concepts/jurisdiction).
* See how Notary API supports [Journaling](/docs/notary-api/notary101/concepts/journaling).
* Learn about [Notary recipients](/docs/notary-api/notary101/concepts/notary-recipients), how they work, and their limitations.