Iterable
This page contains the setup guide and reference information for the Iterable source connector.
Prerequisites
To set up the Iterable source connector, you'll need the Iterable Server-side
API Key with standard
permissions.
Set up the Iterable connector in Airbyte
- Log into your Airbyte Cloud account or navigate to the Airbyte Open Source dashboard.
- Click Sources and then click + New source.
- On the Set up the source page, select Iterable from the Source type dropdown.
- Enter the name for the Iterable connector.
- For API Key, enter the Iterable API key.
- For Start Date, enter the date in YYYY-MM-DDTHH:mm:ssZ format. The data added on and after this date will be replicated.
- Click Set up source.
Supported sync modes
The Iterable source connector supports the following sync modes:
Supported Streams
- Campaigns
- Campaign Metrics
- Channels
- Email Bounce (Incremental)
- Email Click (Incremental)
- Email Complaint (Incremental)
- Email Open (Incremental)
- Email Send (Incremental)
- Email Send Skip (Incremental)
- Email Subscribe (Incremental)
- Email Unsubscribe (Incremental)
- Events
- Lists
- List Users
- Message Types
- Metadata
- Templates (Incremental)
- Users (Incremental)
- PushSend (Incremental)
- PushSendSkip (Incremental)
- PushOpen (Incremental)
- PushUninstall (Incremental)
- PushBounce (Incremental)
- WebPushSend (Incremental)
- WebPushClick (Incremental)
- WebPushSendSkip (Incremental)
- InAppSend (Incremental)
- InAppOpen (Incremental)
- InAppClick (Incremental)
- InAppClose (Incremental)
- InAppDelete (Incremental)
- InAppDelivery (Incremental)
- InAppSendSkip (Incremental)
- InboxSession (Incremental)
- InboxMessageImpression (Incremental)
- SmsSend (Incremental)
- SmsBounce (Incremental)
- SmsClick (Incremental)
- SmsReceived (Incremental)
- SmsSendSkip (Incremental)
- SmsUsageInfo (Incremental)
- Purchase (Incremental)
- CustomEvent (Incremental)
- HostedUnsubscribeClick (Incremental)
Additional notes
List Users Stream when meet 500 - Generic Error
will skip a broken slice and keep going with the next one. This is related to unexpected failures when trying to get users list for specific list ids. See #24968 issue for more details.
Reference
Config fields reference
Field
Type
Property name
string
api_key
string
start_date