public

POST `/v1/public/news/subscribe`

Ask for Zinn® news by e-mail (double opt-in; sends one confirmation e-mail).

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/public/news/subscribe \
  -H "Content-Type: application/json" \
  -d '{ "email": <string>, "wording_version": <string<news-v1>> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

s1014 DOUBLEOPTIN, docs/1052 §7j. Records the consent request (time, IP, user agent, page, the wording version shown, language) and e-mails ONE confirmation link that works for 7 days. ⛔ No oracle: 202 with the same body for a new, pending, confirmed, throttled or suppressed address. Human check (newsletter surface), a per-client budget, a honeypot (website_confirm) and a per-address resend limit. 422 for an unknown source or wording.

Request body

Name	Type	Required	What it is
`email`	`string`	Yes	—
`locale`	`string`	No	—
`source`	`string<footer, newsletter_page>`	No	—
`source_page`	`string`	No	—
`wording_version`	`string<news-v1>`	Yes	—
`turnstile_token`	`string`	No	—
`website_confirm`	`string`	No	The honeypot - a person leaves it empty.

Response

Name	Type	Required	What it is
`status`	`string<check_your_inbox>`	Yes	—

Errors this endpoint can return

422 · 429

POST /v1/public/news/subscribe