> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rails.wayex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Accept a team invitation

> Uses a valid invitation token to set the first administrator’s permanent console password and activate the account the invitation was issued to.

## What this endpoint does

Uses a valid invitation token to set the first administrator’s permanent console password and activate the account the invitation was issued to.

## When to use it

Submit it once after the recipient has reviewed the invitation and chosen a password.

## Before you call

Pass a valid, unused invitation token and a request that meets the credential requirements. No API key is required.

## Money and balance effect

This changes a resource or configuration but does not directly reserve, debit, credit, or settle wallet money.

## States and completion

A successful response consumes the token. Expired or previously used tokens must be replaced by a new invitation.

## Safe retries

Do not submit concurrently. If the response is lost, validate the token again before retrying; a consumed token means activation already completed.

Read [Team and roles](/console/team-roles) for the complete workflow.


## OpenAPI

````yaml /api-reference/openapi.json post /v1/invite/{token}/complete
openapi: 3.0.0
info:
  title: Wayex API
  description: >-
    Wayex APIs for direct customer payment routes and isolated, prefunded
    Treasury accounts. Each API key is bound to one tenant account and its own
    wallet, settings, webhooks, and reporting.
  version: 1.0.0
  contact: {}
servers:
  - url: https://api.sandbox.rails.wayex.com
    description: Sandbox — fully simulated providers, no real funds move
  - url: https://api.rails.wayex.com
    description: Production — live rails, real funds move
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Treasury
    description: >-
      Prefunded AUD and stablecoin wallets for one isolated tenant account.
      Fund, pay, convert, withdraw, track, and reconcile without selecting
      another account.
  - name: Customers
    description: >-
      Onboard end customers, run verification, and manage each customer's
      entitlements.
  - name: Payment routes
    description: >-
      Standing deposit instructions per customer. When a customer funds a route,
      Wayex auto-converts at the live rate and pays out/sends — no quote, no
      lock.
  - name: Transfers
    description: >-
      Read the conversion records produced when customers fund payment routes —
      the live activity feed and per-conversion lifecycle timeline.
  - name: Rates
    description: >-
      The live indicative AUD↔stablecoin rate right now — the all-in rate Wayex
      quotes. Indicative only; the binding price is struck when a route's funds
      land.
  - name: Revenue
    description: Your developer-fee revenue over time.
  - name: Invoices
    description: >-
      Your monthly invoices — Wayex platform fees due, net of your accrued
      developer-fee credit.
  - name: Webhooks
    description: Subscribe to HMAC-signed event webhooks and inspect deliveries.
  - name: API keys
    description: Create, list, and rotate API keys for programmatic access.
  - name: Fees
    description: >-
      Configure your developer fee — the markup withheld from each conversion
      and credited against your monthly invoice.
  - name: Invitations
    description: Accept a team invitation and activate your account.
  - name: Team
    description: Manage your own team — list members and send console invitations.
  - name: Notification settings
    description: >-
      Manage whether Wayex sends customer-facing notification emails on your
      behalf.
paths:
  /v1/invite/{token}/complete:
    post:
      tags:
        - Invitations
      summary: Accept a team invitation
      description: >-
        Uses a valid invitation token to set the first administrator’s permanent
        console password and activate the account the invitation was issued to.
        Submit it once after the recipient has reviewed the invitation and
        chosen a password.
      operationId: InviteController2_complete_v1
      parameters:
        - name: token
          required: true
          in: path
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CompleteInviteDto'
      responses:
        '201':
          description: Account activated; includes the login URL.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                  loginUrl:
                    type: string
                    format: uri
                required:
                  - ok
                  - loginUrl
        '400':
          description: Validation failed (e.g. password too weak).
        '404':
          description: The token is unknown, expired, or already used.
      security: []
components:
  schemas:
    CompleteInviteDto:
      type: object
      properties:
        password:
          type: string
          minLength: 12
          maxLength: 256
      required:
        - password
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: Wayex API key
      description: 'Send the same Wayex API key as `Authorization: Bearer <key>`.'
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: >-
        A Wayex API key. Use a secret key (`sk_…`) — it works on every endpoint.
        Publishable keys (`pk_…`) are accepted only on a small set of read
        endpoints: `GET /v1/rates`, `GET /v1/activity`, `GET
        /v1/developer-fees`, `GET /v1/revenue`, and `GET /v1/reports/revenue`.

````