Skip to main content
Coming soon. The public Developer API is on the roadmap. The page below outlines the planned surface so you can plan integrations. See roadmap.
Keloa already powers a Developers area inside the app — workspace admins manage outbound webhook endpoints today. The full public API (with stable tokens, versioned routes, and SDKs) is the next step. This section documents what’s planned so you can architect against it.

​
What exists today

Inside the app, Settings → Developers ships:
  • Outbound webhooks — admins register HTTPS endpoints, pick events, and receive signed POSTs as those events fire. Built. See Webhooks for the planned event taxonomy and payload shape.
Per AI agent, under AI agents → Channels → Web widget:
  • Identity verification — your backend signs a short-lived token for a user signed in to your site, and the web widget hands it to Keloa, so nobody can chat as one of your users. Built. See Identity verification.
Under Integrations → Zapier:
  • Zapier — owners and admins connect the workspace to Zapier through OAuth, so Zaps can start on Keloa events and act in the workspace. Built. See Zapier for the setup and the API the integration uses.
What’s not shipped yet (covered in detail on the linked pages):
  • A versioned, stable, public REST API surface.
  • API tokens with scoped abilities suitable for production use.
  • Official SDKs.
If you need integration today, the supported paths are:
  • The Custom HTTP tool — let your AI agent call your endpoints from inside a conversation. Already shipped.
  • The Shopify integration — orders, products, tracking lookup. Already shipped.
  • Outbound webhooks — push Keloa events to your stack. Already shipped.
  • Identity verification — tell the web widget who your signed-in users are. Already shipped.
  • Zapier — connect Keloa to thousands of apps without code. Already shipped.

​
The planned API shape

When the public API ships, expect:
  • Base URL — https://api.keloa.ai/v1.
  • Auth — bearer tokens issued in Settings → API tokens, sent as Authorization: Bearer keloa_....
  • Tenancy — every token is scoped to a single workspace. Cross-workspace operations require multiple tokens.
  • Rate limits — per-token, returned as X-RateLimit-* headers; sensible defaults for SMB usage.
  • Format — JSON in/out, ISO-8601 timestamps in UTC, UUIDs for every resource.
  • Pagination — cursor-based with a next_cursor field; no offset/limit.
  • Errors — standard { error: { code, message, ... } } envelope.
These choices follow what the app already uses internally, so the surface should feel consistent with what you see in the dashboard.

​
Resources we plan to expose

  • accounts (read-only — your workspace metadata).
  • contacts — list, create, update, delete; merge.
  • conversations — list, read, create message, resolve, reopen, set priority.
  • messages — read, create on a conversation.
  • agents — read, list (modification stays in the dashboard initially).
  • knowledge_sources — list, create, delete; trigger re-ingest.
  • tags — list, attach, detach.
  • webhooks — already supported via the in-app UI; will be addressable via API too.

​
What’s stable today vs aspirational

Subscribe to updates on the roadmap page so you’re notified when each lands.

Identity verification

Verify signed-in users in the web widget.

API tokens

Planned token management.

Webhooks

Outbound events Keloa will push.

Zapier

Connect Zapier, and the API it uses.