We currently do not support sending attachments when using our batch
endpoint.
Send attachments from a remote file
Include thepath
parameter to send attachments from a remote file. This parameter accepts a URL to the file you want to attach.
Define the file name that will be attached using the filename
parameter.
Send attachments from a local file
Include thecontent
parameter to send attachments from a local file. This parameter accepts the Base64 encoded content of the file you want to attach.
Define the file name that will be attached using the filename
parameter.
Embed Images using CID
You can optionally embed an image in the HTML body of the email. Both remote and local attachments are supported. All attachment requirements, options, and limitations apply to embedded inline images as well. Embedding images requires two steps: 1. Add the CID in the email HTML. Use the prefixcid:
to reference the ID in the src
attribute of an image tag in the HTML body of the email.
content_id
parameter in the attachment object (e.g. content_id: "logo-image"
).
The ID is an arbitrary string set by you, and must be less than 128 characters.
Learn more about embedding images.
Attachment Limitations
- Emails can be no larger than 40MB (including attachments after Base64 encoding).
- Not all file types are supported. See the list of unsupported file types.
- Emails with attachments cannot be scheduled.
- Emails with attachments cannot be sent using our batching endpoint.
All attachments (including inline images) do not currently display in the
emails dashboard when previewing an email’s HTML.