---
title: "Authorize"
method: GET
path: "/oauth/authorize"
tags: ["Authentication"]
---

# Authorize

`GET /oauth/authorize`

Create an authorized session

## Query parameters

- `response_type` 'code', required — The response type, must be 'code' for authorization code flow
- `client_id` string, required — The client identifier issued to the client during registration
- `redirect_uri` string, uri, required — The URI to redirect to after authorization is complete
- `scope` string
- `state` string — Optional value used by the client to maintain state between request and callback
- `code_challenge` string — PKCE code challenge derived from the code verifier
- `code_challenge_method` 'S256' | 'plain' — Method used to derive the code challenge, either 'S256' or 'plain'
- `flow_type` 'login' | 'signup' — If you want to use Nomos as identity provider, you can support a login or signup flow via explicitly setting this parameter. In contrast to the default, the login options skips the consent screen. The signup options allows your users to create a new customer without a subscription attached to it, and therefore register an account.

## Other responses

- `302` — Redirect to the defined redirect_uri
- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The client must authenticate itself to get the requested response.
- `402` — A higher pricing plan is required to access the resource.
- `403` — The client does not have the necessary permissions to access the resource.
- `404` — The server can't find the requested resource.
- `405` — The request method is not allowed.
- `409` — The request could not be completed due to a conflict mainly due to unique constraints.
- `422` — The request was well-formed but was unable to be followed due to semantic errors.
- `429` — The client has sent too many requests.
- `500` — The server has encountered a situation it doesn't know how to handle.

---

[API](https://skmtc.dev/nomos/apis/nomos-api.md) · [All operations](https://skmtc.dev/nomos/apis/nomos-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/nomos/nomos-api/revisions/da60ad83e92f/schema)