Skip to main content
POST
Verify an invitation code
No signed-in session is required. Endpoint-specific tokens, setup secrets or challenges may still be required. Checks the code and binds the returned verificationToken to the exact invited name. Supply that proof when accepting the invitation. Request conventions · API keys · MCP connections

Body

application/json
token
string
required
Pattern: ^[A-Za-z0-9_-]{43}$
name
string
required
Required string length: 1 - 120
code
string
required
Pattern: ^\d{6}$

Response

Successful response. Examples are illustrative; field values vary by record.

verificationToken
string