> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telzino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get, Update, and Delete an Email Template

> Retrieve, partially update, or delete a single email template

## Path Parameters

<ParamField path="templateId" type="string" required>
  The template UUID. Must belong to an organization your account owns.
</ParamField>

## Update (PATCH) — Body Parameters

All fields optional; only the provided fields change.

<Warning>
  `organization_id` and `version` are server-managed and must be **omitted**, not merely left
  unchanged. The request body is validated strictly, so sending either returns
  `400 validation_error`. If you `GET` a template and send the response body straight back,
  strip both fields first.
</Warning>

<ParamField body="name" type="string">Max 100 characters.</ParamField>
<ParamField body="description" type="string">Max 300 characters.</ParamField>

<ParamField body="subject" type="string">
  Max 998 characters. Required to be non-empty when setting `status` to `active`.
</ParamField>

<ParamField body="body_html" type="string">Raw HTML with tokens.</ParamField>
<ParamField body="from_name" type="string">Max 128 characters.</ParamField>

<ParamField body="tags" type="string[]" />

<ParamField body="status" type="string">`draft`, `active`, or `archived`.</ParamField>

<RequestExample>
  ```bash Get theme={null}
  curl https://api.telzino.com/v1/email-templates/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa \
    -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
  ```

  ```bash Activate theme={null}
  curl -X PATCH https://api.telzino.com/v1/email-templates/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa \
    -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{ "status": "active" }'
  ```

  ```bash Delete theme={null}
  curl -X DELETE https://api.telzino.com/v1/email-templates/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa \
    -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  { "data": { "id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa", "status": "active", "version": 2 } }
  ```

  ```json 403 theme={null}
  { "error": "email_templates_locked" }
  ```

  ```json 404 theme={null}
  { "error": "not found" }
  ```

  ```json 409 theme={null}
  { "error": "Only archived templates can be deleted. Archive it first." }
  ```
</ResponseExample>

<Note>
  Deletion is only allowed for `archived` templates that no agent references. If an agent's
  `send_email` tool still points at the template, the request returns `409` naming those agents.
</Note>

<Note>
  A PATCH whose only change is `{"status": "archived"}` is never gated by Feature
  Administration — archiving must always be allowed. Any other content edit (including
  activating) 403s with `email_templates_locked` if the organization's Email Template
  Manager capability is locked.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.