---
title: "OAuth 2.0 Authorization Endpoint"
method: GET
path: "/restapi/oauth/authorize"
tags: ["OAuth 2.0 / OpenID Connect"]
---

# OAuth 2.0 Authorization Endpoint

`GET /restapi/oauth/authorize`

Performs Authentication of the End-User by sending the User Agent to the Authorization Server's
Authorization Endpoint for Authentication and Authorization,
using request parameters defined by OAuth 2.0 [RFC-6749](https://datatracker.ietf.org/doc/html/rfc6749#section-3.1)
and additional parameters and parameter values defined by
[OpenID Connect Core 1.0](https://openid.net/specs/openid-connect-core-1_0.html#AuthorizationEndpoint).

This is the version that uses HTTP `GET` method.

## Query parameters

- `client_id` string, required
- `response_type` 'code', required
- `redirect_uri` string, uri
- `state` string
- `scope` string
- `display` 'page' | 'popup' | 'touch' | 'mobile' — Specifies how the Authorization Server displays the authentication and consent user interface pages to the End-User.
- `prompt` string
- `ui_locales` string
- `localeId` string
- `code_challenge` string
- `code_challenge_method` 'plain' | 'S256' — The code challenge method as defined by the PKCE specification - [RFC-7636 "Proof Key for Code Exchange by OAuth Public Clients"](https://datatracker.ietf.org/doc/html/rfc7636)
- `nonce` string
- `ui_options` string
- `login_hint` string
- `brand_id` string

## Other responses

- `302` — Successful response, HTTP redirect to login form
- `400` — The response with **HTTP 400 "Bad request"** status used in some OAuth / OpenID Connect endpoints.

---

[API](https://skmtc.net/ringcentral/apis/ringcentral-api.md) · [All operations](https://skmtc.net/ringcentral/apis/ringcentral-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringcentral/ringcentral-api/revisions/8d602198ec97/schema)