Maropost

Rekomi's Maropost integration upserts every approved affiliate via Maropost's Contacts API.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /accounts/{accountId}/contacts.json with contact: { email, first_name, last_name, options: { subscribe_list_ids: "{listId}" }, add_tags: [...] }. The endpoint is upsert by email.

Finding your credentials

In Maropost:

1. Account Settings → API. Copy your Auth Token.
2. Your Account ID is in the dashboard URL. It also determines your API region automatically: EU accounts are 4000-4999, CA accounts 5000 and up; Rekomi routes to the right regional host from the ID, no region setting needed.

Connecting Maropost in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Maropost card.
3. Paste both. Click Connect.

Tags

First-class. add_tags array of names. Tags must already exist in your Maropost account; Maropost does not create them. If a tag is missing, Maropost rejects the request and Rekomi retries once without tags so the subscribe itself still lands (the missing tags are dropped and logged). Create your tags in Maropost before configuring them in Rekomi.

Per-campaign overrides + per-affiliate visibility + troubleshooting + disconnecting

Same patterns as other CRM providers.

Provider-specific notes

• Auth via the authorization: ApiKey {token} header (the token never travels in the URL).
• Regional base URL is derived from the Account ID (below 4000 = US, 4000-4999 = EU, 5000+ = CA).
• subscribe_list_ids is a COMMA-SEPARATED STRING, not a JSON array (Maropost quirk).
• Add_tags IS a proper JSON array, but the tag names must pre-exist in the account.
• No public rate limit documented; 429 honors Retry-After.

---

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