public
POST /v1/public/signup/verify
Read what state a sign-up link is 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/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
| Name | Type | Required | What it is |
|---|---|---|---|
token | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
state | string<valid, expired, used, invalid, exists> | Yes | valid shows the password form; expired offers a new link; used and exists offer sign-in; invalid offers starting again. |
email | string | Yes | The address the link was sent to, or empty for an invalid token. |
intent | string | Yes | — |
plan | string | Yes | — |
trial | string | Yes | — |
Errors this endpoint can return
422 · 429 · 503