Keys
Settings → Keys centralizes platform keys used by the widget and public REST
API integrations.
Key Types
Widget keys are public identifiers. They can live in client-side install snippets, but they do not grant account or operator access by themselves.
Use widget keys to:
- Install the Woes widget.
- Route a page to a specific support agent.
Agent Keys
Each agent can have its own widget key. The Keys page lists agent keys, source
counts, and copy actions so teams can install the right agent in the right
place. Workspace/default widget keys may exist for default or legacy runtime
support, but agent widget keys are the primary install and routing surface.
Workspace API Keys
Workspace API keys are table-backed and stored hashed. The full secret is shown once at creation time.
Use workspace API keys from server-side integrations only. Valid public API
calls are tracked against the key that authenticated the request, so admins can
review usage by integration from Settings → Billing.
The Keys page shows the key name, prefix, status, created date, last-used date,
and revoke action. The current in-app key creator makes a named workspace API
key; server-side API support also understands scoped keys where those are
created by backend or administrative tooling. API request examples and endpoint
schemas live in the API Reference.
Treat woesk_ secrets as private. Do not put them in browser code, docs pages, support messages, screenshots, or client-side snippets.
