Skip to main content
Dugble gives your application one API for sending transactional email. Send requests are accepted asynchronously, so your application gets an immediate response while Dugble handles delivery in the background.

Before you send

You need:
  • A Dugble team and a team token with the email:send permission
  • A verified sender domain
  • A from sender address
  • At least one to recipient
  • A subject
  • An HTML body, a plain-text body, or both
Keep team tokens on your server. Never expose them in browser or mobile application code.

Send an email

A successful request returns 202 Accepted with the Dugble message ID:
202 Accepted means Dugble accepted the message for delivery. It does not mean the recipient’s mail server has delivered it.

Address formats

The required from field and the to, cc, bcc, and reply_to fields accept friendly-name strings:
They also accept structured objects:
Recipient fields accept a single address or an array. An email can include up to 50 recipients across to, cc, and bcc.

Message content

Provide at least one of:
  • html for the HTML version
  • text for the plain-text version
Each body can be up to 1 MiB. Providing both versions gives receiving clients a suitable fallback when HTML is unavailable.

Track a message

Retrieve the message using the ID returned by the send request:
The last_event field reports the latest known state, including queued, processing, submitted, delivered, delayed, bounced, complained, rejected, failed, or canceled.

Next steps

Sending email

Learn the request fields and recommended sending workflow.

Attachments

Attach Base64-encoded files to an email.

Schedule email

Send later, reschedule, or cancel a scheduled email.

Delivery status

Understand the email delivery lifecycle.