Developers

Put a WhatsApp inbox inside your own product

If you build software for Nigerian businesses — a hotel system, a clinic system, a school portal — your customers keep asking for WhatsApp. K3Bot is the part you would otherwise have to build.

Status. The authentication, API-key and embedding layer is built and running. Public documentation, self-service keys and a sandbox are not. Integrations today are arranged with us directly.

Two ways to integrate

In development

Embed the inbox

Your application asks K3Bot for a short-lived code and opens the inbox in a frame inside your own interface, under your brand and colour. Your users never see a second login and never leave your product.

Built already: one-time codes, short sessions, per-customer branding and an origin allowlist so the inbox only opens inside domains you have registered.

Planned

Call the API directly

Read conversations, send messages and receive events from your own backend, with an API key scoped to one business.

Built already: API keys with scopes, per-business authentication and request limits. Missing: documentation, a sandbox and a way to issue yourself a key.

How the integration is shaped

So you can judge whether it fits your architecture before talking to us.

ConcernHow K3Bot handles it
AuthenticationAn API key per business, sent as a bearer token. Keys are scoped, so a key that may create inbox sessions cannot do anything else.
Separating customersEvery request resolves to exactly one business, and the separation is enforced in the database query rather than checked afterwards.
EmbeddingYour backend requests a single-use code; the browser exchanges it for a short session. The code cannot be reused.
Where it may openYou register the origins allowed to embed the inbox. A request from anywhere else is refused.
BrandingBusiness name and brand colour are applied at load, so the inbox matches your product rather than ours.
Inbound messagesMessages are routed to the right business by the WhatsApp number they arrived on, and each business's webhook signature is verified against its own credentials.

Tell us what you are building

We are choosing the first integration partners by hand so the API is shaped by real use rather than guesswork. If you have a product and customers asking for WhatsApp, we would like to hear about it.

Start a conversation