curl --request GET \
--url https://api.archera.ai/.well-known/oauth-authorization-server \
--header 'x-api-key: <api-key>'{
"issuer": "<string>",
"authorization_endpoint": "<string>",
"token_endpoint": "<string>",
"jwks_uri": "<string>",
"response_types_supported": [
"<string>"
],
"grant_types_supported": [
"<string>"
],
"code_challenge_methods_supported": [
"<string>"
],
"token_endpoint_auth_methods_supported": [
"<string>"
],
"scopes_supported": [
"<string>"
],
"service_documentation": "<string>"
}Returns OAuth 2.0 Authorization Server Metadata as specified in RFC 8414. This endpoint provides automatic discovery of the authorization server’s configuration, including supported endpoints, grant types, response types, PKCE methods, and available scopes. OAuth client libraries can use this endpoint to automatically configure themselves without manual endpoint configuration. No authentication is required as this is a public discovery endpoint.
curl --request GET \
--url https://api.archera.ai/.well-known/oauth-authorization-server \
--header 'x-api-key: <api-key>'{
"issuer": "<string>",
"authorization_endpoint": "<string>",
"token_endpoint": "<string>",
"jwks_uri": "<string>",
"response_types_supported": [
"<string>"
],
"grant_types_supported": [
"<string>"
],
"code_challenge_methods_supported": [
"<string>"
],
"token_endpoint_auth_methods_supported": [
"<string>"
],
"scopes_supported": [
"<string>"
],
"service_documentation": "<string>"
}API key for authentication. Get your key from User Settings > API Access in the Archera platform.
OK
The authorization server's issuer identifier URL
URL of the OAuth 2.0 authorization endpoint
URL of the OAuth 2.0 token endpoint
URL of the JSON Web Key Set document
OAuth 2.0 response_type values supported
OAuth 2.0 grant type values supported
PKCE code challenge methods supported
Client authentication methods supported at token endpoint
OAuth 2.0 scope values supported
URL of service documentation for developers
Was this page helpful?