One API for every channel: SMS, WhatsApp, RCS, Email, Voice, Numbers and AI
Integrate once and reach customers on any channel. The Talkloo Omnichannel API uses a single authentication scheme, one messages endpoint with a channel field, one calls endpoint, one contact model and one webhook format – so adding WhatsApp, RCS or an AI voice agent to an app that already sends SMS is a one-line change, not a new vendor.
What is an omnichannel API?
An omnichannel API is a single programmatic interface that lets an application send and receive communication across multiple channels – SMS, WhatsApp, RCS, email and voice – without integrating each channel’s provider separately. Talkloo’s Omnichannel API goes further than messaging-only unified APIs: alongside messages it exposes voice calls, phone number (DID) provisioning, SIP trunk management, a no-code Flow Builder and AI voice/chat agents, all under one account, one API key, one contact model and one webhook schema. It is the developer surface of the Talkloo CPaaS platform.
- Messages: POST /v1/messages with channel = sms | whatsapp | rcs | email, plus an optional fallback order.
- Voice: POST /v1/calls for PSTN, SIP and WhatsApp calls; answer with IVR, queue, SIP URI or AI agent.
- Numbers: search, buy, configure and port DIDs and toll-free numbers by country programmatically.
- Automation: trigger Flow Builder journeys and AI agents; receive one webhook format for every event.
- Style
- REST + JSON, Bearer auth
- Channels
- SMS, WhatsApp, WhatsApp Calling, RCS, Email, Voice
- Infra APIs
- DIDs, SIP trunks, numbers
- Automation
- Flows API, AI Agents API
- Events
- Signed webhooks, retries, replay
Every Talkloo capability, exposed as clean REST resources
Consistent naming, predictable pagination, idempotency keys and signed webhooks across all resources.
Messages API
One endpoint for SMS, WhatsApp, RCS and Email. Send templated or free-form content, attach media, set a fallback order and get a message ID back in milliseconds.
Voice & Calls API
Place and receive calls over PSTN, SIP and WhatsApp. Control calls with IVR instructions or hand them to an AI agent, and receive real-time call events.
Numbers, DIDs & SIP API
Search inventory by country and type, purchase numbers, assign them to flows or SIP trunks, and manage trunks and credentials without opening a ticket.
Flows & AI Agents API
Trigger visual flows with contact data and launch AI voice or chat agents programmatically. Outcomes come back as structured webhook events.
How to integrate the Talkloo API
- 1
Create an API key
Generate a key in the dashboard with scoped permissions (messages, calls, numbers, flows).
- 2
Register a webhook
Add your HTTPS endpoint. Talkloo signs every event and retries with backoff; failed events can be replayed.
- 3
Send your first message or call
POST /v1/messages or /v1/calls. The same request shape works for every channel.
- 4
Add channels by changing one field
Switch channel from "sms" to "whatsapp", "rcs" or "email", or add a fallback array – no new SDK, no new vendor.
Send on any channel with one request
Below, a WhatsApp message with automatic fallback to RCS, then SMS. Delivery, read and reply events all arrive on the same webhook.
curl -X POST https://api.talkloo.com/v1/messages \
-H "Authorization: Bearer $TALKLOO_API_KEY" \
-H "Idempotency-Key: order-A-10432-shipped" \
-H "Content-Type: application/json" \
-d '{
"to": "+923001234567",
"channel": "whatsapp",
"template": "order_shipped",
"variables": { "order_id": "A-10432", "eta": "Thursday" },
"fallback": ["rcs", "sms"],
"metadata": { "customer_id": "c_884" }
}'
# 202 Accepted
{ "id": "msg_8f2k1", "status": "queued", "channel": "whatsapp" }Talkloo Omnichannel API vs messaging-only unified APIs
Several “unified messaging APIs” cover SMS and WhatsApp. Talkloo covers the full communication stack.
| Capability | Talkloo Omnichannel API | Messaging-only unified APIs |
|---|---|---|
| SMS / WhatsApp / RCS | Yes | Yes |
| Yes (API + SMTP) | Usually no | |
| Voice calls & IVR | Yes (PSTN, SIP, WhatsApp) | No |
| Phone numbers / DIDs | Yes, programmatic | No |
| SIP trunking | Yes | No |
| No-code Flow Builder | Yes | Rarely |
| AI voice & chat agents | Yes, native | No |
| Single webhook schema | Yes | Yes |
Frequently asked questions
What channels does the Talkloo API support?
SMS, WhatsApp Business (messaging and calling), RCS Business Messaging, Email and Voice (PSTN and SIP), plus number/DID provisioning, SIP trunk management, Flow Builder triggers and AI agents – all through one REST API.
Is Talkloo a CPaaS?
Yes. Talkloo is a Communications Platform as a Service: it provides the carrier connectivity, channel integrations and APIs that let developers embed messaging, voice and AI conversations into their own applications, alongside a dashboard for non-developers.
How is the Talkloo API different from Twilio?
Twilio exposes each channel as a separate product with its own API conventions and pricing. Talkloo exposes every channel through one messages endpoint and one calls endpoint with a shared contact model, includes email and AI agents natively, and offers flat platform plans plus usage rates. See the Twilio comparison page for details.
Does Talkloo provide SDKs?
Yes, official SDKs are available for Node.js, Python, PHP and Java, and a Postman collection is provided. Because the API is plain REST over HTTPS with JSON, any language with an HTTP client works without an SDK.
How do webhooks work?
You register an HTTPS endpoint and choose the events you want. Every event – message delivered, read, replied, call answered, call completed, flow completed – uses the same envelope, is signed with your webhook secret, and is retried with exponential backoff. Missed events can be replayed from the dashboard or API.
Can I try the API before buying?
Yes. Request sandbox credentials from the contact page. The sandbox supports SMS, WhatsApp and voice test numbers so you can integrate end to end before going live.
Integrate once. Reach every channel.
Request API credentials and a technical onboarding call with our solutions engineers.