DELETE /sms/conversations/{line}/{number}
Delete a conversation
| Scope | messages:write |
| Role permission | Phone numbers — line must be one of theirs |
| Cost | Free |
PERMANENT. Every message in the thread is destroyed and there is no recovery through this API.
Additionally gated by the account's restrict deleting SMS setting.
Holding messages:write does not override it — that setting exists
precisely so an account owner can stop their own staff and integrations
from destroying message history. A restricted account gets 403.
Path parameters
| Name | Type | Required | Example | Description |
|---|---|---|---|---|
line | string | yes | 12125550188 | One of your account's numbers — the line the thread is on. Digits. |
number | string | yes | 13475550123 | The other party's number. Digits. |
Responses
204
Deleted.
Errors
| Status | Meaning |
|---|---|
400 | invalid_request — a missing or malformed field, an unknown enum value, or an unknown field in the body. Nothing was charged. |
401 | unauthenticated — no credential, or one that is invalid, revoked or expired. The WWW-Authenticate header names the scope the endpoint wanted. |
403 | Two different failures share this status, and the type tells them apart: |
500 | internal_error — something failed on our side. For a send, nothing was charged, guaranteed, which is what makes a retry safe. |
See Errors for the full catalog and what to do about each.
Example
curl -X DELETE 'https://api.account.telebroad.com/api/public/v1/sms/conversations/12125550188/13475550123' \
-H "Authorization: Bearer $TB_KEY"