> 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 how to move your Click API integration from the development environment into a production environment, including information about the requirements for going-live, best practices, and troubleshooting.

## Go-Live

Before you can begin the Go-Live process, you must have a paid production Docusign account with a plan that includes elastic signing.

To start Go-Live review for your application:

1. Open a [Docusign Support case](https://support.docusign.com/CSP_DSClogin?startURL=%2Fen%2FcaseOverview%3Fdfl%3D1) to create a request.
2. In the **Choose Case Subject** screen, select **APIs and & Developement**, then **Docusign APIs**.
3. Select the **Add Case Details** button.
4. In the **Add New Case** screen, enter “Click API Go-Live\*\*”\*\* in the **Case Subject** field, then enter your integration's data and a brief description.
5. Select **Submit Case**.

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

After the form is processed (which takes up to three business days), your integration key will be copied into production, enabling your app to call the production API endpoints.

## API endpoints

The developer and production endpoints for most Docusign APIs use slightly different paths. This table lists the endpoint base paths for each Docusign environment so you know how to modify your code when you migrate from the developer environment to production.

| Environment | API base URI                                  | Web site login URL |
| ----------- | --------------------------------------------- | ------------------ |
| Developer   | `https://demo.docusign.net/restapi/v2.1/`     |                    |
| Production  | `https://{server}.docusign.net/restapi/v2.1/` |                    |

For information on the CLM API endpoints, see CLM [API 101](/docs/clm-api/clm101).

**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 the [/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&_LANG=enus). To access production API endpoints, you'll need to enable your integration key in the production environment.

## Next steps

* For a list of issues that can prevent an app from passing a Go-Live review, see [Go-Live troubleshooting](/platform/go-live/troubleshooting).
* For a list of configuration changes required for the production environment, see [After Go-Live](/platform/go-live/after-go-live).