Returns a user code, device code, activation link, and QR code activation link
Obtained during either manual client registration or through the Dynamic Client Registration API. It identifies the client and must match the value preregistered in Okta.
Repeat the parameter to authorize multiple resource servers (?resource=https://api.example.com&resource=https://other.example.com, for example). Each access token is issued for a single resource server, so its aud claim is a single value. If you specify more than one resource server, use the resource parameter in the /token request to select one. Values that aren't audiences of the authorization server are ignored.
Note: Multiple audiences for custom authorization servers is a self-service Early Access (EA) feature. See Manage Early Access and Beta features to enable the feature.
- https://subdomain.okta.comhttps://subdomain.okta.com/oauth2/{authorizationServerId}/v1/device/authorize
curl -i -X POST \
'https://subdomain.okta.com/oauth2/{authorizationServerId}/v1/device/authorize' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d client_id=string \
-d resource=http://example.com \
-d scope=stringBased on the type of token and whether it's active, the returned JSON contains a different set of information.
The minimum amount of time in seconds that the client should wait between polling requests to the token endpoint
{ "user_code": "RGTCFDTL", "device_code": "5cbeb234-7e00-4ff7-9aa2-b1a4558a75d2", "interval": 5, "verification_uri_complete": "https://{yourOktaDomain}/activate?user_code=RGTCFDTL", "verification_uri": "https://{yourOktaDomain}/activate", "expires_in": 600 }