Developers · Email
Transactional email API inside Email Marketing
Ship product and transactional email through Azmarq’s Email Marketing stack — with deliverability tooling for domains, IPs, routing, and suppression.
Built for: Product and platform engineers sending receipts, alerts, and lifecycle mail
- Transactional send
- Domains & IPs
- Suppression & bounces
What you can build
01
Transactional by design
API access for receipts, password resets, alerts, and product mail.
02
Deliverability controls
Domains, dedicated IPs, warmup, smart routing, bounces, and suppression lists.
03
Campaigns when needed
Same product surface also covers marketing campaigns and automations in the console.
Quick start
01
Verify your sending domain
Complete DNS (SPF/DKIM/DMARC as guided) before production volume.
02
Create API credentials
Issue keys for your app environment from Email Marketing / console settings.
03
Send a test transactional mail
Post a minimal message to a mailbox you control; check bounce/event webhooks.
04
Wire suppression
Respect unsubscribes and hard bounces before scaling campaigns.
Auth
Credentials from your console
Use server-side API keys only. Confirm live endpoints and event payload schemas in your Azmarq console documentation.
Illustrative send (shape only)
httpPOST /v1/email/messages
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json
{
"from": "alerts@yourdomain.com",
"to": ["user@example.com"],
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>",
"tags": ["transactional", "receipt"]
}
# Confirm templates, attachments, and event webhooks in-console.Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.
Common use cases
Product receipts
Order confirmations and invoices from your commerce backend.
Security notices
Password resets and login alerts with high deliverability expectations.
Lifecycle alongside WhatsApp
Use email when chat isn’t the right channel — orchestrate from Journeys or your app.
FAQs
Email API — FAQs
Integration basics, credentials, and how this API relates to the product console.
Talk to salesThe API focus is transactional (receipts, alerts, product mail). Marketing campaigns and automations also live in Email Marketing’s console.
Yes for production deliverability — complete DNS (SPF/DKIM/DMARC as guided) before scaling volume.
Yes — subscribe to email events via Webhooks and confirm event types in-console.
Build on Email
Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.
