GET /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 GET https://api.zinndigital.com/v1/notification-connections/confirm?token=<token>

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

Public and unauthenticated: the person clicking is very often an accountant or a colleague with no account here, and a confirmation behind a login wall cannot be completed by the one person it is addressed to. GET only DESCRIBES. Mail clients and scanners fetch links before a human sees them, so a confirming GET would be auto-clicked by the recipient's own mail infrastructure and double opt-in would silently become single opt-in. An unknown, expired or already-used token all answer `valid: false` identically - the endpoint must not become an oracle for which addresses an organisation has pending.

Parameters

Response