IotaBot logo
API documentation

IotaBot API

Connect your CRM, helpdesk or order system to IotaBot: read conversations, send messages on WhatsApp, Instagram, email and website chat, and receive every message on your own webhook.

The IotaBot API is one REST API over every channel IotaBot runs — website chat, WhatsApp, Instagram and email. Your system reads conversations, sends messages the same way an agent does, and receives each new message on a webhook the moment it arrives.

Pick your channel

WhatsApp APISend and receive WhatsApp messages from your code — on every number you connected.Email APISend from your own domain, reply in thread, and receive every email as JSON.Instagram APIEvery DM and comment on your webhook. Reply from your code.Chat APIYour website chat, in your code: every message in, live replies out.

Every channel uses the same endpoints, the same webhook events and the same errors, so one integration covers all four — and every WhatsApp number, Instagram account and mailbox you connected.

What each API does, with pricing and use cases: WhatsApp API · WhatsApp API pricing · Email API · Inbound email API · Instagram API · Comment to DM · Live chat API

Base URL

https://api.iotabot.com/v1

Requests and responses are JSON. A successful response carries its result in data; an error carries error.code, error.message and error.request_id.

The whole API is also published as an OpenAPI 3.1 spec — import it into Postman or Insomnia, or generate a client from it. There is also a ready-made Postman collection.

Quick start

  1. In IotaBot, open Developers → API keys and create a key. Only the workspace owner and team members with the Developer role can, on a paid plan.
  2. Keep the key on your server — in an environment variable such as IOTABOT_API_KEY, never in a browser or app.
  3. List your latest conversations:
curl -X GET "https://api.iotabot.com/v1/conversations" \
  -H "Authorization: Bearer $IOTABOT_API_KEY"

The API

WebhooksEvery new message and conversation change, pushed to your server, signed and retried.

Versions

The API is versioned by date. A key keeps the version it was created with (currently 2026-10-01); send an IotaBot-Version header to use another one for a single request. Every response names the version it used in its own IotaBot-Version header. A version that is replaced keeps working for 12 months after notice; in that time its responses carry Deprecation and Sunset headers. An unknown version is refused with 400 invalid_version.