ListKeys

Search Keys

List all matching keys. By default all keys of the instance on which the caller has permission to read the owning users are returned. Make sure to include a limit and sorting for pagination.

Required permission:

user.read

Request Body

application/json

pagination?

List limitations and ordering.

sortingColumn?string

The field the result is sorted by. The default is the creation date. Beware that if you change this, your result pagination might be inconsistent.

Value in

"KEY_FIELD_NAME_UNSPECIFIED" | "KEY_FIELD_NAME_CREATED_DATE" | "KEY_FIELD_NAME_ID" | "KEY_FIELD_NAME_USER_ID" | "KEY_FIELD_NAME_ORGANIZATION_ID" | "KEY_FIELD_NAME_KEY_EXPIRATION_DATE"

filters?

Define the criteria to query for.

[key: string]?never

Response Body

`application/json`

curl -X POST "https://loading/v2/users/keys/search" \
  -H "Content-Type: application/json" \
  -d '{}'

curl -X POST "https://loading/v2/users/keys/search" \  -H "Content-Type: application/json" \  -d '{}'

{
  "pagination": {
    "totalResult": 0,
    "appliedLimit": 0
  },
  "result": [
    {
      "creationDate": "1s",
      "changeDate": "1s",
      "id": "string",
      "userId": "string",
      "organizationId": "string",
      "expirationDate": "1s"
    }
  ]
}

{
  "code": "not_found",
  "message": "string",
  "detail": {
    "type": "string",
    "value": "string",
    "debug": {}
  }
}

ListKeys

Request Body

Response Body

200application/json

defaultapplication/json

`application/json`

`application/json`