Validate Invite Token Post
const url = 'https://example.com/auth/invites/validate';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"token":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/auth/invites/validate \ --header 'Content-Type: application/json' \ --data '{ "token": "example" }'Check whether an invite token is still usable, without consuming it.
Public, no auth required — lets AcceptInvitePage show an error state immediately for a revoked/expired/already-redeemed link instead of a form that would only fail at submit. The token travels in the body, not the URL.
Request Bodyrequired
Section titled “Request Bodyrequired”Body of the POST token-validity checks: the token stays out of the URL and so out of access logs, browser history and Referer headers.
object
Example generated
{ "token": "example"}Responses
Section titled “Responses”Successful Response
Response for a public, side-effect-free “is this token still usable” check — lets a link-landing page (reset-password, accept-invite) show an error state immediately instead of rendering a form that is doomed to fail at submit. Never reveals why a token is invalid (unknown vs expired vs already used vs revoked) — that distinction isn’t needed by the caller and would leak more than the caller asked for.
object
Example generated
{ "valid": true}Validation Error
object
object
object
Example generated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example", "input": "example", "ctx": {} } ]}