public

POST `/v1/public/news/confirm`

Confirm a Zinn® news subscription with the e-mailed token (double opt-in).

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/confirm \
  -H "Content-Type: application/json" \
  -d '{ "token": <string> }'

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

The page the e-mail's link opens POSTs the token here (a link's GET never confirms, so a mail scanner cannot). Only the NEWEST link confirms. 422 with refusal refusal.news.linkExpired (older than 7 days) or refusal.news.linkInvalid.

Request body

Name	Type	Required	What it is
`token`	`string`	Yes	—

Response

Name	Type	Required	What it is
`status`	`string<confirmed, already>`	Yes	—

Errors this endpoint can return

422 · 429

POST /v1/public/news/confirm