MailerLite

Rekomi's MailerLite integration adds every approved affiliate to a MailerLite group you pick.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /api/subscribers on connect.mailerlite.com with:

• email
• fields.name (first name)
• fields.last_name
• groups: [your-chosen-group-id]
• status: "active"

MailerLite's /api/subscribers endpoint is upsert by email, re-syncing the same affiliate returns 200 with the updated record. The call is synchronous, so a "Succeeded" in Rekomi means the subscriber is actually in your group.

Finding your API token

In MailerLite:

1. Click Integrations in the sidebar, then MailerLite API.
2. Click Generate new token, give it a name like "Rekomi".
3. Copy the token immediately. MailerLite does not store it in plaintext, so once you close the dialog you can never see it again.

If you regenerated the token because the old one is lost, disconnect MailerLite in Rekomi and reconnect with the new token.

Connecting MailerLite in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the MailerLite card.
3. Paste your API token. Click Connect.
4. Rekomi runs a test call against GET /api/groups?limit=1 to verify the token.
5. Once connected, pick a default group from the dropdown.

Tags

MailerLite has no separate tags concept, groups are the tagging mechanism. Rekomi only sets the chosen group on subscribe; the Rekomi affiliate system tag is not applied (it would require creating an additional group). If you want to distinguish Rekomi-originated subscribers, create a separate group for them and pick that as your sync target.

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 to:

• Disable MailerLite for this campaign.
• Send this campaign's affiliates to a different group.

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

• Unknown custom fields silently dropped, MailerLite drops unknown field keys in the fields map without error. name and last_name are standard built-ins and always land; other custom fields must be pre-created via MailerLite's Subscriber fields screen.
• Re-subscribing a previously unsubscribed email, MailerLite blocks this for abuse prevention. Rekomi does NOT pass the resubscribe: true flag because reactivating without explicit consent is a deliverability footgun. Re-opting in a former unsubscriber must be done manually.
• 429 rate limit, MailerLite throttles at 120 req/min. Rekomi's worker paces at 1/sec so this is rare; when hit, the response carries Retry-After which Rekomi honors.
• Sync fails with 401/403 after working before, The token was revoked or regenerated. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh token, then use Resync all on the Failed tile of the integration page.

Disconnecting

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

---

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