Affiliates in the same stack as your transactional and marketing email.
Brevo (formerly Sendinblue) consolidates your sending, Rekomi consolidates your affiliate program into that same sending plane. Approved affiliates land in a Brevo contact list with GDPR-aware consent, ready for the marketing automations you already trust.

From paste-API-key to first paid affiliate in 10 minutes.
Paste your Brevo API key into Rekomi. Rekomi runs a test call to verify the key, then pulls your list/audience picker live from Brevo so you pick the right destination.
Affiliates apply via your public landing page or your bulk invite. Approve them manually, auto-approve on a campaign, or import an existing affiliate CSV from Rewardful.
Approved affiliates land in your Brevo list as tagged subscribers within seconds. Rekomi handles idempotency, retries, and per-campaign overrides; you handle the nurture sequence.
The exact Brevo fields Rekomi writes.
No surprise fields, no overwrites of contact data you already have. Empty values are omitted so existing nurture data is preserved.
email, the contact emailattributes.FIRSTNAMEandattributes.LASTNAME, uppercased attribute keys matching Brevo's contact schemalistIds: [your-chosen-list-id], the list you selected in the connect flowupdateEnabled: true, so re-syncing the same affiliate updates rather than 400-Conflicting- Synchronous response: 201 Created on new contact, 204 No Content on existing (Rekomi treats both as success)
What Brevo customers actually do with Rekomi.
GDPR-compliant affiliate onboarding
Affiliates only sync to Brevo after they've explicitly accepted your program terms (the Rekomi accept page captures this with a timestamped audit-log entry). Brevo then sees an opted-in contact with a clean consent timestamp, your DPA stays clean.
Combined transactional plus marketing nurture
Send the affiliate-program welcome via Brevo's marketing send, then the per-conversion 'you earned a commission' notification via Brevo's transactional API, both inside one Brevo account, one billing line, one IP reputation.
Multi-language affiliate cohorts
Brevo's marketing automation supports per-contact language attribute. Set `LANGUAGE = "fr"` on French affiliates and your existing French automation tree fires. Rekomi doesn't push the language attribute (your existing form/signup did), so the segmentation stays where it lives today.
Rekomi handles Brevo's edge cases so you don't have to.
Every CRM API has quirks. Rekomi's integration code was built and audited against the live Brevodocs, these are the ones you'd otherwise hit yourself.
Brevo keys are prefixed `xkeysib-` and are roughly 80 characters. The connect-flow form validates the format before a test call, if you paste a Sendinblue legacy v2 key, the form rejects it with a clear pointer to the v3 keys page.
If you enabled Brevo's Authorized IPs feature on the key, the test call returns 401 until Rekomi's egress IPs are whitelisted. The connect form surfaces this with the exact 401 error so you know it's an IP allowlist issue, not a wrong-key issue.
Brevo's POST /v3/contacts returns 204 with an empty body when the contact already exists and was just updated. Many integrations mishandle 204 as a failure. Rekomi treats 204 as the canonical 'updated' success path, re-syncing the same affiliate 100 times succeeds 100 times.
Brevo's rate-limit header is `x-sib-ratelimit-reset` (not standard `Retry-After`). Rekomi parses both, so 429s respect Brevo's actual reset window instead of defaulting to a fixed backoff.
Built for EU brands (or EU-DPA-required US brands) running Brevo as a unified transactional-plus-marketing stack. You're typically on Business or Enterprise tier with marketing automations + dedicated IPs. Rekomi keeps your affiliate program inside that same compliance envelope.
Common Brevo questions.
Does Brevo have an affiliate program?
Brevo runs a partner program for agencies and resellers, separate from running YOUR affiliate program. Rekomi is the platform that lets you do that, with Brevo as the contact + sending layer. Your affiliates land in Brevo with consent metadata so your marketing automations work on them the same way they work on any opted-in contact.
Is Brevo GDPR compliant?
Yes, Brevo is GDPR-compliant and EU-DPA-friendly with EU data residency on its Enterprise tier. Rekomi only pushes affiliates to Brevo after they've explicitly accepted your program's terms, with a server-side audit-log entry recording the accept timestamp. Your DPA chain stays auditable.
Does Rekomi sync to Brevo's SMS or WhatsApp channels?
No, Rekomi writes to Brevo's contact list (email channel). SMS and WhatsApp opt-ins stay under your control because phone-number consent has different regulatory requirements than email. Your Brevo automation can prompt the new affiliate to opt into other channels.
Which Brevo plan do I need?
Any plan with API access works, Free, Starter, Business, or Enterprise. Rekomi only writes contacts and reads lists, so even the free tier has the necessary permissions. The free tier has stricter daily send limits, but that affects Brevo's outbound marketing, not Rekomi's contact pushes.
Other CRMs that pair well.
Same persona, different stack. Pick the home your existing audience already lives in.
See all 38 integrations


Ten minutes to first click.
14-day free trial. Stripe-native. No card. Live this afternoon.
- 14-day free trial
- Cancel anytime, $0 charged