v1
latestOpenAPI 3.1.02026-08-066984441.1 MBDynamically registers a new OAuth 2.0 client according to RFC 7591.
<Check title="Required Permissions" icon="key">Allows unauthenticated access.</Check>
Headers
Bearer authentication
Request body
Response
Created
Array of redirection URI strings for use in redirect-based flows.
Human-readable name of the client to be presented to the end-user.
Requested authentication method for the token endpoint.
Array of OAuth 2.0 grant types that the client will use.
Array of OAuth 2.0 response types that the client will use.
Space-delimited list of OAuth 2.0 scope values.
Kind of the application.
Array of e-mail addresses of people responsible for this client.
URL that references a logo for the client application.
URL of the home page of the client application.
URL that the client provides to the end-user with information about how the client uses their data.
URL that the client provides to the end-user to read about the client's terms of service.
A unique identifier string (e.g., a Universally Unique Identifier (UUID)) assigned by the client developer.
A version identifier string for the client software identified by software_id.
OAuth 2.0 client identifier string.
OAuth 2.0 client secret string. Only provided for confidential clients.
Time at which the client secret will expire (0 if it doesn't expire).
Time at which the client identifier was issued as seconds since Unix epoch.