Skip to Content
SendlySendly
API ReferenceSegments

Delete a segment

DELETE
/api/v1/segments/{id}

Delete a segment. Refused with 409 while any DRAFT, SCHEDULED, or SENDING campaign still targets it — deleting it would leave those campaigns pointing at an audience that no longer exists, and the failure would surface at send time instead of here. Remove the segment from those campaigns first.

Requires the segments:write scope — Create, edit, and delete your segments.

headerAuthorizationBearer <API Key>

API key authentication. Use a sk_* (FULL) or pk_* (SENDING_ONLY) key as the bearer token. Public keys (pk_*) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by /api/v1/* operations): FULL keys hold every scope; SENDING_ONLY keys hold only emails:send.

id*string

Resource id.

Formatuuid

Response Body

Segment deleted

application/json
  1. response

Acknowledgement that a segment was deleted.

id*string
Formatuuid
deleted*true
Value intrue
Example Request
curl -X DELETE 'https://api.sendly.now/api/v1/segments/497f6eca-6276-4993-bfeb-53cbbbba6f08'
Example Response
{  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "deleted": true}