Skip to main content
Most of the API is the same whatever the channel. Some things belong to one channel — WhatsApp’s message templates and Meta’s approval, the SMS sender IDs and DLT templates operators register. Those are under /v1/channels/<channel>/…, with the same keys, errors and conventions as the rest.
  • A channel’s endpoints exist when your account has that channel; otherwise they answer 404 channel_off.
  • Their scopes start with the channel: whatsapp.templates:write, sms.senders:read.

​
WhatsApp templates

Outside the 24 hours after someone last wrote, WhatsApp only delivers templates Meta has approved. Manage them here, then use them in messages. Meta reviews every new template and every edit: it is pending, and can’t be sent, until approved. On a number FireFlo hosts for you, you see and change only the templates you submitted.

​
SMS sender IDs and DLT templates

Where operators require it, an SMS goes out only from a registered sender ID, and its text must fill in a registered DLT template. Requests are pending until decided. On FireFlo’s shared SMS service you see and withdraw only what you asked for, and the balance to watch is your account’s — in /v1/usage.

​
What every channel shares

Every channel’s senders — sender IDs, the WhatsApp number, RCS bots, voice numbers — are in one list at GET /v1/senders, whatever the channel.