Sendpulse

SendPulse is a marketing automation platform that offers triggered emails, chatbots, scheduled SMS, and web push notifications, enabling businesses to create comprehensive multi-channel marketing campaigns.

Power end-to-end data operations for your Sendpulse API with Nexla. Our bi-directional Sendpulse connector is purpose-built for Sendpulse, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Sendpulse or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Sendpulse workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

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.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	Yes	Your ID
Client Secret	Yes	Yes	Your Secret

Create a credential in Nexla

1. 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

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

3. 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.

4. 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.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the SendPulse connector tile, then select the credential that will be used to connect to your SendPulse account, and click Next; or, create a new SendPulse credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common SendPulse endpoints. Each template is designed specifically for the corresponding SendPulse endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Mailing List

This endpoint template retrieves mailing lists from your SendPulse account. Use this template when you need to retrieve information about available mailing lists, including list IDs, names, and other mailing list metadata.

• This endpoint automatically retrieves all mailing lists from your SendPulse account. No additional configuration is required beyond selecting this endpoint template.

This endpoint returns mailing lists from your SendPulse account, including list IDs, names, and other mailing list metadata. Use this endpoint to discover which mailing lists are available in your SendPulse account.

For detailed information about mailing lists, API response structures, and available list data, see the SendPulse API documentation.

Get Emails List

This endpoint template retrieves a list of emails from a specific mailing list in your SendPulse account. Use this template when you need to retrieve information about emails in a mailing list, including email addresses and other email metadata.

• Enter the mailing list ID in the ID field. This should be the unique identifier of the mailing list for which you want to retrieve emails. The mailing list ID determines which mailing list's emails will be retrieved.

This endpoint returns a list of emails from a specific mailing list in your SendPulse account, including email addresses and other email metadata. Use this endpoint to retrieve all emails associated with a specific mailing list.

For detailed information about email lists, API response structures, and available email data, see the SendPulse API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

SendPulse data sources can also be manually configured to ingest data from any valid SendPulse API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The SendPulse API typically uses the GET method for retrieving data. The API endpoint URL should be the complete URL to your SendPulse endpoint, for example https://api.sendpulse.com/addressbooks or https://api.sendpulse.com/addressbooks/{id}/emails, including any required path parameters.

For the Response Data Path, use $[*] to extract all items from the response array, or $ to extract the entire response for single record endpoints, depending on your endpoint. The JSONPath expression must correctly reference the structure of your SendPulse API response, which may vary by endpoint.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new SendPulse data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the SendPulse destination, and select the Send to Destination option from the menu. Select the SendPulse connector from the list of available destination connectors, then select the credential that will be used to connect to your SendPulse account, and click Next; or, create a new SendPulse credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common SendPulse endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create mailing List

This endpoint template creates a mailing list in your SendPulse account using records from a Nexset. Use this template when you need to create new mailing lists in your SendPulse account.

• This endpoint sends data as JSON in the request body to create mailing lists in your SendPulse account. Each record from your Nexset will be sent as a separate API request to create a new mailing list in SendPulse. The request body should contain the mailing list data in the format required by the SendPulse API.

This endpoint sends data as JSON in the request body to create mailing lists in your SendPulse account. Each record from your Nexset will be sent as a separate API request to create a new mailing list in SendPulse. The request body should contain the mailing list data in the format required by the SendPulse API.

The mailing list structure must match the SendPulse API's expected format. For detailed information about mailing list creation, request body formats, and available mailing list properties, see the SendPulse API documentation.

Delete Emails List

This endpoint template deletes a list of emails from a mailing list in your SendPulse account using records from a Nexset. Use this template when you need to remove emails from a mailing list.

• Enter the mailing list ID in the ID field. This should be the unique identifier of the mailing list from which you want to delete emails. The mailing list ID determines which mailing list's emails will be deleted.

This endpoint sends data as JSON in the request body to delete emails from a mailing list in your SendPulse account. Each record from your Nexset will be sent as a separate API request to delete emails from the specified mailing list. The request body should contain the email data in the format required by the SendPulse API.

For detailed information about email deletion, request body formats, and available email properties, see the SendPulse API documentation.

Manual configuration

SendPulse destinations can also be manually configured to send data to any valid SendPulse API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the SendPulse API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The SendPulse API typically uses the POST method for creating resources and deleting emails, and expects JSON format for all requests. The API endpoint URL should be the complete URL to your SendPulse endpoint, for example https://api.sendpulse.com/addressbooks or https://api.sendpulse.com/addressbooks/{id}/emails, including any required path parameters.

The request body should contain the resource data formatted as JSON, with field names matching the SendPulse API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings. SendPulse API uses specific structures for different endpoints (mailing lists, emails, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the SendPulse API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured SendPulse endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the SendPulse endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.