Broadcasts
Send a single email to all (or filtered) affiliates. Plan limits and unsubscribe semantics.
A broadcast is a single email you send to the affiliates in your organization. Use it for product updates, new asset drops, promo announcements, or asking creators to push a fresh campaign.
Where to send broadcasts
The Emails page (Emails, then Broadcasts) has the composer.
Form fields:
- Subject: 1-200 chars. No newlines or control characters (server-side validated against header injection).
- Message: 1 to 50,000 chars. Plain text.
- Campaign (optional): scope the broadcast to one campaign's affiliates. Leave blank for all affiliates in the org.
Personalize with variables like {{affiliate.firstName}} via the "Insert variable" menu on both the Subject and Message fields; each recipient sees their own values.
Click "Review & send". The confirm step shows the recipient count before anything goes out: how many approved affiliates will receive it and how many unsubscribed addresses will be skipped. Click "Confirm send" to send.
What recipients see
Each affiliate receives an email from notifications@mail.rekomi.com (brands with a verified custom sending domain send from their own domain instead; see Sending domain) with:
- Your subject line
- Your body
- A
List-Unsubscribeheader (RFC 8058 one-click unsubscribe compliant) - A
Reply-To: support@rekomi.comheader (configurable) - The standard Rekomi-branded HTML wrapper
The List-Unsubscribe header means Gmail and Yahoo show a one-click "Unsubscribe" button. Clicking it adds the recipient to the global suppression list. They will not receive broadcasts from any organization on Rekomi going forward. Transactional emails (payouts, application status) still arrive.
Suppression list
Three things land an affiliate on the suppression list:
- They clicked List-Unsubscribe.
- Their email hard-bounced (typo, full inbox, mail server rejected).
- They marked an earlier broadcast as spam.
Suppressed recipients are removed before the send, so the recipient count you see already reflects only deliverable addresses. The suppression list is global across organizations (we don't want different orgs spamming users who clearly want out).
Plan limits
Per-tier broadcast quotas (monthly, per recipient cap per broadcast):
| Tier | Monthly emails (total recipient sends) | Max recipients per broadcast |
|---|---|---|
| Starter | 1,000 | 100 |
| Growth | 10,000 | 1,000 |
| Pro | 50,000 | 10,000 |
| Enterprise | unlimited | unlimited |
The composer enforces both limits at send time. If you exceed your monthly cap, the next broadcast is blocked with an HTTP 402 response and an inline error.
Suspended broadcasts
If your organization's rate of bounces plus spam complaints exceeds 5 percent over a 24 hour window (minimum 20 sends), broadcast sending is automatically suspended; the next send attempt returns an error explaining why. Resuming requires contacting support. This protects domain reputation for everyone on mail.rekomi.com.
Rate limiting
Broadcast endpoint is rate-limited per user (10 sends per minute). The idempotency-key header (optional) allows safe retries if your dashboard tab loses connection mid-send; the same (orgId, idempotencyKey) returns the prior result within a 60-minute window.
Future: HTML compose, scheduled sends, segments
Three features on the deferred list:
- HTML composer with a WYSIWYG editor (today: plain text only)
- Scheduled sends (today: send-now only)
- Segment filters (e.g., "all affiliates who drove a sale in the last 30 days"; today: filter by campaign only)