bird email templates
Usage
Code example
bird email templatesDescription
A template owns a permanent handle and one editable draft. Editing the draft never
changes what sends: only submitting it freezes the version a send serves. Sending by
template lives on email send, whose --template takes the handle or an emt_ id.
Reads return JSON; list is paginated. Mutations take flags and/or a --body-file JSON body (flags overriding); run --example to print the body shape or --dry-run to preview the request. Destructive commands require --yes.
Commands
| Name | Description |
|---|---|
| broadcasts | List the broadcasts blocking a template delete |
| create | Create an email template and its first editable draft |
| delete | Delete an email template |
| duplicate | Duplicate an email template |
| get | Get an email template |
| list | List email templates |
| preview | Preview a template with sample values |
| update | Update an email template |
| versions | Submit, read, and roll back template versions |
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Watch the guideHow to build an email templateExplore the capabilityEmail templatesFollow the learning pathBuild your first integrationImplementation guideEmail templates
Try the practice and get an implementation brief