Channellive
Transactional + marketing email, delivered through the same typed SDK you use for WhatsApp. Verified sending domains, shared suppression, and delivery webhooks that match every other channel.
#What ships today
zaptick.email.send— transactional sends with HTML, text, or a saved template plus variables.zaptick.email.templates— list, fetch, create, and version your HTML templates via API.zaptick.email.subscribers— a dedicated email audience with double opt-in, bounces, and unsubscribes.zaptick.email.campaigns— schedule, launch, and pause bulk sends with stats in the same response.- Every API-originated send fires
email.sentto every webhook endpoint you've registered — so the Deliveries log shows email traffic next to WhatsApp.
#Before your first send
Email traffic needs a verified sending domain so messages actually land. Add and verify your domain from the dashboard in under five minutes:
- Open zaptick.io/email/domains and add your domain.
- Paste the generated DKIM / SPF / DMARC records into your DNS.
- Click
Verify— Zaptick polls until the records propagate.
Sends from an unverified domain return
email_send_failed with a clear message. Use a sandbox address like noreply@inbox.zaptick.io for early integration testing.#Send your first email
TypeScript
#Resources
email.send
Transactional + templated sends, idempotency keys, and tag-based analytics.
email.templates
Create and update HTML templates with {{ variable }} placeholders.
email.subscribers
Audience CRUD with opt-in status, tags, and custom fields.
email.campaigns
Schedule, launch, and pause bulk marketing sends.
#Deliverability notes
- Always supply a plain-text
textbody alongsidehtml. Mailbox providers dock reputation for HTML-only mail. - Tracking pixels and link-rewrites are on by default. Turn them off per-send for receipts and password resets (dashboard-only toggle for now).
- Marketing sends respect the workspace suppression list automatically. Unsubscribing a subscriber via the SDK permanently suppresses their address.