---
title: "aid_auths_client_grants_get"
method: GET
path: "/accounts/{oid}/auth/client-grants"
tags: ["grants"]
---

# aid_auths_client_grants_get

`GET /accounts/{oid}/auth/client-grants`

Manage your Client Grants (also called Client Credentials Grants).
Using Client Grants, your Client can request an access token using
its credentials (a Client ID and a Client Secret).
The access token then represents your Client during API calls.

Use the Grant type to limit how the grant can be used when requesting
an access token. A Grant with type `password` can only be used when
requesting an access token with grant_type set to `password`.

scopes:
- admin:accounts
- read:accounts

## Path parameters

- `oid` string, ^[PT]{1}(?=(?:.{3}|.{8})$)[0-9]*$, required

## Query parameters

- `audience` string
- `client_id` string

## Response `200`

Grant Collection

- Grant[]
  - `id` string, uuid — An UUID that uniquely identifies the resource
  - `created_at` string, date-time — The date-time when the resource was created
  - `created_by` string — The ID of the user/client created the resource
  - `updated_at` string, date-time — The date-time when the resource was last updated
  - `deleted_by` string — The ID of the user/client created the resource
  - `deleted_at` string, date-time
  - `client_id` string, required
  - `audience` string, required
  - `scope` string[], required
  - `type` 'any' | 'authorization_code' | 'client_credentials' | 'password' — Limit the usage of the grant. A grant with grant_types set to only `authorization_code` cannot be used in [Get Token](/api-reference/authenticate/aid_auths_oauth_token_post) when calling the endpoint with `grant_type=client_credentials`
  - `oidc` object — Open ID connect configuration for the Grant. The option enables client to verify the identify of the End-User based on the authentication performed by an authorization server The grant type must be set to `authorization_code` when configured.
    - `client_id` string, required
    - `client_secret` string, required
    - `authority` string, url, required — The authority for the authentication, the authority must support OpenID connect discovery example: https://identityserver.example.com/access/.well-known/openid-configuration

## Other responses

- `401` — Access forbidden, invalid JWT token was used
- `403` — Forbidden
- `500` — Unexpected Error

---

[API](https://skmtc.net/dintero/apis/account-management-api.md) · [All operations](https://skmtc.net/dintero/apis/account-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/dintero/account-management-api/revisions/9b83a4199008/schema)