/v3/auth/token

Dashboard session only. Exchange a refresh token for a new short-lived access token (Bearer JWT) via Supabase. Use this when you are acting as a logged-in dashboard user—not for machine integrations.

For OAuth2 client credentials (server-to-server, no refresh token), use POST /v3/oauth/token instead.

Refresh tokens typically come from the Supabase session after sign-in. Owners may also call POST /v3/auth/generateRefreshToken (authenticated) to mint a long-lived refresh token for integrations. Access tokens expire in about one hour.

Headers: Content-Type: application/json

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

Supabase session refresh token from dashboard login, or a long-lived refresh JWT from POST /v3/auth/generateRefreshToken (company owners only).

Responses

400

Invalid request body or missing refresh_token.

401

Unauthorized - invalid or expired refresh token.

403

Forbidden - insufficient permissions.

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json