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 body (successCount, failCount, invalidEmails, failedUpdates), if failCount is non-zero or invalidEmails/failedUpdates carry entries, 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

Both Iterable data centers are supported: enter us for US-hosted accounts (api.iterable.com) or eu for European Data Center accounts (api.eu.iterable.com) in the Region field when connecting. Iterable keys are region-scoped, an EU key will not work against US and vice versa.

Connecting Iterable in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Iterable card.
3. Enter your region (us or eu) and 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". Note that a re-sync replaces the whole dataFields.tags array (Iterable's bulk update overwrites array fields), so don't store your own values in that field.

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 reported a failure in the body (failCount or a failed-update bucket). 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) and that the region matches where the key was issued. Repeated auth failures mark the integration "action needed" and trigger a reconnect email; after fixing, use Resync all on the Failed tile.

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.