Skip to main content

Create a new OAuth2 client​

Create a new client ID/secret pair that can be used with the client credentials grant type. A valid SlashID organization ID and API key must be used to authenticate and authorize the request. The client credentials can be configured.

SlashID currently only supports the OAuth 2.0 client credentials grant, therefore we enforce that the grant_types field must be ["client_credentials"]. Other values will return a 400 error code.

Note that as the client credentials grant requires a client secret, all clients should be regarded as confidential, as defined in the OAuth 2.0 specification (https://oauth.net/2/client-types/).

The response body will include the client ID and client secret that can be used with the /oauth2/tokens endpoints to obtain an access token. The client secret must be stored securely, and cannot be retrieved in subsequent API calls. If you lose the client secret, a new secret can be generated using the PUT /oauth2/clients/{oauth_client_id}/secret endpoint.

Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
  • SlashID-Required-Consistency string

    Possible values: [local_region, all_regions]

    Default value: local_region

    The consistency level required for this request. If the consistency level is not achieved within the timeout, the request will fail with a 408 Request Timeout error. 408 Request Timeout error indicates that request was not handled within the timeout, but it may still be handled after request timeout. Allowed values: * local_region: Wait while the request executes in the local region. * all_regions: Wait while the request executes across all regions. You can learn more about our replication model on our Cross-region Replication Model page.

  • SlashID-Required-Consistency-Timeout integer

    Possible values: >= 1 and <= 120

    Default value: 30

    The maximum amount of seconds to wait for the requested consistency level to be achieved. If the consistency level is not achieved within this time, the request will fail with a 408 Request Timeout error. 408 Request Timeout error indicates that request was not handled within the timeout, but it may still be handled after request timeout. You can learn more about our replication model on our Cross-region Replication Model page.

Request Body
  • client_name string required

    Human-friendly name to identify this client.

  • scopes string[] required

    The scopes this client is allowed to request.

  • grant_types string[] required

    Possible values: [client_credentials]

    The client's allowed grant types.

  • access_token_duration integer

    How long (in seconds) access tokens should be valid for. If unspecified, it is set to your organization's default value.

Responses

OK

Schema
  • meta object
  • pagination object
  • limit integer
  • offset integer
  • total_count int64
  • errors object[]
  • httpcode integer
  • message string
  • result object
  • client_id string

    The client identifier.

  • client_name string

    Human-friendly name to identify this client.

  • grant_types string[]

    Possible values: [client_credentials]

    The client's allowed grant types.

  • response_types array[]

    Possible values: [code, id_token, token]

    The client's allowed response types. All allowed combinations of response types have to be listed.

  • scopes string[]

    The scopes this client is allowed to request.

  • access_token_duration integer

    How long (in seconds) access tokens should be valid for. If unspecified, it is set to your organization's default value.

  • public boolean

    Indicates if this client is marked as public. Public clients are unable to use registered client secrets, such as applications running in a browser or on a mobile device.

  • client_secret string

    The client secret key.