Chatz

Workspace

Developer: API and webhooks

API tokens, outbound webhooks and the audit log.

API tokens

Under Settings, then Developer, in the Advanced group, you can generate API tokens for your workspace. A token authenticates requests made against the Chatz API on your workspace's behalf, so a backend, a script or a third-party integration can read and write data without a human logging in.

Treat a token like a password
Anyone holding a token can act as your workspace through the API. Keep tokens out of client-side code and version control, and generate a fresh one if you suspect a token has leaked.

Outbound webhooks

Outbound webhooks do the reverse: instead of your systems calling Chatz, Chatz calls a URL you configure whenever something happens in your workspace, such as a new message or a status change. This is how you push Chatz events into a system that Chatz itself has no integration for, without polling the API for changes.

Audit log

The audit log, also in the Advanced group, records workspace activity: what changed, and who made the change. It is the place to check when a setting, a channel or a member's access looks different than expected and you need to know when and by whom it happened.

Plan availability

API access and outbound webhooks are part of the Scale plan. If your workspace is on a lower plan, upgrade from Billing to unlock this page.