API & developers
Your systems, reading and writing Kanesh data.
A REST API, an MCP server and signed webhooks, behind scoped, revocable keys. On approved projects, not self-service.
Beta Available on approved projects, not self-service.
# List contacts with a read-only keycurl https://app.kanesh.example/api/v1/contacts \ -H "Authorization: Bearer kn_live_••••"Keys that only do what you allow.
A REST API and OpenAPI schema for your data, with scoped keys. Give each integration its own key, with only the scopes it needs.
- An OpenAPI schema, so you can generate a client in the language you use.
- Scoped keys: read, write or send, resource by resource.
- Keys are stored as a hash and can be revoked at any time.
- Idempotent template sends, so a retried request doesn't message a customer twice.
- Reference docs inside the app once your project is approved.
Illustration of creating an API key: it gets a name and only the scopes it needs, the key is shown once, and later it is revoked so requests with it are rejected.
Your systems need to talk to your customers too.
Data stuck in one place
Contacts, conversations and orders your ERP or BI can't read.
Alerts that never go out
Your system knows something happened but can't send the right WhatsApp template.
Brittle integrations
Scripts without auth or limits that break as soon as something changes.
What a key can be allowed to do.
Every key gets only the scopes you tick. These are the resources available today.
Read
- contacts
- conversations
- messages
- orders
- team
- labels
- usage
- analytics
- attribution
- automations
- campaigns
- clicks
- segments
Write
- contacts
- conversations
- labels
- segments
Send
- templates:send
The exact scope identifiers are in the reference docs for approved projects.
Operate Kanesh from your AI.
Ask your AI to build reports, configure workflows, prepare campaigns and landing pages and manage customers through MCP, with your permissions.
- Connects over streamable HTTP and authenticates with a bearer API key.
- Works with MCP clients that let you set that key. It isn't a one-click connector for consumer AI apps.
Read
- Contacts
- Conversations
- Messages
- Orders
- Campaigns
- Segments and members
- Automations
- Metrics
- Attributions
Act
- Build reports and dashboards
- Configure AI guidance and knowledge
- Build workflows and campaigns
- Create and publish landing pages
- Manage CRM, catalogue and orders
Events out, messages in.
Two more pieces for teams that need Kanesh to talk to their own systems.
Signed webhooks
BetaSigned webhooks for key events, so your endpoint can check each one came from Kanesh. The event list is shared with approved projects.
Custom API channel
BetaBring conversations from a channel you run into the shared inbox through the API.
Four steps, no self-service sign-up.
- 01
Tell us the project
What you want to connect, and which data it needs.
- 02
We approve it
If it fits, we enable API access for your workspace.
- 03
Scoped keys
One key per integration, with only the scopes it needs.
- 04
Build and revoke
Build against the OpenAPI schema. Revoke a key whenever you want.
Developer questions
Can I get an API key right away?
Is there an SDK?
Can I connect ChatGPT or Claude?
Which webhook events are there?
What happens if a key leaks?
Tell us what you want to build.
Access is granted per project. Tell us what you want to connect in the diagnosis, and we'll say honestly whether it fits.