Nodium API · v1

Your software talks to your customers on WhatsApp.

Send and receive messages, manage contacts and templates, follow every delivery by webhook — and choose who answers: the collaborator or your code.

Quickstart Browse the reference

Example

curl https://nodium.io/api/v1/inbox/conversations \  -H "Authorization: Bearer $NODIUM_KEY" \  -H "Content-Type: application/json" \  -d '{    "channelId": "9f4c…",    "to": "+33612345678",    "templateName": "order_ready",    "templateLanguage": "fr",    "variables": { "1": "Karim" },    "idempotencyKey": "order-1042"  }'

200 OK

{  "data": {    "conversationId": "c81d…",    "duplicate": false,    "message": {      "id": "5b2e…",      "type": "template",      "status": "sent",      "textContent": "Bonjour Karim, votre commande est prête."    }  }}

Base URL: https://nodium.io/api/v1
Authentication: Bearer nod_…
Responses: { data } · { error }
Limit per key: 600 / min

Where to start

Get startedFrom nothing to a first message sent and answered, in three calls.Read AuthenticationOne key, one workspace, one role. The key acts as itself.Read WebhooksNodium calls you when something happens. Signed, retried, logged.Read

The reference

All 0 endpoints

What makes a first try fail

window_closedThe 24-hour windowOutside it, only an approved template goes out. The API refuses before WhatsApp does.idempotencyKeyOne idempotency key per sendRequired: two calls with the same key send once.error.codeTest the code, not the textEvery refusal carries a stable code and a request id.X-Nodium-SignatureVerify every webhookHMAC-SHA256 over the raw body; two signatures while a secret rotates.

For your tools and your agents

The OpenAPI 3.1 description generates an SDK in one command; llms.txt hands the whole API to an agent. Both are drawn from the code, never written by hand.

openapi.json llms.txt