Skip to main content
POST

Overview

Initiates the device authorization flow for CLI tools and AI agents that cannot open a browser directly. Returns a user code that must be entered at the verification URL to authorize the device. Flow:
  1. Agent calls this endpoint to get a device_code and user_code
  2. User opens verification_url in their browser and enters the user_code
  3. Agent polls Poll Device Token with the device_code
  4. Once authorized, the poll returns an API key
No authentication required.

Body Parameters

string
default:"Unknown Client"
Name of the client requesting authorization (shown to user during approval)
string
An organization id or slug. The minted key then belongs to that organization and acts for it without a danube-org-id header; the user who authorizes the code must be a member, or the authorization is refused with 403. 404 when no organization matches. This is what danube login --org sends.

Response

string
Opaque code for the agent to use when polling for the token
string
Human-readable code in XXXX-XXXX format for the user to enter
string
URL where the user should enter the code
integer
Seconds until the device code expires (600 = 10 minutes)
integer
Minimum seconds between poll requests (5)
string
The organization the key will belong to, when the request named one; otherwise null
string
That organization’s display name, for showing the user what they are authorizing

Example

Device Auth Flow