POST /v1/notification-connections/confirm

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/notification-connections/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 double opt-in click. Until it happens nothing is routed to the address - a billing notification carries an amount, a legal address and a VAT identity, so a mistyped address is a disclosure and the person who mistyped it is the one who cannot notice. Single-use and expiring.

Request body

Response