Skip to main content

Authorization

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

Sendpulse

Prerequisites​

Before creating a SendPulse credential, you need to obtain your Client ID and Client Secret from your SendPulse account. SendPulse uses Token Authentication, which requires authenticating with your Client ID and Client Secret to obtain an access token that is then used for all API requests.

To obtain your SendPulse API credentials, follow these steps:

  1. Sign in to your SendPulse account using your administrator credentials.

  2. Navigate to your account settings or API management section in the SendPulse interface.

  3. Look for the API or API Keys section in your account settings, or navigate to Settings > API or Account > API.

  4. If you don't have API credentials yet, look for the option to generate or view your Client ID and Client Secret.

  5. Click Generate API Credentials or Create API Application to create new API credentials.

  6. Configure your API credential settings:

    • Enter a name for the application (e.g., "Nexla Integration")
    • Review and select the permissions or scopes for the credentials (if applicable)

  7. Click Generate or Create to create the API credentials.

  8. Your Client ID will be displayed immediately after creation. Copy the Client ID.

  9. Your Client Secret will be displayed immediately after creation. Copy the Client Secret immediately, as it may not be accessible again after you navigate away from the page.

  10. Store both credentials securely, as you will need them to configure your Nexla credential. The Client ID and Client Secret are sensitive information and should be kept confidential.

The Client ID and Client Secret are used to authenticate with the SendPulse API authentication endpoint (/integrations/api) to obtain an access token. The access token is then sent in the Authorization header with the Bearer prefix for all subsequent API requests to the SendPulse API. The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your SendPulse account settings and generate new ones. For detailed information about SendPulse authentication, API access, and available endpoints, refer to the SendPulse API documentation.

Create a SendPulse Credential​

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

New Credential Overlay – SendPulse

SendpulseCred.png

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 provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Token Authentication​

SendPulse uses Token Authentication for all API requests. Your Client ID and Client Secret are used to authenticate with the SendPulse API authentication endpoint to obtain an access token, which is then used for all subsequent API requests.

  1. Enter your SendPulse Client ID in the Client ID field. This is the Client ID you obtained from your SendPulse account settings (Settings > API or Account > API). The Client ID is used along with the Client Secret to authenticate with the SendPulse API authentication endpoint and obtain an access token.

  2. Enter your SendPulse Client Secret in the Client Secret field. This is the Client Secret you obtained from your SendPulse account settings. The Client Secret is used along with the Client ID to authenticate with the SendPulse API authentication endpoint and obtain an access token. The Client Secret is sensitive information and must be kept confidential.

    Your SendPulse API credentials can be found in your SendPulse account settings under Settings > API or Account > API. The Client ID and Client Secret are used to authenticate with the SendPulse API authentication endpoint (/integrations/api) to obtain an access token. The access token is then automatically sent in the Authorization: Bearer {token} header for all subsequent API requests to the SendPulse API.

    The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your SendPulse account settings and generate new ones. The Client ID and Client Secret provide access to your SendPulse account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

    For detailed information about SendPulse authentication, API access, and available endpoints, see the SendPulse API documentation.

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.