Brevo

Rekomi's Brevo integration adds every approved affiliate to a Brevo contact list you pick.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v3/contacts with:

• email
• attributes.FIRSTNAME (first name)
• attributes.LASTNAME (last name)
• listIds: [your-chosen-list-id]
• updateEnabled: true (so re-syncing the same affiliate updates instead of returning 400)

The call is synchronous and the response is authoritative, 201 Created on new, 204 No Content on existing.

Finding your API key

In Brevo:

1. Top-right profile menu, then SMTP & API.
2. Open the API Keys tab.
3. Click Generate a new API key, name it "Rekomi".
4. Copy the key. It starts with xkeysib-.

If you enable Authorized IPs on the key (optional security feature), you must whitelist Rekomi's server IPs first, otherwise the connection test returns 401.

Connecting Brevo in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Brevo card.
3. Paste your API key. Click Connect.
4. Rekomi runs a test call against GET /v3/account.
5. Once connected, pick a default list from the dropdown.

Tags

Brevo has no first-class tags concept on the contacts endpoint. Rekomi does NOT send the configured tags to Brevo (sending unknown attribute names returns HTTP 400; the safer behavior is to drop them). If you want tag-like segmentation, create a Brevo contact attribute manually (Contacts > Settings > Contact attributes) and use Brevo's segment builder.

The Rekomi affiliate system tag is therefore also not applied for Brevo.

When sync fires

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

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

• HTTP 400 "duplicate_parameter", Means updateEnabled was missing or false on the request. Rekomi always sends updateEnabled: true; if you see this, contact support so we can check the request.
• HTTP 400 unknown attribute, Brevo rejects unknown attribute names with 400 (opposite of ConvertKit which silently drops). Rekomi only sends FIRSTNAME / LASTNAME which auto-exist on every Brevo account.
• HTTP 403, Authorized IPs restriction. Whitelist Rekomi's server IPs on the key, or remove the restriction.
• HTTP 429, Brevo's contacts endpoint throttles around 10 req/sec. Rekomi's worker paces at 1/sec so this is rare; when hit, Retry-After is honored.
• Sync fails with 401/403 after working before, The key was revoked or an Authorized IPs restriction was added. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Fix the key, reconnect, then use Resync all on the Failed tile of the integration page.

Disconnecting

From the Brevo connect page, click Disconnect. The integration row and per-campaign overrides are deleted. Historical sync history rows are preserved for audit.

---

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