Buttondown Documentation
Emails are why you're here on Buttondown, right? Creating an email via the API is just like creating one in the interface; it will instantly trigger sending actual emails, based on the tags and email type you provide.
Relevant changes to the schema:
included_tags and excluded_tags fields.is_comments_disabled field, and replaced it with a more flexible commenting_mode field.subject field from 1000 to 2000 characters.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.
The date and time at which the object was first created.
A human-readable description of the email, used for archives and SEO.
Designated whether or not this email should be highlighted within the archives.
The unique identifier for the email.
A primary image to be 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. (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 URL of the email, and in the 'slug' field of the email object.)
The subject line for the email.
Reason for suppression, if email is suppressed.
If present, this template overrides your newsletter's default template.