REST API with OpenAPI
Every public endpoint is described in an OpenAPI file and shipped as a Postman collection, so the first call takes a minute, not an afternoon.
For developers
Built for the person who has to integrate it
A documented REST API, an OpenAPI description you can generate a client from, Postman collections, signed webhooks, and a way to put YOUR endpoints inside the AI's reach.
API keys and OAuth
Machine keys that name their own workspace, or OAuth tokens with scopes. Every route states the scope it needs.
Skills: your API, called by the AI
Describe an endpoint of yours — inputs, auth, what it returns — and the agent can call it mid-conversation, with the result written back into the answer.
Knowledge API
Create, update and search knowledge from your own software, with idempotency keys and webhooks when indexing finishes.
Signed webhooks
Conversation, lead, task, knowledge and automation events, signed and retried, so your system hears about a customer the moment we do.
Identity you control
Your system verifies the customer; ConvoOK only records what your system said, and the AI is never shown the account id it was given.
First call
Ask an agent a question
An API key names its own workspace, so there is no workspace header and nothing to switch. Ask, and the answer comes back with the conversation it belongs to.
Rate limits, idempotency keys and error shapes are all in the documentation — including which scope each route needs.
curl -X POST https://api.example.com/v1/agents/{agent_id}/chat \
-H "X-API-Key: cok_your_key" \
-H "Content-Type: application/json" \
-d '{"message": "What are your opening hours?"}'
Two directions
Call us, or let us call you.
Skills: your endpoint, inside the conversation
Describe an endpoint of yours — its URL, its auth, the arguments it takes and what it gives back — and the agent can call it while the customer waits: check an order, look up a balance, book a slot. You choose which agents may use it, and the AI never sees the credential.
Inputs can be bound to the signed-in customer, so a caller cannot ask about somebody else's account.
Webhooks: we tell your system first
Subscribe an endpoint of yours to conversation, lead, task, knowledge and automation events. Every delivery is signed, retried with backoff, and visible in the console with its response, so a broken integration is something you can see rather than guess at.
Straight answers
What you get, and what you do not have to build.
A widget you can embed anywhere
One script tag with a public channel token, an origin allowlist and its own rate limits — or a hosted chat page on a link, when there is no site to edit.
Knowledge that stays in sync
Create, update, search and delete knowledge from your own software, with idempotency keys on writes and a webhook when indexing finishes. Or point ConvoOK at a read-only query on your own MySQL, PostgreSQL or SQL Server.
Identity you stay in charge of
ConvoOK checks no codes. Your system sends the one-time password and says who the customer is; we record only what your system told us, and the account id is never shown to the model.
Build the integration this week
Create a free workspace, mint an API key, and make your first call in about five minutes. The documentation and the Postman collection are open to everybody — no account needed to read them.