> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Delete signal
> Soft-delete (archive) a signal and its access records
`DELETE /api/v2/storefront/signals/{signalId}`
Soft-deletes a signal and all of its access records. The signal is archived, not permanently removed — it stops appearing in list and get results unless `includeArchived` is set.
**This cascades into buyer targeting.** Archiving a signal also archives every
custom-signals targeting profile that references it, whether the signal sat in
that profile's include or its exclude set. Any buyer targeting built on this
signal stops working. Archiving is also one-way: a repeat `DELETE` returns `404`
because the signal is no longer visible, and there is no un-archive call. Check
what depends on the signal first — setting `isLive: false` via
[Update signal](/v2/storefront/signals/tasks/update-signal) takes it out of
service reversibly instead.
## Request
```bash curl theme={null}
curl -X DELETE https://api.apostra.com/api/v2/storefront/signals/acme_high_value_customers \
-H "Authorization: Bearer $SCOPE3_API_KEY"
```
## Parameters
| Field | Type | Required | Notes |
| ---------- | ------ | -------- | ------------------------ |
| `signalId` | string | Yes | Signal identifier (path) |
## Response
`204 No Content` — the signal and its access records are archived. The response body is empty.
## Errors
* `404 NOT_FOUND` — no signal with that `signalId` is visible to the authenticated account.
* `401 UNAUTHORIZED` — missing or invalid bearer token.
See [Errors](/v2/reference/errors) for the full error contract.
## Related
All signal operations
Use `includeArchived=true` to see archived signals
Change metadata and access records
Fields, lifecycle, and concepts