Email API for transactional and bulk email – on the same platform as SMS, WhatsApp and Voice
Send OTPs, receipts, alerts and marketing campaigns over email with a REST API or SMTP relay. Because email lives inside the same omnichannel account as your other channels, one contact record, one template library and one set of webhooks cover every message you send.
What is the Talkloo Email API?
The Talkloo Email API is a programmable email sending service that lets your application send transactional email (one-time passwords, receipts, password resets, alerts) and bulk marketing email through a single REST endpoint or a standard SMTP relay. It runs on the Talkloo omnichannel platform, so the same contact list, templates, suppression rules and webhooks you use for SMS and WhatsApp also apply to email – and you can set email as a fallback channel when a message cannot be delivered elsewhere.
- Two sending modes: REST API (JSON) for application events, SMTP relay for existing mail servers and tools.
- Separate transactional and marketing streams so promotional volume never hurts OTP deliverability.
- Domain authentication (SPF, DKIM, DMARC) plus dedicated IP options for high-volume senders.
- Webhooks for delivered, opened, clicked, bounced, complained and unsubscribed events.
- Protocols
- REST API, SMTP
- Streams
- Transactional + marketing
- Auth
- SPF, DKIM, DMARC
- Tracking
- Open, click, bounce webhooks
- Fallback
- Email ⇄ SMS ⇄ WhatsApp
Everything a modern email sender needs, inside your omnichannel stack
Talkloo Email is built so engineering teams stop stitching together a separate email vendor, a separate SMS vendor and a separate WhatsApp BSP. One account, one API key, every channel.
Transactional email API
Trigger email from any backend event with a single HTTP call. Sub-second acceptance, priority routing and a dedicated transactional stream keep OTPs and receipts fast.
Bulk email campaigns
Upload or sync an audience, choose a template, schedule and send. Campaign analytics show delivery, opens, clicks and unsubscribes per segment.
SMTP relay
Point an existing application, CMS or mail server at Talkloo’s SMTP endpoint and keep your current code. Same analytics, same webhooks.
Deliverability tooling
Guided SPF, DKIM and DMARC setup, bounce classification, complaint feedback loops and reputation monitoring so mail lands in the inbox.
How to send email with Talkloo in four steps
Most teams send their first production email within a day.
- 1
Verify your sending domain
Add the SPF, DKIM and DMARC records Talkloo generates for your domain. Verification is automatic once DNS propagates.
- 2
Create a template
Build HTML or plain-text templates in the dashboard with variables such as {{first_name}} or {{otp}}. The same template engine is shared with SMS and WhatsApp.
- 3
Send via API or SMTP
Call POST /v1/messages with channel "email", or relay through smtp.talkloo.com with your credentials.
- 4
Track with webhooks
Receive delivered, opened, clicked, bounced and complained events at your callback URL and feed them into your CRM.
One request. Any channel.
The email endpoint is the same messages endpoint used for SMS, WhatsApp and RCS. Set the channel, pass a template and variables, and Talkloo handles rendering, authentication headers and delivery tracking.
POST /v1/messages
Authorization: Bearer <API_KEY>
{
"channel": "email",
"to": "customer@example.com",
"from": "alerts@yourdomain.com",
"template": "order_confirmation",
"variables": { "order_id": "A-10432", "total": "$129.00" },
"fallback": ["sms", "whatsapp"],
"callback_url": "https://yourapp.com/webhooks/talkloo"
}
// 202 Accepted
{ "id": "msg_8f2k1", "channel": "email", "status": "queued" }What businesses send with Talkloo Email
OTP & security email
Password resets, login codes and new-device alerts on the transactional stream with priority delivery.
Receipts & notifications
Order confirmations, invoices, shipping updates and account changes triggered from your backend.
Marketing campaigns
Newsletters, promotions and lifecycle drips with segmentation, scheduling and engagement analytics.
Channel fallback
Send by WhatsApp or SMS first and fall back to email automatically when a number is unreachable.
AI agent follow-ups
Let a Talkloo AI agent send a summary or document by email after a voice or chat conversation.
Flow Builder journeys
Drop an email node into any Flow Builder journey alongside SMS, WhatsApp and voice steps.
Frequently asked questions
Does Talkloo offer an email API as well as SMS and WhatsApp?
Yes. Talkloo Email is a native channel on the omnichannel platform. You can send transactional and bulk email through a REST API or SMTP relay using the same account, API key, contact list and webhooks as your SMS, WhatsApp, RCS and voice traffic.
Can I use Talkloo as an SMTP relay?
Yes. Talkloo provides an SMTP endpoint with TLS on ports 587 and 465. Any application or mail server that speaks SMTP can send through it without code changes, and you still get delivery, open and click tracking.
How does Talkloo protect email deliverability?
Transactional and marketing mail run on separate streams, sending domains are authenticated with SPF, DKIM and DMARC, bounces and complaints are automatically suppressed, and high-volume senders can use dedicated IP pools. Reputation and bounce rates are visible in the dashboard.
Can email be a fallback for SMS or WhatsApp?
Yes. Pass a fallback array in the API call or add a fallback branch in Flow Builder. If a WhatsApp or SMS message fails or is not delivered within your timeout, Talkloo automatically sends the email version of the template.
Does the email API support attachments and HTML?
Yes. Templates support full HTML with inline CSS, plain-text alternatives, inline images and attachments up to 10 MB per message.
What events does the email webhook send?
Accepted, sent, delivered, opened, clicked, bounced (hard and soft), complained and unsubscribed. Every event carries the message ID and any metadata you attached at send time.
Consolidate email with the rest of your channels.
Get a sending domain verified, an API key issued and your first transactional email live – usually within a day.