Skip to main content
Dugble lets you send transactional email immediately or schedule it for later delivery.

​
Basic request

Send email with POST /emails and include an idempotency key so retries do not create duplicate messages.
A successful send request returns 202 Accepted. This means Dugble accepted the message for asynchronous delivery; it does not mean the recipient’s mail server has delivered it.

​
Message content

Every email needs a from sender, at least one to recipient, and a subject. Include at least one of html or text for the body. You can also provide cc, bcc, reply_to, custom headers, attachments, tags, metadata, and a future scheduled_at value.

​
Sender address

The from value is required and can be an email address or a display name with an email address, such as:
Use a sender address on a domain that has been configured and verified for sending.

​
Multiple recipients

The to, cc, bcc, and reply_to fields accept a single address or a list of addresses. A message can include up to 50 recipients across to, cc, and bcc.

​
Schedule delivery

Set scheduled_at when the message should be delivered later instead of immediately. See Schedule Email for scheduling, rescheduling, and cancellation workflows.

​
Send many independent emails

For up to 50 independent messages in one request, use the batch endpoint. Batch requests are accepted atomically and do not support attachments. See Batch Sending.

​
Next steps

Attachments

Add files or inline assets to an email.

Delivery Status

Understand message states and delivery outcomes.