Skip to main content

MailBluster

Overview​

MailBluster is available as a connector. Depending on your workspace and enabled features, it may be available as:

  • Source: Extract data from MailBluster into your destination (warehouse/lake).
  • Destination (Reverse ETL): Activate data into MailBluster.

Setup​

Prerequisites​

  • A MailBluster account
  • A MailBluster API key

Create a MailBluster API key​

  1. In MailBluster, navigate to your account/API settings.
  2. Create or copy an existing API key.
  3. Store it securely—you’ll use it to configure the connector.

Authentication​

MailBluster uses Bearer token authentication.

  • The connector sends requests to the MailBluster API with:
    • Authorization: Bearer <api_key>

During credential validation, the connector verifies access by calling:

  • GET https://api.mailbluster.com/api/lists

Configuration​

Required fields​

FieldTypeRequiredDescription
api_keystringYesYour MailBluster API key used for Bearer authentication.

Streams / Objects​

Destination: MailBluster Audiences (Reverse ETL)​

A MailBluster Audiences destination exists for credential validation, but loading/syncing is not yet available.

  • Credential validation: supported (checks access to the Lists endpoint)
  • Data loading: not supported yet (the destination is still in development)

If you need MailBluster audience activation, check back for updates once loading is released.

Hashing and normalization​

This connector does not currently expose field-level hashing options.

Data contract​

Not available yet for MailBluster Audiences destination loading, since sync behavior is still in development.