Skip to main content
Version: Developer

Issue fresh browser login credentials for a session

POST 
/api/session/sessions/:session_id/browser-logins

Mints a new login-session JWT for the session's owner and returns it with the browser connect_url. An authenticated user may call it for their own session (someone else's is 404); an API key needs USERS_AUTH_SESSION. Every call persists a new revocable session token. Status polling never carries credentials; this is the explicit credential-producing operation.

Request​

Responses​

Successful Response

Response Headers
    Cache-Control

    Always no-store.

    Pragma

    Always no-cache.