public

POST /v1/public/signup/verify

Read what state a sign-up link is in.

All public endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

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/signup/verify \
  -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

docs/576 §9. Unauthenticated (no permission: the token is the credential), throttled per trusted client (signup_token, 60/hour). POST, not GET ?token=, so the token stays out of access logs and referrers. Reading never consumes the link.

Request body

NameTypeRequiredWhat it is
tokenstringYes—

Response

NameTypeRequiredWhat it is
statestring<valid, expired, used, invalid, exists>Yesvalid shows the password form; expired offers a new link; used and exists offer sign-in; invalid offers starting again.
emailstringYesThe address the link was sent to, or empty for an invalid token.
intentstringYes—
planstringYes—
trialstringYes—

Errors this endpoint can return

422 · 429 · 503