delete_v1_marketing_suppressions
Re-subscribes an address on one channel and answers 204.
Re-subscribes an address on one channel and answers 204. An address that is not on the list reads as not found.
| Tool | delete_v1_marketing_suppressions |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | DELETE /v1/marketing/suppressions |
| Product | marketing |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
address | string | — | — | — | Address is the recipient, normalized (lower-cased, trimmed) so an opt-out cannot be slipped past on a case or whitespace difference. Required. |
channel | string | — | — | — | Channel is the surface opted out of: email, sms, social, meta, google or tiktok. Empty means email. Opting out of one leaves the others reachable. |
createdAt | integer | — | — | — | CreatedAt is unix seconds, server-assigned. |
reason | string | — | — | — | Reason is a free-text note, capped at 1024 bytes. The public one-click endpoint records "one-click unsubscribe". |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "delete_v1_marketing_suppressions",
"arguments": {
"address": "<address>",
"channel": "<channel>",
"createdAt": 0,
"reason": "<reason>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. createdAt holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
delete_v1_marketing_suppressions | DELETE /v1/marketing/suppressions | marketing | Re-subscribes an address on one channel and answers 204. |
The same capability over plain HTTP is in the marketing API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?