Accept Account Invitation

POST /api/v1/auth/invitations/accept

Access

Authentication options declared in the contract include user cookie session or bearer service token.

Authentication and permissions explains tokens, cookies, CSRF, and workspace context.

Parameters

Name	Location	Required	Type	Description and constraints
X-CSRF-Token	header	No	string	Required for unsafe requests authenticated by CookieSession; ignored for bearer clients. minimum length 32. maximum length 256

Request body

Required.

application/json — AcceptAccountInvitationBody.

Field	Type	Required	Description and constraints
token	string	Yes	minimum length 16. maximum length 256
username	string	Yes	minimum length 3. maximum length 64. pattern ^[A-Za-z0-9][A-Za-z0-9._-]*$
password	string	Yes	minimum length 12. maximum length 128

cURL request template

Set the connection variables described in Get started. Replace each additional EOI_… variable with the parameter value for this request. Prepare the body file using the request schema above. This template sends the request when run.

curl --fail-with-body --silent --show-error \
  --request POST \
  --header "Authorization: Bearer ${EOI_SERVICE_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-binary @request.json \
  "${EOI_API_BASE_URL}/auth/invitations/accept"

Contract responses

The table records responses declared by the OpenAPI contract. See Errors and status codes for the runtime error envelope and shared failures.

Status	Description	Media type	Body
200	Successful Response	application/json	UserResponse
422	Validation Error	application/json	HTTPValidationError

Operation identifier acceptAccountInvitation. Browse Authentication and sessions.