oauth
Sign-in for AI apps: authorization, consent and connected apps
10 operations
- GET/.well-known/oauth-authorization-server/oauthMetadata for this deployment's OAuth authorization server
- GET/.well-known/oauth-protected-resource/mcpWhich authorization server protects the MCP service, and what it can grant
- POST/oauth/authorizationsOpen a consent request from the consent page, for the signed-in person
- GET/oauth/authorizations/{authorization_id}A consent request waiting for the signed-in person's answer
- POST/oauth/authorizations/{authorization_id}/approveAllow an app the scopes the person chose, and send the browser back to it
- POST/oauth/authorizations/{authorization_id}/denyRefuse to connect an app, and send the browser back to it
- GET/oauth/authorizeStart connecting an app: checks the request and sends the browser to the consent page
- POST/oauth/tokenExchange an authorization code, or a refresh token, for an access token
- GET/user/oauth-grantsThe apps the authenticated user has connected through sign-in
- DEL/user/oauth-grants/{oauth_grant_id}Disconnect an app: its access ends at once