API & developers
Your systems, reading and writing Kanesh data.
A REST API with an OpenAPI schema, an MCP server for your own AI tools and signed webhooks, all behind scoped, revocable API keys. Available on approved projects, not self-service.
Beta Available on approved projects, not self-service.
Talk to us about API access# List contacts with a read-only keycurl https://app.kanesh.example/api/v1/contacts \ -H "Authorization: Bearer kn_live_••••"Illustrative demo · synthetic data
REST API
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.
Illustrative demo · synthetic data
Scopes
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.
MCP server
Let your own AI tools work with Kanesh data.
An MCP server so your own AI tools can read and act on your Kanesh data with a scoped API key.
- 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
- Send a WhatsApp template
- Add a note
- Assign a conversation
- Manage labels
- Create or update a contact
Also for approved projects
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.
How access works
Four steps, no self-service sign-up.
- 1
Tell us the project
What you want to connect, and which data it needs.
- 2
We approve it
If it fits, we enable API access for your workspace.
- 3
Scoped keys
One key per integration, with only the scopes it needs.
- 4
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?
Free diagnosis
Tell us what you want to build.
API access is granted per project. Start with the conversation diagnosis, tell us what you want to connect, and we'll tell you honestly whether it fits.