GET/.well-known/oauth-authorization-server
Get authorization server metadata
get_oauth_server_metadata
OAuth 2.0 authorization server metadata (RFC 8414): issuer is the main address of the installation, the consent page is on the main address, and the token and revocation endpoints are on the API address when one is set. Lists the supported grant types, PKCE methods, client authentication methods and scopes. Added in 1.62.0.
Authentication
No credentials needed.
Responses
200OK
Response headers
RateLimit-PolicyLimits in effect, in the format of the IETF draft
draft-ietf-httpapi-ratelimit-headers: comma-separated items"<name>";q=<quota>;w=<window in seconds>.keyis the request rate of the API key (the quota is the burst, the window is the time to refill it fully; for a session it isuser, without credentialsip);minute,dayandmonthare the organization's quotas for the calendar minute, day and month in UTC.RateLimitWhat is left of each limit in
RateLimit-Policy:"<name>";r=<remaining>;t=<seconds until reset>.X-RateLimit-LimitLimit of the strictest entry in
RateLimit-Policy(the one with the fewest requests left).X-RateLimit-RemainingRequests left under the strictest limit.
X-RateLimit-ResetSeconds until the strictest limit resets.
application/json
issuerstringrequiredauthorization_endpointstringrequiredtoken_endpointstringrequiredrevocation_endpointstringrequiredresponse_types_supportedarray of stringrequiredgrant_types_supportedarray of stringrequiredcode_challenge_methods_supportedarray of stringrequiredtoken_endpoint_auth_methods_supportedarray of stringrequiredrevocation_endpoint_auth_methods_supportedarray of stringrequiredscopes_supportedarray of stringrequiredservice_documentationstring
Rate limits
Responses carry the RateLimit and RateLimit-Policy headers and the earlier X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. A 429 response has Retry-After in seconds: wait and retry.