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.The unique identifier for the email.
The date and time at which the object was first created.
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).
The subject line for the email.
The body of the email. Can be either HTML or markdown.
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 URL of the original source of the content.
A primary image to be used when previewing the email on the web or in other contexts.
A human-readable description of the email, used for archives and SEO.
A structured key-value blob that you can use to store arbitrary data on the object.
An informal 'number' for the email, used in some templates ('This was issue #123').
If present, this template overrides your newsletter's default template.
A list of attachment IDs present on the email. (See Attachments for more information.)
A list of email IDs that are related to this email. Related emails are shown at the bottom of the email and archive pages.
Designated whether or not this email should be highlighted within the archives. (Currently unused.)