Inspect CLI credentials - Kato

curl --fail-with-body --silent --show-error \
  "https://api.getkato.io/cli/v1/whoami" \
  -H "Authorization: Bearer $KATO_API_KEY"

{
  "workspace": {
    "id": "workspace_example",
    "name": "Northlane",
    "slug": "northlane"
  },
  "scopes": [
    "env:read"
  ],
  "recordId": null
}

GET

/

cli

/

v1

/

whoami

curl --fail-with-body --silent --show-error \
  "https://api.getkato.io/cli/v1/whoami" \
  -H "Authorization: Bearer $KATO_API_KEY"

{
  "workspace": {
    "id": "workspace_example",
    "name": "Northlane",
    "slug": "northlane"
  },
  "scopes": [
    "env:read"
  ],
  "recordId": null
}

Inspect the workspace, scopes, and optional project pin on a CLI-compatible key. Use a developer access key. This endpoint is part of the CLI API, with its own response format and rate limit. No additional resource scope is required. The response is a top-level object without a data wrapper. recordId is null for an unpinned key.

Response

200 — Returns the resource under data. Example IDs and values are illustrative.

{
  "workspace": {
    "id": "workspace_example",
    "name": "Northlane",
    "slug": "northlane"
  },
  "scopes": [
    "env:read"
  ],
  "recordId": null
}

curl --fail-with-body --silent --show-error \
  "https://api.getkato.io/cli/v1/whoami" \
  -H "Authorization: Bearer $KATO_API_KEY"