These sample requests are autogenerated by the OpenAPI spec. This endpoint requires one or more parameters in the URL: those are offset in curly-braces.
The IDs and values referenced in these responses are fake; please only rely on these responses for overall structure.
All parameters are optional unless explicitly specified.
A list of attachment IDs present on the email. (See Attachments for more information.)
[
"att_01h8xg4j3k2m1n0p9q8r7s6t5v"
]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). Pass "none" to clear a scheduled date.
The subject line for the email.
"The subject line for the email"A human-readable description of the email, used for archives and SEO.
The URL of the original source of the content.
"https://sheinhardtwig.com/2025/01/17/our-nbc-partnership"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 -->.
"This is an example of the body of an email."Controls who can view this email in the archive.
This email is visible in the archive to everyone, but is not email content (e.g. an imported blog post) and is never sent or shown in email-rendering contexts.
This email is not visible in the archive.
This email is visible in the archive to everyone.
This email is visible in the archive to paid subscribers only.
This email is visible in the archive to subscribers only.
The type of email. Defaults to PUBLIC. Deprecated: this is a legacy single-axis view derived from archival_mode (archive visibility) and filters (audience); prefer setting those directly. Because it is derived, it does not always round-trip: writing it alongside an explicit archival_mode that disagrees will report the value implied by the two underlying fields, and writing a value that already matches the derived one is a no-op.
Public emails are sent out to all of your subscribers and are available in your web archives.
Private emails are sent out to all of your subscribers but are not viewable in your web archives.
Free emails are sent out only to subscribers who are not paying for your newsletter (so you can send specific emails to convince them to pay, for instance!)
Emails sent specifically to subscribers who were previously premium but have since churned.
Emails that are only available in the archive and not sent to subscribers.
The status of the email (e.g. draft, about_to_send, sent, scheduled).
Draft emails are only visible to you and are not sent out to subscribers.
This email was created by an external feed, and has not yet been finalized and sent out by Buttondown.
This email has been queued to send out to subscribers, and will be sent automatically within a few minutes.
If you're seeing that an email you just sent out is 'stuck' here, worry not — Buttondown sometimes takes a little bit longer to send out emails to ensure deliverability, but once it's marked as 'about to send' it will get sent out.
This email has been scheduled to send out to subscribers at a specific time. This specific time is available on the email as its publish_date.
This email is currently being sent out to subscribers, and is visible in your web archives if enabled.
Some emails, especially those with large subscriber lists, may take a while to send out — Buttondown sends emails out in batches to ensure deliverability, so if you're seeing an email 'stuck' here, it's because our systems have detected that that's the optimal way to reach your subscribers.
This email has been paused, and is not visible in your web archives. If it is not resumed within seven days, it becomes a draft, sent, or partially sent email.
This email has been deleted, and is no longer visible in your web archives.
This email has encountered an error while sending out to subscribers, and is not visible in your web archives.
This email has been sent out to subscribers, and is visible in your web archives if enabled.
This email was paused while sending and was not resumed within seven days, so only some subscribers received it. It is not visible in your web archives.
This email was imported from another service, and is visible in your web archives if enabled.
This email is in the process of being sent out, but is being intentionally sent slowly to ensure deliverability.
This email is in the process of automatically being resent to subscribers by Buttondown's systems in order to make sure all subscribers have received it.
This email is a transactional email used by a core workflow in your newsletter or Automations, and is not visible in your web archives nor sent out to subscribers.
This email has been suppressed and is not visible to subscribers.
If the email has been suppressed from sending, the reason why.
Used for communications with law enforcement agencies regarding legal inquiries or data requests.
Used for internal auditing and compliance-related communications.
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.)
A primary image URL used when previewing the email on the web or in other contexts.
A short, human-readable identifier for the email, used in the archive URL.
"hello-world"An informal 'number' for the email, used in some templates (e.g. 'This was issue #123').
If present, this template overrides your newsletter's default email template. Pass "none" to clear an override.
A plaintext template that puts emphasis on your content.
Your own HTML template, wrapped around every email's content.
The default email template.
A plaintext (like, literally plaintext, no HTML at all) template for the truly minimalist.
The email body itself is used as the template, with no outside scaffolding provided by Buttondown.
Controls whether subscribers can comment on this email.
Commenting is disabled for this email.
Commenting is enabled for this email.
Commenting is enabled for paid subscribers only.
IDs of emails related to this one. Shown at the bottom of the email and archive pages.
[
"em_01h8xg4j3k2m1n0p9q8r7s6t5v"
]Designated whether or not this email should be highlighted within the archives.
Whether this email should trigger pay-per-email billing for paid subscribers. Use this to differentiate between free updates and premium newsletters.