One API call, one message
Use a key with emails:send permission and a verified sender. Send HTML, plain text or a saved template with variables, including To, CC and BCC recipients.
000° Transactional email: API and SMTP
Send order confirmations, access links and notifications directly from your code through the API, or from any software that can send over SMTP. No campaign or workflow required.
The example request is not executed by this page.
090° From idea to outcome
Use a key with emails:send permission and a verified sender. Send HTML, plain text or a saved template with variables, including To, CC and BCC recipients.
Include attachments, Reply-To, metadata, tags and a scheduled send time. Idempotency-Key prevents duplicate messages when retrying the same request.
Receive identifiers and statuses you can query through the API. Signed webhooks report delivery events; acceptance into the queue is not delivery.
POST /v1/sending/emails
curl https://api.azimea.com/v1/sending/emails \
-H "Authorization: Bearer $AZIMEA_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042-confirmation" \
-d '{
"to": [{"email": "emma@example.com"}],
"subject": "Order 1042 confirmed",
"html": "<p>Thank you for your order.</p>"
}'The example request is not executed by this page.
API documentation →WordPress, PrestaShop, OpenCart, Magento, Shopware, a CRM or an ERP can send through Azimea with four settings. The emails take the same route as API calls: verified sender, queue, suppressions, plan limits, delivery statuses and webhooks.
smtp.azimea.comazimeaNo. Both are for transactional email. Use campaigns and workflows for marketing, with their consent rules. Account limits and suppressions apply; an accepted request may wait for sender verification.
Feature availability and limits depend on your plan and account configuration. View plans →
000° Start today
Create your account, connect your data and prepare your first customer communication.