# (NEW!) Delete Security Template

Permanently delete a security, rights, or access template the authenticated customer owns.

Delete Rules:
- Template must exist for the authenticated customer.
- Deletion is blocked when the template is still referenced: either it has stored dependencies, or it is applied somewhere — for access-template, the count of metadata templates using it; otherwise, the count of assets using it.
- There is no force-delete option. An in-use template can only be removed directly against the database, outside this API.
- On success, the deletion is recorded in tenovos_delete_history for the security-template type.

This action is permanent and cannot be undone.

The user submitting the request must have the Security Template Management admin privilege.

Endpoint: DELETE /security/templates/{templateId}
Version: 1.5
Security: ApiKeyAuth, BasicAuth

## Header parameters:

  - `X-API-Key` (string, required)
    Customer-specific API key required to invoke API.

  - `Authorization` (string, required)
    Provided by Authentication Token creation operation.

## Path parameters:

  - `templateId` (string, required)
    The unique ID of the security template to delete.
    Example: "a9380047-07d7-48aa-b4b7-474d00f0f428"

## Response 401 fields (application/json):

  - `message` (string)

  - `detail` (string)

## Response 403 fields (application/json):

  - `message` (string)

  - `detail` (string)

## Response 404 fields (application/json):

  - `message` (string)

  - `detail` (string)

## Response 409 fields (application/json):

  - `message` (string)

  - `code` (string)
    Enum: "TEMPLATE_IN_USE"

  - `usageCount` (integer)
    Number of objects referencing this template.

  - `usageType` (string)
    What kind of object the usage count reflects. metadata-template for access templates; asset otherwise.
    Enum: "asset", "metadata-template"

  - `dependencies` (array)
    Stored dependency references, when present.


## Response 204 fields