Skip to main content
POST
Verify a recent session
A signed-in human session is required. API keys and MCP bearer credentials cannot replace that session. Reauthenticates the current session. A passkey-protected account receives a second-factor challenge before recent authentication is renewed. Request conventions · API keys · MCP connections

Authorizations

posted_session
string
cookie
required

Signed-in human browser session; mutation requests also need the exact UI Origin

Headers

Origin
string<uri>
required

The exact configured Posted UI origin. Required for browser mutations carrying session cookies.

Body

application/json
password
string
required
Required string length: 1 - 1024

Response

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

ok
boolean