Compose your message
Use text and HTML, recipients, Reply-To and bounded attachments.
Maail Send · InfrastructurePlanned
Keep customers informed at every step.
Connect account messages, receipts and product updates to a delivery workflow your application can follow.
What you can build
Transactional Email API for Product Notifications
Send important product messages. Explore the planned capabilities below.
Verified domains
Prepare ownership checks and SPF, DKIM and DMARC configuration.
Retry safely
Use idempotency and temporary-error handling to avoid accidental duplicate sends.
Delivery feedback
Follow per-recipient events and distinguish acceptance from failure.
Bounce handling
Connect delivery feedback to suppression and complaint policies.
Sending limits
Keep volume and domain throttling under an explicit abuse policy.
Three steps
A workflow your team can follow.
- Verify your sending domain
- Submit content or a template
- Follow delivery events
In practice
One reliable receipt workflow
An order event selects a template and submits a receipt. Your application tracks the result and offers an alternative contact path if delivery fails.
Explore transactional templatesWhat is included in the wider product direction?
Scheduled and batch sending, priority queues and provider failover form the advanced sending scope.
Does an accepted API request mean the email was delivered?
An accepted request enters processing. Follow the documented message and recipient states to distinguish queued, accepted, bounced and failed outcomes; receiver acceptance does not prove inbox placement.
Can I integrate this product today?
This product scope is planned. Discuss your requirements with us to confirm available components, processing terms and integration timing. The public DNS tools can be used without an account.
Start with the task you want to simplify.
Tell us which messages, systems and decisions need to connect.