Get OAuth Client Details
Authentication
Bearer token authentication using JWT tokens from Ory Kratos/Hydra
Path parameters
Response
Human-readable name for the OAuth client.
List of authorized redirect URIs for OAuth flows requiring user interaction. Required for authorization code and implicit flows. Must be exact matches when used. Must use HTTPS in production (except for localhost).
OAuth 2.0 grant types enabled for this client.
- client_credentials: For server-to-server API access
- authorization_code: For web and mobile apps
- refresh_token: For maintaining long-term access
- implicit: Legacy flow, not recommended for new applications
Secret key used to authenticate the client. Only shown once upon creation. Must be stored securely. Required for confidential clients (e.g., server applications).
Authentication method enabled for the client:
- client_secret_basic: Client ID and secret sent in HTTP headers
- client_secret_post: Client ID and secret sent in request body
- none: No client authentication (required for public clients using PKCE)
Whether PKCE (Proof Key for Code Exchange) is required for this client. When enabled, authorization code flows must include code_challenge and code_verifier. Recommended for public clients (mobile apps, SPAs) and enhances security for all clients.
PKCE code challenge method when PKCE is enabled.
- S256: SHA256 hash of code verifier (recommended and secure)
- plain: Plain text code verifier (not recommended, only for testing)
