Skip to main content
Session tokens are best for frontend applications where you need to authenticate users in the browser. Sessions are created by your backend using the project API key, then passed to the client. Sessions expire after a period of inactivity but can be refreshed.

Flow

1

Backend creates a session

Your server calls the session endpoint using the project API key.
2

Pass token to client

Return the session token to the frontend (e.g., via HTTP-only cookie or secure storage).
3

Client makes requests

The frontend sends the token in the Authorization header with each request.

Step 1: Create a session

This is called from your backend using the project API key.

Step 2: Use the session token

Pass the token from the response as a Bearer token in your client requests.

Refresh a session

Expire the existing session and issue a new one. This extends the user’s authenticated session without requiring them to re-authenticate.

Expire a session

Manually expire a specific session or all sessions for an account.

Available routes

All routes under /api/v1/account/* and /api/v1/wallet/* accept session tokens.