Skip to main content
The kataven Python package wraps every Hub API endpoint with a typed, ergonomic client.

Quickstart

Resources

API key (sk_live_) management is deliberately not exposed in the SDK. A leaked sk_live_ shouldn’t be able to mint another sk_live_ — otherwise rotation isn’t a real defense. Server enforces this with 403 Forbidden on POST/PATCH/DELETE /api/v1/api-keys for sk_live_ callers; the SDK doesn’t bother trying. Manage keys at Hub UI → Settings → API Keys (Zitadel JWT auth required). Intentionally not in the SDK (admin / dashboard-only operations): client.config, client.settings, client.spokes, client.users, client.accounts, client.api_keys, recordings.delete, call_limits.update, marketplace.create_template, integrations.create.

Errors

The SDK raises subclasses of KatavenError: Generic KatavenError carries the response body and status for anything else.

Configuration