Skip to Content
SendlySendly
API ReferenceDomains

Remove a sending domain

DELETE
/api/v1/domains/{id}

Remove the domain from the project. Refused with 409 conflict while a template, workflow step or active campaign still sends from an address on this host — repoint those first, or their sends would start failing at SES with nothing here explaining why.

The underlying SES identity is dropped too, unless another project still holds the same host. Its DKIM keys go with it, so re-adding the domain later mints new records that have to be published again.

Requires the domains:write scope — Add and remove sending domains, and trigger verification.

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

Sending domain removed

application/json
  1. response

Acknowledgement that a sending domain was removed.

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