Authorization

Follow this guide to create a new Campaign Monitor credential that will allow Nexla to authenticate to and exchange data with your Campaign Monitor account.

Campaign Monitor

Prerequisites

The Campaign Monitor API supports two authentication methods: API Key (Basic Authentication) and OAuth 2.0. Before creating a credential in Nexla, you will need either an API key or OAuth application credentials from your Campaign Monitor account.

Obtain a Campaign Monitor API Key

An API key is the quickest way to authenticate with the Campaign Monitor API. Each Campaign Monitor account has a unique API key that grants access to the resources in that account.

1. Log in to your Campaign Monitor account.

2. Click your profile image or initials in the upper-right corner of the dashboard, then select Account settings from the dropdown menu.

3. In the Account Settings page, scroll down to the API keys section.

4. Click Show API key to reveal your existing API key. If no API key has been generated yet, click Generate API key to create one.

5. Copy the API key and store it securely. This key will be used as your credential in Nexla.

Campaign Monitor API keys grant full access to your account's data. Treat your API key like a password — do not share it publicly or commit it to source control. For additional information, see the Campaign Monitor API Keys documentation.

Register an OAuth Application (OAuth 2.0 Only)

OAuth 2.0 is the preferred authentication method for integrations that will be used by multiple users or third-party applications, as it does not require sharing your account password. To use OAuth 2.0, you must first register an OAuth application in Campaign Monitor.

1. Log in to your Campaign Monitor account and select a client if prompted.

2. Click Integrations in the top navigation bar.

3. In the right sidebar, click OAuth Registration.

4. Fill in the details for your new OAuth application:

   • Application Name: Enter a descriptive name for your application (e.g., "Nexla Integration").

   • Redirect URI: Enter the redirect URI that Campaign Monitor will use after a user authorizes your application. This URI must match exactly what you configure in Nexla.

   • Permissions / Scopes: Select the permission scopes your integration requires. Scopes are comma-separated and define what your application can do. Common scopes include ImportSubscribers, ViewReports, ManageLists, SendCampaigns, and ManageSubscribers. Grant only the scopes that are needed for your use case.

5. After submitting, Campaign Monitor will assign your application a Client ID and Client Secret. Copy both values and store them securely — the Client Secret will not be shown again.

For complete information about available OAuth scopes and the authorization flow, see the Campaign Monitor API Getting Started guide.

Create a Campaign Monitor Credential

• To create a new Campaign Monitor credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description

1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Method

Campaign Monitor credentials can be configured using either an API key or OAuth 2.0. Select the method that matches how you plan to authenticate:

Campaign Monitor Authentication Methods

API Key

Authenticate using your Campaign Monitor account API key. This method uses HTTP Basic Authentication, where your API key serves as the username. It is the simplest method to set up and is suitable for server-side integrations where you control the credentials.

1. Enter your Campaign Monitor API key in the **API Key** field. This is the key you retrieved or generated in your Campaign Monitor Account Settings under the API Keys section. The API key authenticates Nexla with Campaign Monitor on your behalf.

OAuth 2.0

Authenticate using OAuth 2.0, which is the preferred method for integrations accessed by multiple users or third-party applications. OAuth 2.0 allows Nexla to request only the specific permissions needed, without requiring you to share your Campaign Monitor password.

1. Enter your OAuth application's **Client ID** in the **Client ID** field. This is the unique identifier assigned to your application when you registered it in Campaign Monitor's OAuth Registration section under Integrations.
2. Enter your OAuth application's **Client Secret** in the **Client Secret** field. This is the secret key assigned to your application at registration. Keep this value secure and do not share it publicly.
3. Complete the OAuth authorization flow as prompted. Nexla will redirect you to Campaign Monitor's authorization page, where you will grant the requested permissions. After authorization, Nexla will receive an access token that will be used to authenticate API calls.

Save the Credential

1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.