> 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 On-Demand > The Notary On-Demand feature enables your eSignature API integration to send your recipients a link to a third-party online notary service for the signature and notarization of eSignature envelopes. eSignature REST API 2.1 only > **Note** > > Notary On-Demand is available in all developer accounts, but only in certain production account plans. Contact your account manager to find out whether Notary On-Demand is available for your production account plan. The Notary On-Demand feature enables your [eSignature REST API](/docs/esign-rest-api) integration to send your [recipients](/docs/esign-rest-api/esign101/concepts/recipients) a link to a third-party online notary service for the signature and notarization of eSignature [envelopes](/docs/esign-rest-api/esign101/concepts/envelopes). Docusign partners with [OneNotary](https://onenotary.us/) to provide online notarization. Notary On-Demand offers the following benefits: * Supplies notaries for organizations that do not have notaries on staff or whose volume is too large for in-house notaries to fully support * Supports signers in all 50 U.S. states * Provides notary services seven days a week, 24 hours a day * Enables multiple signers of the same document to complete the notary session at any mutually convenient time with minimal coordination by the envelope sender * Includes storage on the OneNotary platform of journal entries and notary session recordings * Supports multiple notary transactions per envelope ## Example use case A credit union can use Notary On-Demand to process auto loans. By leveraging Notary On-Demand, the organization avoids time delays and the expense of sending physical copies of loan agreements to signers. In addition, the credit union no longer expends resources scheduling appointments for signers and notaries to meet in person. Notary On-Demand further reduces the complexity associated with finding a notary in the correct jurisdiction, since the OneNotary service supports signers in all 50 states. With Notary On-Demand, all required signers for a document receive an email with simple instructions to join an online notary session at any convenient time. Within minutes, the signers’ identities are verified, and they can complete the notarization process in a recorded session. ## User experience When you programmatically create and send your customers an eSignature envelope that uses Notary On-Demand, the customer experience is as follows: 1. All signers receive an email with a link to join an online notary session with the third-party notary service. The link expires after 30 days. ![Signer invitation email](/_fern-files/_img/5c37313c190a4308997fdbbd329cac60ff31322ce06dc573d2d9b0afd67f2e22.webp) > **Note** > > On the developer environment, if **Suppress emails to embedded signers** is enabled in your account’s Signing Settings, notary session invitation emails are not sent to signers. On production, by default, enabling this setting does not prevent invitation emails from being sent. If you would like to enable this behavior for your account on production, contact [Docusign Support](https://support.docusign.com/s/contactSupport). See [Envelope Delivery](https://support.docusign.com/s/document-item?bundleId=pik1583277475390\&topicId=fur1583277359739.html) for more information about the setting. 2. If multiple signers are required for a notary session, they coordinate among themselves to determine a time to join the session, or the envelope sender can assist with this coordination. 3. Signers select the link in the email and are routed to the OneNotary platform to join the notary session. 4. To confirm their identity, the signers provide documentation and answer questions about their credit history. ![Notarization session identity verification](/_fern-files/_img/66ddb060ef0361feac5230fff9d16c8b22d5225e2c2fd1083bfa608855c032e4.webp) 5. After identity verification for all signers is complete, OneNotary provides a notary to join the online session. ![Notarization session notary joining](/_fern-files/_img/bf456fceacdedadc4a0d697f01824b0acb3724fc24d77b3dcfce99563d195dd0.webp) 6. The notary confirms that the signers’ identity verification succeeded. 7. During a recorded session, the signers complete and sign each document, and the notary signs or initials it and applies a digital seal. ![Notarized document](/_fern-files/_img/34bd6e8673fc13c1ab697e5738fd64e139f193798b9fe0a2f0efa595ab423c8a.webp) ## Implement Notary On-Demand in an API request To implement Notary On-Demand with a Docusign integration, submit an eSignature REST API [Envelopes:create](/docs/esign-rest-api/reference/envelopes/envelopes/create) request or equivalent [SDK](/docs/esign-rest-api/sdks) method call to generate an envelope. The envelope definition must include a *notary group*, which consists of a notary recipient and up to four signer recipients whose documents will be processed by that notary. All signers in a notary group are required to be signed into the online notary session concurrently. These properties identify a notary and signer recipients as members of the same notary group: 1. The notary recipient definition and the signer recipient definitions have the same value for the `routingOrder` property. 2. In each signer recipient definition, the `notaryId` property is set to the `recipientId` value in the notary recipient definition. This example `Envelopes:create` request body defines a notary group consisting of a notary recipient and two signer recipients. ```text { "emailSubject": "Please sign this document set", "documents": [ { "documentBase64": "UEs...AAA", "name": "Test document", "fileExtension": "pdf", "documentId": "1" } ], "recipients": { "notaries": [ { "name": "Notary", "recipientId": "1", "routingOrder": "1", "recipientSignatureProviders": [ { "sealDocumentsWithTabsOnly": "false", "signatureProviderName": "ds_authority_idv" } ], "tabs": { "notarySealTabs": [ { "xPosition": "200", "yPosition": "400", "documentId": "1", "pageNumber": "1" } ], "signHereTabs": [ { "xPosition": "200", "yPosition": "500", "documentId": "1", "pageNumber": "1" } ] }, "notaryType": "remote", "notarySourceType": "thirdparty", "notaryThirdPartyPartner": "onenotary" } ], "signers": [ { "clientUserId": "1000", "email": "signer0114a1@email.com", "name": "signer0114a1", "recipientId": "2", "routingOrder": "1", "notaryId": "1", "tabs": { "signHereTabs": [ { "anchorString": "Signature", "anchorXOffset": "1", "anchorYOffset": "0", "anchorIgnoreIfNotPresent": "false", "anchorUnits": "inches", "tabOrder": "3" } ], "textTabs": [ { "tabId": "nameondoc", "xposition": "144", "yposition": "96", "required": "true", "documentId": "1", "pageNumber": "1", "tabOrder": "1" }, { "tabId": "emailondoc", "xposition": "144", "yposition": "120", "required": "true", "documentId": "1", "pageNumber": "1", "tabOrder": "2" } ] } }, { "clientUserId": "1001", "email": "signer0114a2@email.com", "name": "signer0114a2", "recipientId": "3", "routingOrder": "1", "notaryId": "1", "tabs": { "signHereTabs": [ { "anchorString": "Signature", "anchorXOffset": "1", "anchorYOffset": "0", "anchorIgnoreIfNotPresent": "false", "anchorUnits": "inches", "tabOrder": "3" } ], "textTabs": [ { "tabId": "nameondoc", "xposition": "144", "yposition": "96", "required": "true", "documentId": "1", "pageNumber": "1", "tabOrder": "1" }, { "tabId": "emailondoc", "xposition": "144", "yposition": "120", "required": "true", "documentId": "1", "pageNumber": "1", } ] } } ] }, "status": "sent" } ``` For lists of the required properties and objects in the recipient definitions for Notary On-Demand notaries and signers, see [How to request a signature with third-party notarization](/docs/notary-api/how-to/request-signature-with-third-party-notarization). ## Notary session results ### Envelope status Envelopes that trigger a Notary On-Demand session remain in `sent` [status](/docs/esign-rest-api/esign101/concepts/envelopes/status-codes) until the notary session is completed. If a notary group is last in the envelope’s routing order, the envelope status will be `completed` after the Notary On-Demand session is completed. For an envelope with multiple notary groups, the envelope remains in `sent` status until all notary groups have completed their sessions. ### Notary information The response to any eSignature API request that returns recipient information, such as [EnvelopeRecipients:list](/docs/esign-rest-api/reference/envelopes/enveloperecipients/list), will include the notary name in the `EnvelopeRecipients.notaries.name` property and the notary’s email address in the `EnvelopeRecipients.notaries.email` property. ### Session recording Your integration can download a recording of a successful notary session using the Notary API [Envelopes:FindNotarialAssets](/docs/notary-api/reference/accounts/envelopes/findnotarialassetsv1_1) request. The response contains a list of session IDs and URLs for an envelope’s completed notary sessions, and a recording in MP4 format can be downloaded for each session. ### Connect events Notary On-Demand sessions can trigger several [Docusign Connect](/platform/webhooks/connect) events. You can set up a webhook listener to detect these events and take any needed action, such as sending a new envelope to the recipients whose notary session failed. See [Notary events](/platform/webhooks/connect/event-triggers#notary-events) for details about when each event is triggered. ## Error codes Docusign returns these codes to report errors related to Notary On-Demand: | Error code | Error message | Description | | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | NOTARY_HOSTED_SIGNER_ID_INVALID | The notary host signer ID is not valid. The notary for recipient ID = 1 has no signer associated with. | The request has a notary recipient defined, but it is not associated with any signer recipient. The signer recipient definition must include a `notaryId` property whose value matches the `recipientId` of the notary recipient. This error can also occur if more than four signers are associated with a single notary group. | | NOTARY_INVALID_MINIMUM_REQUIRED_NOTARY_SEAL_TAB | Notary recipient is required to have at least one notary seal tab. Notary \[notary name] is missing a notary seal tab, assign a notary seal tab to the notary. | The notary recipient whose name is referenced in the error message does not have a `notarySealTab` in the `tabs` definition. This tab type is required for a notary recipient. | | NOTARY_INVALID_ROUTING_ORDER | Notary and signer routing orders do not match. | The `routingOrder` property value must be the same for the signer recipient and the notary recipient who will notarize the signer’s document. | | NOTARY_INVALID_SIGNER_REQUIRED_TAB | Notary recipient is required to have at least one signHere or initialHere tab. Notary \[notary name] is missing a signature tab, assign a signHere or initialHere tab to the notary. | The notary recipient whose name is referenced in the error message does not have either a `signHereTab` or an `initialHereTab` in the `tabs` definition. At least one of these two tab types is required for a notary recipient. | | NOTARY_RECIPIENT_CORRECT_WAS_DELIVERED | You may not correct a delivered Notary or Notary Signer recipient. | The notary or signer recipient cannot be corrected for a sent envelope. | | NOTARY_SESSION_CANNOT_CANCEL_INVALID_STATE | The notary session cannot be cancelled. | The sender cannot void or delete an envelope if a notarization session is in progress. | | NOTARY_SIGNER_MUST_BE_CAPTIVE | Signers with Notaries must be captive | The signer recipient definition did not include a `clientUserId` property. | | NOTARY_THIRD_PARTY_NOT_ALLOWED | Third-party notary not enabled. | The Notary On-Demand feature is not enabled for the API account ID under which the request was sent. If you have a paid support plan or if you are enrolled in the Docusign Partner Program, contact [Docusign Support](https://support.docusign.com/s/contactSupport) for assistance. Other options are contacting your Docusign account executive or using the self-service resources listed in [FAQ: Support for developers and Docusign APIs](https://support.docusign.com/s/articles/FAQ-Support-for-developers-and-Docusign-APIs). | ## Notary On-Demand support with other eSignature features The following common eSignature features support Notary On-Demand: * [Remote signing](/docs/esign-rest-api/how-to/request-signature-email-remote) * [Templates](/docs/esign-rest-api/esign101/concepts/templates) * [Responsive signing](/docs/esign-rest-api/esign101/concepts/responsive) * [Phone authentication](/docs/esign-rest-api/esign101/concepts/recipients/auth#phone). Even if phone authentication is implemented for an envelope, signers still undergo identity verification on the OneNotary platform. These features, however, do not: * [Embedded signing](/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing) * [Bulk sending envelopes](/docs/esign-rest-api/esign101/concepts/envelopes/bulk-send) * [Focused view](/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing#focused-view) * [Embedded sending](/docs/esign-rest-api/esign101/concepts/embedding/embed-sender-correct-views) * [Composite templates](/docs/esign-rest-api/esign101/concepts/templates/composite) * [Document visibility](/docs/esign-rest-api/how-to/set-document-visibility) * [Knowledge-based authentication (KBA)](/docs/esign-rest-api/esign101/concepts/recipients/auth#kba) through the Docusign platform * [ID verification](/docs/esign-rest-api/esign101/concepts/recipients/auth#idv) through the Docusign platform ## Next steps * Get an overview of other notary options in the [Notary feature comparison](/docs/notary-api/notary101/notary-feature-comparison). * See [How to request a signature with third-party notarization](/docs/notary-api/how-to/request-signature-with-third-party-notarization) for a detailed walkthrough and code examples.