Build your own workflows on Kato
The first Kato developer tools make it possible to connect custom systems and automate work around your workspace.
Available now to workspace administrators on web.
At a glance
Highlights
- 01Create and revoke workspace API keys from a dedicated developer settings area.
- 02Work with objects, records, and tasks through versioned API endpoints.
- 03Subscribe to signed webhooks and manage project environment values from Kato or the CLI.
Workspace access you can control
Workspace administrators can create and revoke API keys from developer settings. Each key provides an explicit credential for custom tools, scripts, and services that need to work with Kato data.
Keeping key management inside the workspace makes ownership visible and gives administrators a clear place to remove access when a workflow changes.
Versioned APIs and signed webhooks
The first versioned endpoints cover the core building blocks of a Kato workspace, including objects, records, and tasks. Webhooks can notify an external system when relevant changes happen instead of requiring constant polling.
Webhook signatures provide a way for receiving services to verify that a delivery came from Kato before processing it.
Project configuration from the CLI
Developer workflows can also manage project environment values and bring them into local work through the Kato CLI. That creates a more direct path between the records that describe a project and the systems used to build it.