Iterable

Rekomi's Iterable integration subscribes every approved affiliate to an Iterable list with first/last name + tags written into the user's dataFields for segmentation.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /api/lists/subscribe with:

{
  "listId": 12345,
  "subscribers": [{
    "email": "...",
    "dataFields": {
      "firstName": "...",
      "lastName": "...",
      "tags": ["Rekomi affiliate"]
    }
  }]
}

Iterable returns HTTP 200 even on partial failure. Rekomi parses the response and checks code != "Success" or non-empty failedUpdates.* arrays, if either is true, the sync is marked Failed with the reason.

Finding your API key

In Iterable:

1. Integrations → API Keys.
2. Click Create new API Key. Choose Server-side (NOT JS-Web SDK, JS keys 401 on the subscribe endpoint).
3. Copy the key.

Region

Rekomi connects to api.iterable.com (US data center). Iterable accounts on the EU region (api.eu.iterable.com) are not yet supported.

Connecting Iterable in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Iterable card.
3. Paste your API key. Click Connect.
4. Rekomi runs a test call against GET /api/lists.

Tags

Iterable has no native tag primitive. Rekomi writes the tags array into dataFields.tags so you can build segments with rules like dataFields.tags contains "Rekomi affiliate".

When sync fires

• Default: only Approved affiliates sync.
• Optional: turn on "Include applicants before approval" to also sync Pending.

Per-campaign overrides

Each campaign can override the account-level configuration. From a campaign's detail page, click the CRM sync tab.

Per-affiliate sync visibility

Open any affiliate's detail page. The CRM sync panel shows the per-CRM status. Resync clears prior jobs and re-fires the sync.

Troubleshooting

• iterable_partial_failure, Iterable returned 200 but code != "Success". Inspect the affiliate's CRM sync panel for the body snippet.
• iterable_failed_update:invalidEmails, Email rejected by Iterable validation.
• iterable_failed_update:notSignedUp, User is in your project but isn't yet a list-subscriber. Iterable doc-recommended behavior: re-fire the subscribe.
• 401 on server-side key, Verify you copied a SERVER-SIDE key, not a JS-Web SDK key.

Disconnecting

From the Iterable connect page, click Disconnect. Integration row + per-campaign overrides are deleted. Sync history is preserved.

See the iterable integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.