Skip to main content
POST
Accept account invitation

Authorizations

Authorization
string
header
required

Use a JWT bearer token or a Veryfront API key in the Authorization header.

Body

application/json
token
string
required

Invitation acceptance token. Requires a user session; API keys are refused. Fresh acceptance requires the matching current email. Repeating acceptance returns the existing membership for the same accepting user, if that membership still exists. Unknown or revoked tokens return 404; a fresh request with a mismatched email returns 403. Expired or no longer authorized invitations return 409.

Required string length: 20 - 200

Response

Already a member; the existing membership

id
string<uuid>
required
slug
string
required
name
string
required
kind
enum<string>
required
Available options:
personal,
team
created_at
string
required
updated_at
string
required
membership
object
required

The caller's own membership in this account, including their resolved role and capabilities.