domains
POST /v1/domain-watches/{watchId}/mute
Silence a watched domain's alerts without removing it.
Authentication
Send an API key as a bearer token. The endpoint checks domains.watch.manage; 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 POST https://api.zinndigital.com/v1/domain-watches/{watchId}/mute \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'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
⚖️ Owner 2026-08-30: "can be removed at anytime or silenced at least." ⛔ A muted watch is still checked and its history still recorded — only its notifications are suppressed. Skipping the read would leave a hole, so un-muting would produce a burst of "changes" that are simply everything that happened while nobody was listening. Send until: null to un-mute.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
watchId (path) | string | Yes | — |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
until | string | No | Suppress alerts until this instant. null un-mutes. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | string | Yes | — |
fqdn | string | Yes | Normalised lowercase punycode. |
source | string<registered, hosting, manual> | Yes | How it came to be watched. registered — we hold it. hosting — it is attached to a hosting account with us, whoever registered it. manual — the customer added it. ⛔ A domain… |
domain_id | string | No | The Domain row, when the watched name is one of ours. |
site_id | string | No | — |
muted | boolean | Yes | Whether alerts are currently suppressed. |
muted_until | string | No | — |
expires_at | string | No | ⛔ null is "the registry did not say", never "it does not expire". Render it as unknown; a client that treats it as a far-future date shows a customer a reassuring answer we… |
days_until_expiry | integer | No | Whole days, or null when expires_at is unknown. |
registrar | string | No | As the registry reports it. Empty when redacted or not yet read. |
nameservers | string[] | No | — |
status | string[] | No | The EPP status set — clientHold, redemptionPeriod, pendingDelete, … |
last_checked_at | string | No | When the registry last answered. ⛔ Every value on this row is a snapshot of the outside world taken at this instant, so it is never rendered without this beside it (§2.36). |
created_at | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422