Skip to main content

​
What this is

Minimo runs the WhatsApp Business plumbing — the Meta Cloud API / 360dialog / Twilio connection, the number, the inbox, templates and delivery — and lets your backend own the conversation logic. You receive every inbound message on a signed webhook, run whatever bot or AI you want, and send the reply back through one API. In other words: Minimo is the transport, you are the brain. This is the path an external product (for example a legal-AI like IUS) takes to put its own assistant on a WhatsApp number without building a WhatsApp integration from scratch.
This surface assumes you already have a WhatsApp number connected to your company in Minimo (via Channels). Onboarding a number is a separate, dashboard-driven flow and is not part of this API.

​
The flow

1

A customer messages your WhatsApp number

Meta (or 360dialog / Twilio) delivers the message to Minimo.
2

Minimo forwards a normalized event to your webhook

Minimo pushes a stable, provider-agnostic JSON envelope for the whatsapp.message.received event to the URL you registered — HMAC-signed, retried, and idempotent per message. See Inbound Webhook.
3

Your backend decides the reply

Your bot / AI reads the envelope and produces a response. Minimo does not run any logic here — this is entirely your code.
4

You send the reply through the Minimo API

Call the Send endpoint with either a free-form session text (inside the 24-hour window) or an approved template. Minimo delivers it over the right provider and records it in the inbox.
5

(Optional) Read history on demand

Use the Read API to backfill conversation history — handy on bot restarts, for a custom chat UI, or for debugging.

​
Authentication

Every request authenticates with a Minimo API key in the Authorization header:
Create the key in Account Settings → API Keys and grant it the WhatsApp permission.
The WhatsApp permission (whatsapp) is a least-privilege scope for exactly this transport surface: sending WhatsApp messages, managing inbound webhook registrations, and reading WhatsApp conversation history. Issue a WhatsApp-only key for your bot instead of a broad key.The Send endpoint also accepts a legacy Transactional key for backward compatibility, but the webhook and read-API endpoints require the WhatsApp permission.
The company (tenant) is always resolved from the API key — you never pass a company id in the body or headers. A key can only ever read and write its own company’s data.

​
Base URL

All endpoints on this surface are served from the new API host:

​
Coexistence with the native assistant

Forwarding is additive: registering a webhook never disables Minimo’s own native WhatsApp assistant. If you connect your own bot, turn the native assistant off on that channel so you don’t get two replies to one message. See Notes & Limits for the full contract.

​
Next steps

Send messages

Reply with a session text or an approved template.

Receive inbound

Register a webhook, read the envelope, verify the signature.

Read history

Page through conversations and messages.

Notes & limits

Double-handling, current limits, common errors.