---
title: "The OAuth 2.0 Device Authorize Endpoint"
method: POST
path: "/oauth2/device/auth"
tags: ["oAuth2"]
---

# The OAuth 2.0 Device Authorize Endpoint

`POST /oauth2/device/auth`

This endpoint is not documented here because you should never use your own implementation to perform OAuth2 flows.
OAuth2 is a very popular protocol and a library for your programming language will exist.

To learn more about this flow please refer to the specification: https://tools.ietf.org/html/rfc8628

## Response `200`

deviceAuthorization

- DeviceAuthorization — # Ory's OAuth 2.0 Device Authorization API
  - `device_code` string — The device verification code.
  - `expires_in` integer — The lifetime in seconds of the "device_code" and "user_code".
  - `interval` integer — The minimum amount of time in seconds that the client SHOULD wait between polling requests to the token endpoint. If no value is provided, clients MUST use 5 as the default.
  - `user_code` string — The end-user verification code.
  - `verification_uri` string — The end-user verification URI on the authorization server. The URI should be short and easy to remember as end users will be asked to manually type it into their user agent.
  - `verification_uri_complete` string — A verification URI that includes the "user_code" (or other information with the same function as the "user_code"), which is designed for non-textual transmission.

## Other responses

- `default` — errorOAuth2

---

[API](https://skmtc.net/ory/apis/ory-hydra-api.md) · [All operations](https://skmtc.net/ory/apis/ory-hydra-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ory/ory-hydra-api/versions/ab053e716585/schema)