> 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

# Go-Live

> Learn about the process for go-live for apps that use the Notary API.

When you are ready to launch your Notary API app in production, you will need to promote your application’s integration key from your developer account to a production Docusign account by passing a Go-Live review, similar to the [Go-Live](/docs/esign-rest-api/go-live) process for the eSignature REST API.

Before you can begin the Go-Live process for an app that uses the Notary API, you must have Notary API access added to your account.

When you are ready to start a Go-Live review for your application, follow the steps described on the [Go-Live](/docs/esign-rest-api/go-live) overview page for Docusign eSignature.

**Note:** If your application fails Go-Live review, you may be required to bring it into compliance with the [API rules and resource limits](/docs/notary-api/notary101/rules-and-limits) before you can Go-Live.

After the form is processed, your integration key will be copied into your production account, enabling your app to call production Notary API endpoints. Note that although your key is copied over, you must configure it with all required values in the production environment separately; configuration settings are not copied automatically.

## API endpoints

The developer and production endpoints for the Notary API use slightly different paths. The examples on the Developer Center use the developer paths; the following table shows the production version of the base path.

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

**Note:** \{server} is the data center location of your production account (for example, **CA**, **NA2**, or **EU**). You can obtain your production data center location from:

* The `base_uri` in the response of a call to [/oauth/userinfo](/platform/auth/reference/user-info). If you obtain the `base_uri` in this way, you should do it once when the user authenticates for the first time and cache the response.
* The **Account Base URI** section of the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page

For a full list of sites, see [Site certificates](https://support.docusign.com/s/document-item?bundleId=khf1655309726546\&topicId=kkh1657307586557.html&\<i>LANG=enus).

## Next steps

Learn more about the Go-Live process and what you need to do after you pass Go-Live with these resources:

* [Go-Live troubleshooting](/platform/go-live/troubleshooting)
* [After Go-Live](/platform/go-live/after-go-live)