Delete an email template
/v1/email/templates/{template_ref}bird email templates delete <template-ref> --yescurl -X DELETE "https://us1.platform.bird.com/v1/email/templates/{template_ref}" \
-H "Authorization: Bearer $TOKEN"Deletes the template from authoring and lists. The slug becomes available for reuse in the workspace, and the deletion cannot be undone.
Published versions remain readable and previewable when you supply the template ID and version ID, so you can review the original content of a started broadcast. Deletion does not remove access to that published content. The draft is unavailable, and the old slug can refer to a different template after reuse.
A template can't be deleted while a broadcast that has not started sending still uses it, because a scheduled or accepted broadcast has not pinned the content it will send yet. List the broadcasts blocking a template delete to see which ones those are. A broadcast that has already started sending does not block the delete: it pinned its version when it started, so it keeps sending the content it froze.
A template that an active Verify configuration pins as the body of its custom email sender can't be deleted either. The conflict reports only how many verification configurations pin it, directly or for one country, not which; open Verify settings in the dashboard to find the configuration or country sender using it and switch it to Bird's built-in email or another template.
A message scheduled with this template does not block the delete either. It keeps only a reference to the template version until it falls due, so once the template is deleted that message is rejected with generation_failure at its scheduled time and no email is sent.
参数
template_refstringThe template's id (emt_…) or slug. On read, a built-in system template's bird_ slug also resolves here. Write operations (update, delete) accept a workspace template only, because a system template is immutable.