Share links
“Here is how the receipt renders on this branch”, posted into the pull request. A public link to one message, minted from the pipeline.
Create a share link
POST /api/v1/emails/{email_id}/shares Scope: shares:create Idempotency-Key: <recommended> { "expires_in": "7d", "mode": "preview" } Response, 201: { "id": "s2h7k9m4p1x6c8v3", "url": "https://app.mailclutch.com/share/…", "mode": "preview", "expires_at": "2026-09-09T09:14:22.000000Z" }
| Field | Accepts |
|---|---|
expires_in | 1h, 24h, 7d (default), 30d or never |
mode | preview (default): the rendered message, for a stakeholder reviewing copy. dev: adds headers, source and analysis, for another developer |
Anyone with the link can open it; no account is needed. There is no branding parameter: white label is chosen in the app, not switched by a script. A link created here is unbranded, and issued on your own domain, when the organization's policy is Always on, or On by default with Also for the API and agents ticked — see White label. The link is listed with the email's other shares in the app, where it can be revoked at any time. Sensitive messages are better shared from the app, where a password can be set.