---
schema_version: "1"
id: 37a90fed685235f70bef4669c7d64e7c0194bd4186c2dfe16359ea30d5051719
title: Promoting an API Instance to Another Environment
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/promote-api-task.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/promote-api-task
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 6c9b24095dfa296ce790d87b135af65237d705e29aa15f8c23885e8e547a0424
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Promoting an API Instance to Another Environment

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Before promoting an API instance to another environment, ensure that you have the
`Manage APIs Configuration` permission.

To promote an entity, you must have permissions to view and manage the entity. For example, you must
have the `View Policies` and `Manage Policies` permissions to promote a policy.

## Promote an API Instance from Another Environment

1.  Navigate to **Anypoint Platform** > **API Manager**.

2.  In **API Administration**, click **Add API** and select **Promote API from environment**.

3.  Select the **Source Environment**.

4.  Select the **API** by entering the name of the API into the search field.

5.  Select the **API Version**.

6.  Select the **API instance label**.

7.  Optionally, uncheck any of the **Include in Promotion** options you want to exclude.

8.  Click **Promote**.

9.  Review and update the Runtime & Endpoint Configuration details as needed and click **Save**.

Promoting an API instance affects only the API definition, not the existing deployed applications
subscribed to the instance. After promoting an API, the **API Label** remains the same, but the
**API Instance ID** changes.

For existing applications that must subscribe to a promoted API instance:

1.  Update the **API Instance ID** within the application.

2.  Update the application’s client ID and secret (because each environment has a different client
    ID and secret).

## See Also

- [Granting Permission to Access an environment](https://docs.mulesoft.com/api-manager/latest/environment-permission-task)

- [Environments](https://docs.mulesoft.com/access-management/environments)

- [Creating an API instance on API Manager](https://docs.mulesoft.com/api-manager/latest/api-instance-landing-page)