---
title: "Authorization server metadata (RFC 8414)"
method: GET
path: "/.well-known/oauth-authorization-server"
tags: ["OAuth"]
---

# Authorization server metadata (RFC 8414)

`GET /.well-known/oauth-authorization-server`

## Request

- Base URL: `https://api.infolang.ai`
- URL: `https://api.infolang.ai/.well-known/oauth-authorization-server`
- Auth: none declared

The endpoint map plus the supported grant types, response types and PKCE methods. `code_challenge_methods_supported` is `["S256"]` only — `plain` is removed in OAuth 2.1 and is CHECK-constrained out of the authorization-code table, so advertising it would be a claim the schema then refuses to honor. Public — no credential. That is not an oversight: a client cannot authenticate before it has a token, which is the entire purpose of this surface.

## Response `200`

Authorization server metadata

- object
  - `issuer` string, required
  - `authorization_endpoint` string, required
  - `token_endpoint` string, required
  - `registration_endpoint` string, required
  - `device_authorization_endpoint` string, required
  - `scopes_supported` string[], required
  - `response_types_supported` string[], required
  - `grant_types_supported` string[], required
  - `code_challenge_methods_supported` string[], required
  - `token_endpoint_auth_methods_supported` string[], required

---

[API](https://skmtc.dev/infolang/apis/infolang-api.md) · [All operations](https://skmtc.dev/infolang/apis/infolang-api/llms.txt) · [OpenAPI document](https://skmtc.dev/infolang/apis/infolang-api/revisions/d04bf6de72c8?raw)