v1
latestOpenAPI 3.0.02026-08-04891301.4 MBInitiate a device authorization request
Starts the OAuth 2.0 Device Authorization flow for a device that cannot perform browser-based redirects. Returns a device_code (used by the device to poll for a token) and a user_code (shown to the user to enter at the verification_uri).
This endpoint requires a publishable API key; secret keys are rejected with a 403. Third-party OAuth must be enabled on the app; if it is not, the response returns error: "third_party_oauth_not_enabled" with a 403.
The endpoint is rate-limited to 10 requests per IP per minute. Excess requests receive a 429 response. The returned codes expire after expires_in seconds; once expired, a new authorization request must be initiated.
post/oauth/device/authorize
Request body
Example request
{
"client": "string",
"scope": "string"
}Response
Successful response
Example response
{
"device_code": "string",
"expires_in": 1800,
"interval": 5,
"user_code": "WDJB-MJHT",
"verification_uri": "https://example.com",
"verification_uri_complete": "string"
}