Skip to main content
DELETE
Deletes the Target in the authenticated organization’s scope. This is destructive and cannot be undone through the API.

Request

string
required
Target UUID.
No query parameters or body.

Response

204 No Content with an empty body means the Target was deleted. There is no response JSON, data object, or pagination metadata.

Side effects and lifecycle

The service:
  1. Marks this Target’s pending and running ingest jobs as failed with error watch deleted.
  2. Finds members that are exclusive to this Target within the organization and releases their graph audience access.
  3. Deletes the Target. Its watch_members rows cascade from the foreign key, and jobs retain a nullable reference.
People also present on another Target or a custom List are not released from the organization’s graph audience by this operation. Generated Lists are not deleted by this route: their source_watch_id is set to null by the foreign key. Do not assume deleting a Target removes every List-based event-visibility path. The route does not promise deletion of global person/profile data, and it does not delete another Target or its members. There is no soft-delete or undo endpoint. If you need to preserve a Target’s query, call Get target first and save its query.

Examples

Errors and recovery

  • 401 unauthorized, 402 payment_required, and platform-key 400 invalid_request have the shared authentication/access meanings.
  • 404 not_found means the Target was not found in the authenticated organization. A second delete after a successful delete also returns 404; treat that as already absent only if your workflow can safely reconcile it.
  • 429/5xx: do not blindly repeat a destructive request after a timeout. First List targets or Get target. If the Target is absent, the desired state is already reached; otherwise investigate before retrying.

Next