Email API for Transactional & Bulk Sending
An Email API lets your application send transactional and bulk email programmatically - order confirmations, invoices, OTPs and newsletters - through code rather than a manual campaign tool. Teleopedia's Email API runs transactional and bulk sending on separately managed IP pools, with domain authentication (SPF, DKIM, DMARC) support, so a promotional send can't damage the deliverability of a critical receipt.
This page covers the integration side of email - what the API sends, how domain authentication and templates work, and how delivery is tracked. For the broader product overview, see Email Messaging.
How Does The Email API Work?
Your backend authenticates with an API key, submits a message with the recipient, template and content, and the platform routes it through the correct IP pool - transactional or bulk - based on how the send is classified. Delivery, open, click and bounce events are then reported back so your application knows the outcome, not just that the request was accepted.
Conceptual example - illustrative only; request full endpoint details from your account team:
// Conceptual - illustrative only
POST /email/messages
Authorization: Bearer YOUR_API_KEY
{
"to": "customer@example.com",
"template": "order_confirmation",
"variables": { "order_id": "BL123456" }
}Email API Capabilities
Separate Transactional & Bulk IPs
Transactional and bulk email run on separately managed IP pools, so one newsletter send can't hurt your OTP or receipt deliverability.
Domain Authentication
SPF, DKIM and DMARC setup support, so receiving servers trust mail sent from your domain instead of routing it to spam.
Templates
Build transactional templates and newsletters in the dashboard, or import existing HTML templates you already use.
Delivery Analytics
Opens, clicks, bounces and unsubscribes tracked per campaign and per recipient.
Email API Use Cases
Transactional Email
Order confirmations, invoices and password-reset emails sent through dedicated infrastructure kept separate from bulk sends.
Newsletters & Promotions
Reach your full subscriber list with bulk campaigns, tracked down to opens and clicks, without touching your transactional sender reputation.
Cross-Channel Follow-Up
Trigger a WhatsApp or SMS message automatically when a time-sensitive email goes unopened after a set period.
Ready To Integrate Email Alongside WhatsApp & SMS?
Talk to our team about domain authentication, templates and API access.
Delivery Events & Webhooks
Delivery, open, click and bounce events are tracked per message, correlated to the send so your application can react - for example, triggering a follow-up on a different channel if an important email goes unopened.
An "opened" event depends on the recipient's email client loading tracking content, which some clients block by default - treat open tracking as directionally useful, not a fully precise measurement.
Email + WhatsApp + SMS Strategy
Email works well for detailed, document-style content - invoices, statements, newsletters - while WhatsApp and SMS suit shorter, time-sensitive updates. A business can trigger the right channel per message type from the same account, with a follow-up on another channel when an important email isn't opened in time - see Omnichannel Messaging Platform for how channel priority is configured across all of them.
Where Email API Fits
Ecommerce
Order confirmations, invoices and shipping receipts, kept separate from marketing sends.
BFSI
Statements and policy documents that need reliable, authenticated delivery to the inbox.
Email API FAQs
What is an Email API?
An Email API is a REST interface that lets your application send transactional or bulk email programmatically - triggered from your backend - instead of composing and sending emails manually.
Does Teleopedia provide an Email API?
Yes, email is one of the channels available through Teleopedia's REST API alongside WhatsApp, RCS, SMS and Voice, with dedicated support for domain authentication, templates and delivery reporting.
What's the difference between this page and the Email Messaging service page?
Email Messaging (Service) covers what the product does at a feature level. This page focuses on the API integration side - how to send programmatically, authenticate requests and handle delivery events.
Do transactional and bulk email share the same sending reputation?
No, they run on separately managed IP pools, so a bulk newsletter campaign never risks the deliverability of critical transactional email like OTPs or receipts.
What is SPF, DKIM and DMARC, and are they required?
These are domain authentication standards that prove an email genuinely came from your domain. They're not strictly mandatory to send email, but skipping them significantly increases the chance of landing in spam - setup guidance is provided as part of onboarding.
Can I track opens and clicks through the API?
Yes, delivery status along with opens, clicks, bounces and unsubscribes are tracked per campaign and recipient, available through the dashboard and delivery events.
Can email trigger a WhatsApp or SMS follow-up?
Yes, cross-channel journeys can check email engagement and automatically send a WhatsApp or SMS follow-up if a customer hasn't opened a time-sensitive email within a set window.
Can I import my existing HTML email templates?
Yes, existing HTML templates can be imported rather than requiring every template to be rebuilt from scratch in the dashboard.
Is Email API pricing different from SMS or WhatsApp pricing?
Yes, each channel has its own pricing structure - talk to our team for a quote covering your actual email volume alongside any other channels you're using.
How do I get the exact Email API endpoint reference?
Request API access through Teleopedia's API Documentation page for full endpoint references and live credentials - this page covers the integration concepts and capabilities rather than a complete field-by-field spec.
Can Email run on the same account as WhatsApp and SMS?
Yes, Email sits on the same panel, contact list and API as WhatsApp, RCS and SMS, so a cross-channel journey doesn't require a separate tool or integration.
What happens to my email if it bounces?
Bounce handling is built in and reported back through delivery analytics, so a bad address doesn't silently damage your sender reputation over repeated attempts.
Ready to unify your business communication?
Most businesses are live on their own branded panel within days, not months - talk to our team today and see how fast you can start sending.