pricklymails-com · Schema

AuthorizationServerMetadataResponse

`GET /.well-known/oauth-authorization-server` response body (RFC 8414 subset).

Email VerificationAPISaaSData ValidationEU-hosted

Properties

Name Type Description
authorization_endpoint string The authorization endpoint URL.
authorization_response_iss_parameter_supported boolean `true`: every authorization response (success and `access_denied`) carries `iss` (RFC 9207), letting a client that talks to more than one authorization server verify which one a given callback actuall
code_challenge_methods_supported array Supported PKCE code challenge methods (RFC 7636).
grant_types_supported array Supported OAuth `grant_type` values.
issuer string The authorization server's issuer identifier: its own public base URL.
registration_endpoint string The dynamic client registration endpoint URL (RFC 7591).
response_types_supported array Supported OAuth `response_type` values.
scopes_supported array Scopes this server may grant to a client.
token_endpoint string The token endpoint URL.
token_endpoint_auth_methods_supported array Supported token endpoint authentication methods. `"none"`: every registered client is public and authenticates via PKCE, not a client secret.
View JSON Schema on GitHub

JSON Schema

pricklymails-com-authorization-server-metadata-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/pricklymails-com/json-schema/pricklymails-com-authorization-server-metadata-response-schema.json",
  "title": "AuthorizationServerMetadataResponse",
  "description": "`GET /.well-known/oauth-authorization-server` response body (RFC 8414 subset).",
  "x-generated": "2026-10-31",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/pricklymails-com-openapi.json#/components/schemas/AuthorizationServerMetadataResponse",
  "type": "object",
  "required": [
    "issuer",
    "authorization_endpoint",
    "token_endpoint",
    "registration_endpoint",
    "scopes_supported",
    "response_types_supported",
    "grant_types_supported",
    "code_challenge_methods_supported",
    "token_endpoint_auth_methods_supported",
    "authorization_response_iss_parameter_supported"
  ],
  "properties": {
    "authorization_endpoint": {
      "type": "string",
      "description": "The authorization endpoint URL."
    },
    "authorization_response_iss_parameter_supported": {
      "type": "boolean",
      "description": "`true`: every authorization response (success and `access_denied`) carries `iss` (RFC 9207), letting a client\nthat talks to more than one authorization server verify which one a given callback actually came from."
    },
    "code_challenge_methods_supported": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Supported PKCE code challenge methods (RFC 7636)."
    },
    "grant_types_supported": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Supported OAuth `grant_type` values."
    },
    "issuer": {
      "type": "string",
      "description": "The authorization server's issuer identifier: its own public base URL."
    },
    "registration_endpoint": {
      "type": "string",
      "description": "The dynamic client registration endpoint URL (RFC 7591)."
    },
    "response_types_supported": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Supported OAuth `response_type` values."
    },
    "scopes_supported": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Scopes this server may grant to a client."
    },
    "token_endpoint": {
      "type": "string",
      "description": "The token endpoint URL."
    },
    "token_endpoint_auth_methods_supported": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Supported token endpoint authentication methods.\n`\"none\"`: every registered client is public and authenticates via PKCE, not a client secret."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/pricklymails-com-authorization-server-metadata-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.