---
title: "Delete an SMS topic"
description: "Archive an SMS topic (a soft delete: subscription records are kept so you can restore it with { \"archived\": false } on Update an SMS topic). `DELETE /api/v1/sms/topics/{id}`"
url: https://www.unitpost.com/docs/sms/delete-sms-topics-id
section: "SMS API reference"
updated: 2026-10-13
---
# Delete an SMS topic

`DELETE /api/v1/sms/topics/{id}`

Archive an SMS topic (a soft delete: subscription records are kept so you can restore it with `{ "archived": false }` on [Update an SMS topic](https://www.unitpost.com/docs/sms/patch-sms-topics-id)). Blocked with `409` while an active SMS campaign or a live automation still uses it. Requires the `topics:write` capability.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | string | yes | — |

## Responses

| Status | Description |
| --- | --- |
| 204 | Archived. |
| 401 | Missing or invalid API key. |
| 403 | Insufficient scope. |
| 404 | SMS topic not found, or SMS is not enabled. |
| 409 | The topic is in use by an active campaign or automation. |

## Example request

```bash
curl -X DELETE 'https://www.unitpost.com/api/v1/sms/topics/top_123' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0'
```

## Links

- HTML reference (with Node.js, Python, Ruby, PHP, Go, Java, Rust, .NET and CLI examples): https://www.unitpost.com/docs/sms/delete-sms-topics-id
- OpenAPI 3.1 (full schemas): https://www.unitpost.com/api/v1/openapi.json