E-File Magic

Discovery

Discover the authorization server

Return authorization-server endpoint URLs, grants, S256 PKCE, client authentication methods, supported scopes and optional agent-registration metadata.

GET
/.well-known/oauth-authorization-server
Authentication
No access token required
Required scopes
See authentication requirements
Idempotency key
Not required

Successful outcomes: ok.

Example · HTTP 200
{
  "issuer": "https://<issuer>",
  "authorization_endpoint": "https://<issuer>/oauth/authorize",
  "pushed_authorization_request_endpoint": "https://<issuer>/oauth/par",
  "token_endpoint": "https://<issuer>/oauth/token",
  "revocation_endpoint": "https://<issuer>/oauth/revoke",
  "jwks_uri": "https://<issuer>/oauth/jwks.json",
  "response_types_supported": [
    "code"
  ],
  "grant_types_supported": [
    "authorization_code",
    "refresh_token",
    "client_credentials"
  ],
  "code_challenge_methods_supported": [
    "S256"
  ],
  "token_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "private_key_jwt"
  ],
  "require_pushed_authorization_requests": true
}

Confidential external API configuration; optional MCP metadata varies with availability.