---
title: "Authorize Consent"
method: GET
path: "/oauth2/authorize"
tags: ["oauth2"]
---

# Authorize Consent

`GET /oauth2/authorize`

Human-facing consent screen. The external app sends the user here (this is
the `authorize_url` the connecting app redirects to); on Allow the page calls
POST /oauth2/authorize and forwards the browser to the returned redirect_url.

If the user isn't signed in, the page runs an interactive Auth0 login whose
callback returns to THIS url with `?code=...` (the original OAuth params are
carried client-side in Auth0 `appState`). In that callback case we render the
shell and let the JS restore the params — so client_id/redirect_uri are optional.

## Query parameters

- `client_id` string, nullable
- `redirect_uri` string, nullable
- `scope` string, nullable
- `state` string, nullable
- `response_type` string
- `code` string, nullable

## Response `200`

Successful Response

## Other responses

- `422` — Validation Error

---

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