cs...) alongside it. The client secret is safe to expose to the frontend — it authorizes a single user to complete one specific session.
For the end-to-end integration pattern (create session on backend, pass URL to frontend), see Authentication & Keys.
Properties
Example
clientSecret
Refreshing an expired secret
If a user doesn’t complete verification within two hours, mint a new client secret for the same session:Security properties
- Single-session: each secret authorizes exactly one session. Cannot be reused or used to create new sessions.
- Short-lived: expires two hours after creation.
- URL-safe: designed for embedding in redirect URLs, iframes, and WebViews.
- Read-only: cannot read or modify sessions other than its own.
API keys must stay on the server. Client secrets are the only credential that should reach the browser.
Next Steps
Authentication & Keys
Full integration pattern and security rules.
Create Session
The endpoint that returns a client secret.
Create Client Secret
Mint a new secret for an existing session.