EMAIL API

Email for your app and AI agents.

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.

FROM YOUR APP TO THE INBOX

Send. Receive. Know what happened.

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.

Verified sending identities

Use a sender authorized for your project. Complete the identity's DNS verification before sending from that address.

Inbound mail, connected

Receive the sender, subject and text at a configured mailbox. Bring inbound messages into the shared journal and message-received webhook flow.

Delivery state

Read the status of an email through the API. Provider receipts record delivery, hard bounces and complaints when supplied by the connection.

Safe retries

Reuse an idempotency key when retrying a send. The same accepted request returns its existing record instead of sending a second email.

Suppression protection

Hard bounces and complaints update recipient suppression, so later sends respect the delivery history.

BUILT FOR PRODUCT EMAIL

Your message. Your verified identity.

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 connection
  1. Verify your sender

    Publish the required DNS record for the sending identity and confirm verification.

  2. Send a product email

    Submit the subject and text or HTML with a project credential and an idempotency key.

  3. Connect inbound mail

    Configure the receiving mailbox and webhook subscription to bring incoming messages back to your app.

Good to know.

What kind of email can I send?

The email contract supports transactional and operational messages, such as confirmations and requested product updates. It is not a bulk marketing campaign service.

Does email use the same content format as chat?

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.

Are sending and receiving enabled together?

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.

Ready to start building?