Skip to main content
This index covers every operation on Kato’s developer, CLI, Raycast, and OAuth integration surfaces: 49 canonical operations, plus four compatibility aliases. All paths below use https://api.getkato.io. Choose the surface before choosing an endpoint. Developer keys, Raycast OAuth tokens, and signed-in sessions have different access rules. Internal application routes, provider callbacks, and service-to-service endpoints are not supported developer integration contracts and are not included here. Examples throughout the reference use illustrative IDs and workspace data. Replace them with values returned by your workspace.

​
Developer API

Workspace-scoped developer keys. See authentication.

​
CLI API

Developer keys; environment operations also require a current owner or admin role. See CLI conventions.

​
Raycast API

OAuth access tokens issued to kato-raycast. Every listed scope is required. See Raycast conventions.

​
OAuth

Registered-client authorization and token lifecycle. See OAuth flow.

​
Compatibility aliases

Four older OAuth paths call the same handlers. They are listed alongside their canonical paths in OAuth compatibility paths. Use the canonical endpoint when implementing a new client.