---
schema_version: "1"
id: d1858bf71b562822c771aabda591e1f46ad78a3b012f8644c50db5ffeafab713
title: Create an OAuth 2.0 API Integration in Enhanced Packages
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-app-development/create-integration-enhanced.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/create-integration-enhanced.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: fa138a5e582006b4f7790b626b14719e04e912a3907e791ab9879688924daedb
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# Create an OAuth 2.0 API Integration in Enhanced Packages

Use an OAuth 2.0 integration to enable external apps to securely integrate with Marketing Cloud Engagement. An admin can create an installed package and configure the settings for OAuth 2.0 authentication.

| User Permissions Needed                    |       |
| ------------------------------------------ | ----- |
| To create an installed package             | Admin |
| To add a component to an installed package | Admin |

1. [Create an installed package](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/install-packages.md) with enhanced functionality, or go to an existing package that was created with enhanced functionality.
2. In the Components section, click **Add Component**.
3. Select **API Integration**.

   **note:** After you add an API Integration component to an installed package, you can’t remove it.

4. Select an [integration type](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/installed-package-types.md).
5. Set the properties for the integration, including scopes and the redirect URIs for web and public apps.

   You can’t use a redirect URI that is URL-encoded. You can use `https://127.0.0.1:80/` as a redirect URI for local testing.

6. If you’re creating a public app integration, save the component.

   If you’re creating a server-to-server or web app integration, save the client secret in a secure location, because after you finish creating the component, you can’t view the client secret again.

7. Click **Finish**.

## Next Steps

If you created a server-to-server or web app integration, update your external apps to use the client secret.

To protect the security of your installed packages, we recommend that you [rotate your OAuth secrets](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/rotate-oauth2-secret.md) periodically.

## See Also

- [Rotate an OAuth2 Secret](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/rotate-oauth2-secret.md)
- [Installed Packages Scope](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/data-access-permissions.md)
- [Tenant-Specific API Endpoints](https://developer.salesforce.com/docs/marketing/marketing-cloud/mc-apis/your-subdomain-tenant-specific-endpoints.md)