Newsletter
Subscriber capture and lists
Newsletter isn't part of this workspace
This org has no newsletter tenant. Add the Newsletter product to your plan to enable it.
Plan & Invoices Total subscribers
—
all time
Last 7 days
—
new sign-ups
Last 30 days
—
new sign-ups
Today
—
since midnight
Recent sign-ups
| Source | When | |
|---|---|---|
| Loading… | ||
Top sources
From the most recent sign-ups.
Loading…
Next steps
Drop the <ff-newsletter> snippet on your site, or POST to the subscribe URL directly.
Subscribers
| Source | Status | Subscribed | ||
|---|---|---|---|---|
| Loading… | ||||
—
Signup behavior
How new subscribers are captured and which language their emails use.
Sender name
The display name on subscriber emails.
Sender email
Your own address, sent through your mail providers - must be one of their configured senders. Blank = FlowPrime's newsletter address.
Email language
Applies to confirmation/welcome emails and the hosted confirm/unsubscribe pages.
Consent & compliance
Rendered by the embed widget (v1.3+) next to a checkbox and stored on each subscriber as consent evidence.
Consent text
Terms URL
Privacy policy URL
Heads up: saving a consent text (or requiring consent) makes the widget on your live site start
rendering the checkbox as soon as visitors load the page - no site deploy needed.
Subscribe URL
POST JSON { email, source?, hp, ts } with
Authorization: Bearer <license-jwt>. Calls are accepted only from
origins on the license's domain allowlist (wildcards like *.example.com
supported; localhost is exempt for dev). The
<ff-newsletter> widget handles the JWT for you.
…
Manage authorized domains per license in
Licenses & Domains.
Server-to-server callers can use X-Api-Key with the platform key instead of a JWT.
Embed on your site
Drop this snippet into any page to start collecting subscribers.
…
Replace your-api-key with a license key for the
newsletter product. Issue keys to your authorized domains in
Licenses & Domains.
Dev-only embed (no license check)
… Built-in anti-spam:
honeypot hp field (silent drop on bots) ·
3-second submit-time check (silent drop) ·
10-request/hour-per-IP rate limit (returns 429) ·
idempotent on duplicate emails.