POST /v1/domain-alerts/searches

Authentication

Send an API key as a bearer token. The endpoint checks sites.create; 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-alerts/searches \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "params": <object> }'

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

params are the aged-domain list's query parameters exactly as the list sent them (q, tld, language, category, min_/max_ for dr, da, tf, cf, rd, uniques, added_year, price, and the flags indexed, wiki, gnews); sort and anything else is ignored. Saving takes a baseline — the domains matching now are not announced. A blank name is built from the filters. 422 when no filter is set, the name is blank after trimming, the same active search exists, or the account's active searches are already at its allowance (pause one or choose a plan with more).

Request body

Response

Errors this endpoint can return

400 · 401 · 403 · 404 · 422