---
title: "OAuth authorization request (consent screen)"
method: GET
path: "/authorize"
tags: ["GET authorize"]
---

# OAuth authorization request (consent screen)

`GET /authorize`

Starts the authorization code flow and shows the consent screen when interaction is required. If the user is not signed in, they are redirected to sign-in and then returned here with the same query string. Optional parameters include PKCE (`code_challenge`, `code_challenge_method`) and `state` (recommended). Example request: `https://healthsherpa.com/oauth/authorize?client_id=YOUR_OAUTH_APPLICATION_ID&redirect_uri=YOUR_OAUTH_APPLICATION_REDIRECT_URI&response_type=code&scope=intake_form_api`

## Query parameters

- `client_id` string, required
- `redirect_uri` string, required
- `response_type` 'code', required
- `scope` string, required
- `state` string

## Response `200`

HTML consent page. Only displays when the user does not have any unrevoked access tokens. Otherwise, we'll redirect to client `redirect_uri`.

## Other responses

- `302` — Redirect to client `redirect_uri` or to login when unauthenticated.
- `429` — Too many requests to OAuth authorization endpoints. Limit is 500 requests per minute (combined across authorization-related traffic when rate limiting applies).
- `500` — Missing a parameter or parameter does not match client values, such as redirect_uri saved in HealthSherpa

---

[API](https://skmtc.net/healthsherpa/apis/health-insurance-quotes-api.md) · [All operations](https://skmtc.net/healthsherpa/apis/health-insurance-quotes-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/healthsherpa/health-insurance-quotes-api/revisions/3cbfff4e5929/schema)