Skip to main content

Sendlane

Overview​

Sendlane is supported in RudderStack as a Reverse ETL destination for syncing audience/member data into Sendlane.

Prerequisites​

  • A Sendlane account
  • A Sendlane API token with access to the Sendlane API

Authentication​

RudderStack authenticates to Sendlane using a Bearer API token.

Get your Sendlane API token​

In Sendlane, generate or copy an API token from your account settings (where Sendlane exposes API credentials). You’ll use this token in the destination configuration.

Set up the Sendlane destination in RudderStack​

  1. In RudderStack, go to Destinations and click New destination.
  2. Select Sendlane.
  3. Enter the required configuration values (see below).
  4. Click Test connection to validate the credentials.

Configuration settings​

SettingRequiredDescription
api_tokenYesYour Sendlane API token. RudderStack uses this token as a Bearer token to authenticate API requests.

Hashing and normalization​

This destination does not currently expose field-level hashing controls in RudderStack.

Data contract​

This destination is currently under development and does not yet support loading/syncing records. As a result, a stable RudderStack-to-Sendlane field mapping (data contract) is not yet available.

Supported objects (streams)​

This destination is currently under development. Connection testing validates credentials by calling Sendlane’s Lists endpoint (GET https://api.sendlane.com/v2/lists), but syncing data is not yet supported.