Public
Invites

Accept a team invite (verify code)

SMS-channel invites only: checks the one-time code against the invited mobile. On success the account is created if new (unusable random password, default grower — exactly like phone sign-in), the mobile is marked verified, this role is attached and accepted, any other pending invites for the number are claimed, and the standard first-party Doorkeeper token payload is returned (same shape as POST /users/phone-sessions/verify).

post/invites/{token}/accept

Request

  • Base URL: https://api.purplegrain.com/api/v1
  • URL: https://api.purplegrain.com/api/v1/invites/{token}/accept
  • Auth: none declared

Path parameters

tokenstring required

The invite token from the invite link.

Request body

codestring required

The 6-digit code from the SMS.

Response

Invite accepted — Doorkeeper access token; includes user_id.

access_tokenstring required

Opaque bearer token. Send as header Authorization: Bearer {token} on /api/v1/* routes.

token_typestring required
expires_ininteger

Lifetime of the access token in seconds.

refresh_tokenstring nullable

Present when the client and grant type allow refresh tokens.

scopestring

Granted scopes (space-separated).

user_idstring uuid nullable

Only returned by first-party JSON endpoints (/users/sign-in, /users/access-tokens), not by POST /oauth/token.

actor_idstring uuid nullable

The acting entity's id (first-party endpoints only). Equals user_id today; becomes the Organization id when a token is scoped to act for an organization.

actor_type'User' | 'Organization' nullable

Polymorphic type of actor_id (first-party endpoints only).

Example response

{
  "token_type": "Bearer"
}

Changes

No recorded changes to this operation across all 2 revisions of this API.