Delete Lead List

curl --request DELETE \
  --url https://api.example.com/api/v1/entities/leadlists/{id} \
  --header 'Authorization: Bearer <token>'

(No content)

DELETE

api

entities

leadlists

{id}

Delete Lead List

curl --request DELETE \
  --url https://api.example.com/api/v1/entities/leadlists/{id} \
  --header 'Authorization: Bearer <token>'

(No content)

Permanently deletes a lead list by its unique identifier. This action cannot be undone.

Authentication

This endpoint requires authentication. Only users with access to the lead list (or admin users) can delete it.

This operation is irreversible. The lead list and its associations will be permanently removed. The underlying persons or companies are not deleted.

string (UUID)

required

The unique identifier of the lead list to delete.

Returns an empty response with status code 204 No Content on successful deletion.

(empty)

void

No response body is returned on successful deletion.

(No content)

Status Code	Error Code	Description
403	`FORBIDDEN`	User does not have access to this lead list. Only users in `userIds` or admins can delete the list.
404	`NOT_FOUND`	No lead list exists with the specified ID.
500	`INTERNAL_ERROR`	An unexpected server error occurred.

Access Control: Only users whose ID is in the userIds array can delete the lead list.
Admin Override: Users with the admin role can delete any lead list regardless of userIds.

Deleting a lead list does not delete the associated persons or companies. Only the list itself and its ID associations are removed.
If you need to archive a list instead of permanently deleting it, consider implementing a soft-delete mechanism or moving the list to an archive state.