---
title: "Delete Status Page Template"
description: "Deletes a template. Incidents created from it stay as they are."
---

`DELETE /api/status-pages/templates/{id}`

A template pre-fills the form for a new public incident (`kind: incident`) or for an update on a running one (`kind: update`). It publishes nothing by itself; incidents are still created with [Create Manual Incident](/api/monitoring/create-manual-incident).

## Access

Organization `admin` and `editor` with an unrestricted scope: a customer-scoped user or API token gets `403` (`customerScopedTokenForbidden`), because a template belongs to the whole organization. A template of another organization answers `404` (`statusPageTemplateNotFound`). Path ids take the numeric id or the `publicId`. The change is written to the organization's audit log.

## Example (cURL)

```bash
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X DELETE "$BASE_URL/api/status-pages/templates/4" \
  -H "Authorization: Bearer $TOKEN"
```

## Response

`204 No Content`, no body. A second DELETE answers `404`.

## Common errors

- `400 Bad Request` (`invalidIdentifier`) when the id is neither a number nor a UUID
- `404 Not Found` (`statusPageTemplateNotFound`) when the template does not exist or belongs to another organization
- `401 Unauthorized` when you are not logged in
- `403 Forbidden` (`statusPagesModuleDisabled`) when the status pages module is not activated
- `403 Forbidden` (`forbidden`) when your role may not write
- `403 Forbidden` (`customerScopedTokenForbidden`) for a customer-scoped user or token
