Skip to main content
POST
Confirm account email
No signed-in session is required. Endpoint-specific tokens, setup secrets or challenges may still be required. Consumes the id and token from a valid verification link. Request conventions · API keys · MCP connections

Body

application/json
id
string<uuid>
required
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
token
string
required
Pattern: ^[A-Za-z0-9_-]{43}$

Response

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

ok
boolean