beehiiv

Rekomi's beehiiv integration adds every approved affiliate as a subscriber to your beehiiv publication.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v2/publications/{publicationId}/subscriptions with email, reactivate_existing: true, send_welcome_email: false.

beehiiv has no list-picker concept; subscribers are publication-wide.

Platform limitation: beehiiv's subscription API has no first/last name fields, so affiliates arrive as email-only subscribers. (Custom fields exist but require pre-created field schemas; unknown names are silently dropped, so Rekomi doesn't attempt them.)

Finding your API key and publication ID

In beehiiv:

1. Settings → Integrations → API Keys.
2. Generate a new API key. Copy the key.
3. The same page shows your Publication ID (starts with pub_).

Connecting beehiiv in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the beehiiv card.
3. Paste your API key and publication ID. Click Connect.
4. Rekomi runs a test call against GET /v2/publications/{publicationId} to verify both.

Tags

beehiiv has no first-class tags concept. Custom fields exist but require the brand to pre-create the field schema in the beehiiv dashboard (unknown field names are silently dropped). Rekomi ignores the tags array on subscribe.

Referred customers and leads (optional)

Turn on Sync referred customers and leads on the integration page and every sale or lead Rekomi attributes to an affiliate is written to beehiiv as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• custom fields Rekomi referral link, Rekomi campaign, Rekomi referring affiliate, Rekomi referring affiliate code, Rekomi last event, Rekomi last sale amount, created on first use
• no tags (beehiiv has none); filter on Rekomi last event instead
• Affiliates synced by the section above also get Rekomi referral link, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default. Turning this on subscribes referred customers to your publication. Leave it off if you only want affiliates in beehiiv.

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, open the Settings tab and scroll to the CRM sync for this campaign section.

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

• 404 on test, Publication ID is wrong or the API key can't see that publication.
• publication_id_invalid, Publication ID doesn't match the pub_* shape. Re-copy from Settings → Integrations.
• 429, beehiiv throttles at 180 req/min. Rekomi honors the RateLimit-Reset header.
• Sync fails with 401/403 after working before, The API key was revoked. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh key, then use Resync all on the Failed tile of the integration page.

Disconnecting

From the beehiiv connect page, click Disconnect. Integration row + per-campaign overrides are deleted. Sync history is preserved.

---

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