public

POST /v1/public/signup/complete

Choose the password and finish the sign-up.

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/complete \
  -H "Content-Type: application/json" \
  -d '{ "token": <string>, "password": <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). A valid, unused link is claimed atomically, the account is created with its address already verified, and a single-use sign-in URL (about two minutes) is returned that lands the person in the dashboard. 409 with details[0].code EXPIRED, USED or INVALID for a link that cannot be used; 409 ACCOUNT_EXISTS when the address already has a password; 422 with details[0].field = password when the password policy refuses it (at least 12 characters, not the username, not the address).

Request body

NameTypeRequiredWhat it is
tokenstringYes—
passwordstringYes—

Response

NameTypeRequiredWhat it is
sign_in_urlstringYesA single-use sign-in link, valid about two minutes.

Errors this endpoint can return

409 · 422 · 429 · 503