Product email, through an API
Send transactional and operational messages with a subject, plain text and HTML. Set recipients and a Reply-To address for the workflow.
Send product emails from a verified identity. Receive inbound mail through a configured mailbox, and bring it into your application's messaging workflow.
Sender verification and receiving-mailbox setup required.
Your order will be ready tomorrow at 10.
Send transactional and operational messages with a subject, plain text and HTML. Set recipients and a Reply-To address for the workflow.
Use a sender authorized for your project. Complete the identity's DNS verification before sending from that address.
Receive the sender, subject and text at a configured mailbox. Bring inbound messages into the shared journal and message-received webhook flow.
Read the status of an email through the API. Provider receipts record delivery, hard bounces and complaints when supplied by the connection.
Reuse an idempotency key when retrying a send. The same accepted request returns its existing record instead of sending a second email.
Hard bounces and complaints update recipient suppression, so later sends respect the delivery history.
Connect a sending identity and configure a receiving mailbox for your project. Your application owns the email content and audience; TidyMessages handles authorized sending, inbound routing and delivery records.
Discuss your connectionPublish the required DNS record for the sending identity and confirm verification.
Submit the subject and text or HTML with a project credential and an idempotency key.
Configure the receiving mailbox and webhook subscription to bring incoming messages back to your app.
The email contract supports transactional and operational messages, such as confirmations and requested product updates. It is not a bulk marketing campaign service.
Email has its own subject, text, HTML, recipient and sender-identity fields. Incoming mail can join the shared message journal; channel contracts and setup remain distinct.
They require separate setup. Sending needs a verified identity; receiving needs a configured mailbox and receiving route. Confirm the connection available to your project during onboarding.