Skip to main content
The Kataven Hub REST API is the canonical management surface for your account. Every dashboard screen at hub.kataven.ai, the Python SDK, the Node SDK, and the MCP server all sit on top of this same API — they’re convenience wrappers, not separate products. Use REST directly when:
  • You’re writing in a language we don’t ship an SDK for (Go, Rust, Ruby, PHP, Java, Elixir, Bash, …).
  • You’re hitting Kataven from a CI pipeline or webhook handler where adding a runtime dependency is overkill.
  • You’re debugging an SDK call and want to see the raw HTTP request and response.
Otherwise — pick the SDK or MCP that fits your runtime; same endpoints, less boilerplate.

​
Resources

Every endpoint is grouped under a resource in the sidebar. Each resource page lists every endpoint, with parameters, response codes, schema fields, and copy-paste examples in curl, Python, and Node.

​
Conventions

  • Base URL. https://api.kataven.ai/v1. Production. Outages on hub.kataven.ai (the dashboard) don’t affect this; rate-limit and monitoring policies apply independently.
  • Authentication. Authorization: Bearer <token>. Token is either an sk_live_… API key (preferred — see Authentication) or a Zitadel JWT (interactive admin sessions only). sk_live_ callers don’t need an X-Account-ID header — the account is in the prefix.
  • Content type. application/json for request and response bodies. Multipart used by POST /v1/campaigns (CSV upload).
  • Idempotency. Read endpoints (GET) are safe to retry. Write endpoints (POST/PATCH/DELETE) are not idempotent today — don’t blindly retry on connection errors. Idempotency-Key support is on the roadmap.

​
Status codes you’ll see across the surface