Retrieve Email
Retrieve a specific email by its ID
Path parameters
Response
OK
A unique TypeID associated with the object.
The date and time at which the object was first created.
The canonical web URL of the email on the newsletter's archive.
A list of callouts that apply to this email — surfaced in the UI alongside analytics to flag context the reader should know about (e.g., first send on a custom sending domain).
A list of attachment IDs present on the email. (See Attachments for more information.)
The body of the email, in either HTML or markdown format. Buttondown attempts to intelligently detect the format of the body automatically, but you can also specify the format explicitly by prepending the text with the buttondown-editor-mode comment: <!-- buttondown-editor-mode: fancy --> or <!-- buttondown-editor-mode: plaintext -->.
The URL of the original source of the content.
Governs who can comment on this email.
This enum replaces the is_comments_disabled field, which has been deprecated. (Also note that this field may be superseded by newsletter-level settings; for instance, "enabled" is an invalid and inert value if the newsletter itself has comments disabled.)
A human-readable description of the email, used for archives and SEO.
Governs who can view this email in the archive.
Represents the audience of an email, and to whom it is visible both in the initial email and in online archives.
Designated whether or not this email should be highlighted within the archives.
A primary image URL used when previewing the email on the web or in other contexts.
A structured key-value blob that you can use to store arbitrary data on the object. Metadata can be nested — you can store objects and arrays within your metadata. (You can read more about metadata.)
The date and time at which the object was last modified.
The date and time at which the email should be published in the future (for scheduled emails), or the date and time at which the email was published (for sent emails).
A list of email IDs that are related to this email. Related emails are shown at the bottom of the email and archive pages.
An informal 'number' for the email, used in some templates ('This was issue #123').
Whether this email should trigger pay-per-email billing for paid subscribers. Use this to differentiate between free updates and premium newsletters.
A short, human-readable identifier for the email, used in the archive URL.
Represents the original provenance of an email. This value is not exposed to subscribers, but does determine some behavior of the email (e.g. whether or not analytics can be calculated.)
Represents the state of an email.
No action is required to move from one state or another; Buttondown internally handles the transitions, and exposing the status is for observability purposes only.
The subject line for the email.
Represents the reason an email was suppressed.
Represents the template of an email.
Each template has a different layout/style; you can view screenshots and examples in the docs.