The second step of the device code flow. Call this repeatedly after showing the user code or QR code.
While the user hasn’t confirmed yet, you’ll get { status: "pending" } — just keep polling.
Once they approve, the response changes to { refreshToken, publicId, expiresAt }.
Store the refreshToken securely — it’s your long-lived credential for all identity-tier calls.
Recommended interval: every 5 seconds. Stop polling when you receive a refreshToken or a 401 error.
Documentation Index
Fetch the complete documentation index at: https://docs.discovr.media/llms.txt
Use this file to discover all available pages before exploring further.
The device code obtained from the request device code endpoint
Poll result. Two possible shapes:
refreshToken, publicId, expiresAt.status: "pending". Keep polling.Returned when the user has confirmed the device code. Store the refreshToken securely — it's your long-lived credential.
Call POST /auth/session-token with a profileId to get a session token and start browsing.
Your long-lived credential (valid for 90 days). Use it as the bearer for identity-tier endpoints and to mint session tokens. Keep it secure — treat it like a password and never put it in URLs.
"rt_a1b2c3d4e5f6..."
An identifier for this sign-in session. You can use it to revoke access later via DELETE /auth/sessions/{publicId}.
"MqXYz12abc"
When the refresh token expires, as a Unix timestamp (seconds).
1733088000