Runs examples for real against your account. Test keys only; kept in this tab, never stored on our side. Get a key
ZapSMTP / Docs / Click actions

Delete an action

DELETE/v1/actions/{name}

Delete an action’s declaration. Links that name it keep working: clicks are still tracked and still reach webhooks filtered on it.

Requires a full-access live key; test keys get 403 test_key_restricted.

While links or webhooks still use it, the action stays in the catalogue with declared: false.

Path parameters

namestringrequired
Action name, as written in data-zap-action.

Errors

restricted_api_keyHTTP 403
test_key_restrictedHTTP 403
test-mode keys can send test email and read, not change the account: use a live key
not_foundHTTP 404
action not found (not declared)
DELETE/v1/actions/{name}
curl -X DELETE 'https://zapsmtp.xyz/v1/actions/confirm_order' \
  -H "Authorization: Bearer $ZAP_API_KEY"
Set ZAP_API_KEY in your environment.
Response 200 OK
{
  "object": "action",
  "name": "confirm_order",
  "deleted": true
}