Accept Invitation

POST /invitations/accept

No credential

This operation is public: it authenticates by its own mechanism — a webhook signature or a channel token — rather than by a platform credential.

Request body — InvitationAccept

Field	Type		Notes
token	string	required	min length 16 max length 200
full_name	string | null	optional	max length 200
password	string | null	optional	min length 12 max length 256

Responses

Status	Description	Body
200	Successful Response	TokenPair
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/invitations/accept \
  -H "Content-Type: application/json" \
  -d '{
       "token": "string"
     }'

Response — TokenPair

Field	Type		Notes
access_token	string	required	—
refresh_token	string	required	—
token_type	string	optional	Default "bearer".
expires_in	integer	required	—
principal	PrincipalView	required	—