Documentation Index
Fetch the complete documentation index at: https://docs.kataven.ai/llms.txt
Use this file to discover all available pages before exploring further.
WidgetKeysClient is reachable on every Kataven client as client.widget_keys. Each method maps to one HTTP endpoint on the Hub API; links to the underlying spec entry are inline below.
pk_live_ keys are the public identifiers you put in your website’s HTML widget bootstrap. They’re not credentials — domain allowlists keep them safe.
Methods at a glance
| Method | HTTP | Summary |
|---|---|---|
list | GET /api/v1/widget-keys | List widget keys |
create | POST /api/v1/widget-keys | Create a widget key (returns plaintext pk_live_ ONCE) |
update | PATCH /api/v1/widget-keys/{widget_key_id} | Update or revoke a widget key |
delete | DELETE /api/v1/widget-keys/{widget_key_id} | Delete or soft-disable a widget key |
Reference
client.widget_keys.list(...)
List widget keys
HTTP — GET /api/v1/widget-keys · API reference →
client.widget_keys.create(...)
Create a widget key (returns plaintext pk_live_ ONCE)
HTTP — POST /api/v1/widget-keys · API reference →
domain_allowlist: origins permitted to load the embed. Wildcards supported:acme.com,*.acme.com,localhost:*. Empty allowlist = key blocked.agent_id: optional pin. If set, the widget bootstrap forces this agent regardless of the embed’sdata-agentattribute.
<script data-client-key="..."> attribute.
client.widget_keys.update(...)
Update or revoke a widget key
HTTP — PATCH /api/v1/widget-keys/{id} · API reference →
client.widget_keys.delete(...)
Delete or soft-disable a widget key
HTTP — DELETE /api/v1/widget-keys/{id} · API reference →

