> 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 how to take your Docusign integration live with the Admin API.

When you are ready to launch your 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 Admin API, you must have admin 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/admin-api/admin101/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 Admin 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 Admin API use slightly different paths. The examples in the how-to section use the developer paths; this table shows the production version of the base path.

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

## Next steps

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

* Learn about [Go-Live troubleshooting](/platform/go-live/troubleshooting).
* See what to do [After Go-Live](/platform/go-live/after-go-live).