Dugble supports attachments on individual email sends. Attachment content must be provided as Base64-encoded data.
Attachment fields
Each attachment can include:
filename — required name shown to the recipient.content — required Base64-encoded file content.content_type — optional MIME type, such as application/pdf.content_id — optional identifier for inline content referenced from HTML.
Attachment paths and remote URLs are not supported. Provide Base64 content directly in the request.
Example
Size limit
The combined decoded size of all attachments in one email can be up to 7 MB. Dugble rejects requests that exceed this limit.
Base64 increases the size of data on the wire, so account for the encoded payload size when building requests.
Inline content
Use content_id when an attachment should be referenced inside the HTML body, for example for an embedded image.
The corresponding attachment uses the same identifier:
Batch sending
Attachments are not supported by POST /emails/batch. Send messages with attachments individually using POST /emails.
