Subscribe an endpoint to receive captured leads
Register a public HTTPS URL to receive lead.created deliveries (a lead
captured on one of your Mailr landing pages). Only landing-page leads fan
out here — CRM-synced leads (see POST /api/v1/tracking/lead) never do, to
avoid an echo loop.
The response returns a signing_secret exactly once, at creation.
Store it: every delivery to a secret-bearing subscription is HMAC-signed
(see the lead.created webhook below). Re-subscribing the same URL is
idempotent — it returns the existing row’s id with
signing_secret: null (secrets are never re-disclosed and never
silently rotated, so a re-subscribe can’t break a receiver mid-flight
and a compromised API key can’t recover live secrets). Lost the secret?
POST /api/v1/webhooks/rotate mints a new one and returns it once. A
subscription created before signing shipped is delivered unsigned;
delete and re-subscribe (or rotate) to upgrade it.
The URL is SSRF-guarded at registration (public https only; hostname must resolve to public addresses) and again at delivery time.
Authorizations
Organization-scoped Mailr API key. Header: Authorization: Bearer ak_….
Body
Response
Subscribed (or already subscribed). Note this is 200, not 201, on both create and idempotent re-subscribe.