# Delete an email template draft

`DELETE /v1/email/templates/{template_ref}/versions/{version_id}`

Discards the draft's unsaved work: its content resets to what is currently published (or to a single empty language when nothing has been published yet), so the draft matches what sends actually deliver again. Compare each language's `content_hash` against the published version's to see what a discard would throw away.

The draft itself remains, ready for new edits at a bumped `revision`, and what is published never changes. Only the draft can be discarded. Addressing a published version returns a `422` `validation_error`, because published versions are permanent history.

## Code samples

### CLI

```sh
bird email templates versions delete <template-ref> <version-id> --yes
```

### cURL

```sh
curl -X DELETE "https://us1.platform.bird.com/v1/email/templates/{template_ref}/versions/{version_id}" \
  -H "Authorization: Bearer $TOKEN"
```

## Path parameters

- `template_ref` (string): The template's id (`emt_…`) or slug. On read, a built-in `system` template's `bird_` slug also resolves here, to its one permanently published version. Discarding a draft requires a workspace template, because a `system` template has no draft and returns `404` `not_found_error`.
- `version_id` (string)

## Related resources

- [How to build an email template](/learn/email/how-to-build-an-email-template) (video)
- [Email templates](/products/email/templates) (product)
- [Build your first integration](/learn/paths/integration) (course)
- [Email templates](/docs/guides/email/templates) (docs)

[Get an implementation brief](/learn/workspace?topic=email-templates)