Poplar

Poplar (heypoplar.com) is a direct mail marketing platform for creating, targeting, and tracking data-driven postcard and mailer campaigns. The Poplar API lets you retrieve campaigns, creatives, audiences, and mailings, and trigger mailers, orders, and suppression-list updates programmatically.

Power end-to-end data operations for your Poplar API with Nexla. Our bi-directional Poplar connector is purpose-built for Poplar, 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 Poplar or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Poplar 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 Poplar credential, you need an API access token from your Poplar account. Poplar uses bearer token authentication: the token is sent in the Authorization header as Bearer <access token> on every request.

To obtain your Poplar API token, follow these steps:

1. Sign in to your Poplar account at heypoplar.com.

2. Navigate to the API page in your account dashboard, where your access tokens are managed.

3. Copy your Access Token. Poplar provides both Test and Production access tokens; use the Production token for full API access, as Test tokens are limited to the mailings endpoint.

4. Store the token securely. Your access token can access your private Poplar data and should be treated like a password. If a token is compromised, you can revoke it from the same dashboard page.

For detailed information about Poplar API authentication and available endpoints, refer to the Poplar API Documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key used to authenticate requests to the Poplar API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

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 Poplar access token in the API Key field. This token is sent in the Authorization header as Bearer <access token> on all requests to the Poplar API and must be kept confidential.

   Your access token can access your private Poplar data and should be treated like a password. If your token is compromised, revoke it from the API page in your Poplar dashboard and generate a new one.

   For detailed information about Poplar API authentication and available endpoints, see the Poplar API Documentation.

4. 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 Poplar connector tile, then select the credential that will be used to connect to Poplar, and click Next; or, create a new Poplar 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 Poplar endpoints. 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.

[Rest API] List Campaigns

Retrieve campaigns.

• This endpoint template fetches the list of campaigns from your Poplar account so they can be ingested into Nexla for analysis, reporting, or integration.

For detailed information about campaigns and the available response fields, see the Poplar API Documentation.

[Rest API] List Creatives

Retrieve creatives.

• This endpoint template fetches the list of creatives from your Poplar account so they can be ingested into Nexla for analysis, reporting, or integration.

For detailed information about creatives and the available response fields, see the Poplar API Documentation.

[Rest API] List Audiences

Retrieve audiences.

• This endpoint template fetches the list of audiences from your Poplar account so they can be ingested into Nexla for analysis, reporting, or integration.

For detailed information about audiences and the available response fields, see the Poplar API Documentation.

[Rest API] List Mailings

Retrieve mailings.

• This endpoint template fetches the list of mailings from your Poplar account. The endpoint is paginated, and Nexla automatically iterates through pages to fetch all available mailings.

For detailed information about mailings and the available response fields, see the Poplar API Documentation.

[Rest API] List Me

Retrieve me.

• This endpoint template fetches details about the authenticated Poplar account so they can be ingested into Nexla for verification or reference.

For detailed information about the account details returned by this endpoint, see the Poplar 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

Poplar data sources can also be manually configured to ingest data from any valid Poplar API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request 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.

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 Poplar 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 Poplar destination, and select the Send to Destination option from the menu. Select the Poplar connector from the list of available destination connectors, then select the credential that will be used to connect to Poplar, and click Next; or, create a new Poplar 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 Poplar 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.

[Rest API] Create Mailing

Trigger a mailer for a given campaign, accepting recipient details, optional creative selection, merge tags, and scheduled send time.

• This endpoint sends each record from your Nexset as a JSON request body to trigger a mailer. Ensure your records include the campaign identifier and recipient details required by the Poplar API.

The request body must match the Poplar API's expected format for mailings. For detailed information about request fields and options, see the Poplar API Documentation.

[Rest API] Create Order

Report a new transaction or order, requiring shipping/billing address or customer email identifiers.

• This endpoint sends each record from your Nexset as a JSON request body to report an order. Ensure your records include the shipping/billing address or customer email identifiers required by the Poplar API.

The request body must match the Poplar API's expected format for orders. For detailed information about request fields and options, see the Poplar API Documentation.

[Rest API] Create Do Not Mail Entry

Add a recipient to the do-not-mail suppression list using email, hashed email, customer identifier, or mailing address.

• This endpoint sends each record from your Nexset as a JSON request body to add a recipient to the suppression list. Ensure your records include an email, hashed email, customer identifier, or mailing address.

The request body must match the Poplar API's expected format for do-not-mail entries. For detailed information about request fields and options, see the Poplar API Documentation.

[Rest API] Create Audience Member

Add a member to an existing audience list by audience ID, accepting address, email, email_sha256, or identifier.

• This endpoint sends each record from your Nexset as a JSON request body to add a member to an audience. You must provide the Audience ID of the audience to add the member to, along with an address, email, email_sha256, or identifier.

The request body must match the Poplar API's expected format for audience members. For detailed information about request fields and options, see the Poplar API Documentation.

Manual configuration

Poplar destinations can also be manually configured to send data to any valid Poplar API endpoint. 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.

Poplar APIs expect JSON format in the request body for these operations. Ensure your Nexset records are shaped to match each endpoint's expected fields.

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 Poplar endpoint, open the destination resource menu, and select Activate.

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