DELETE /v1/mail/services/{mailServiceId}

Authentication

Send an API key as a bearer token. The key must carry the mail.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X DELETE https://api.zinndigital.com/v1/mail/services/{mailServiceId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Moves the service to deleting; teardown then runs asynchronously. Idempotent — a service already removed returns 204. Requires mail.manage. When we published the domain's mail DNS records, removing the service also removes them in the background: every record we recorded publishing, including a DKIM key an earlier setup wrote, but only while it still holds the value we published, only in the zone the domain is delegated to, and each removal confirmed at the domain's own nameservers. A foreign MX and any record someone changed are left alone, and an SPF record another sender was added to keeps everything except our own include.

Parameters

Errors this endpoint can return

401 · 403 · 404 · 409 · 429