Skip to main content
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 takes it out of service reversibly instead.

​
Request

curl

​
Parameters

​
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 for the full error contract.

Signal tasks

All signal operations

List signals

Use includeArchived=true to see archived signals

Update signal

Change metadata and access records

Signal overview

Fields, lifecycle, and concepts