connections

GET /v1/waap/domains

Domains protected by the organisation's WAAP account, and what the policy did.

Vituo vyote vya connections

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

curl -X GET https://api.zinndigital.com/v1/waap/domains \
  -H "Authorization: Bearer zdk_live_…"

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

Web application and API protection on the customer's own account. ⛔⛔ **`mode` is mandatory reading and no client may render a domain as "protected" without it.** `monitor` evaluates every rule, logs every match and **delivers the traffic anyway** — it produces analytics, shows threats detected, and blocks nothing. On a dashboard it is indistinguishable from `block` unless the mode is shown. `locked` is a fourth state the **provider** assigns (usually for billing) and the customer cannot change; it is not a mode they chose and a toggle will not clear it. ⛔ `total_requests` and `blocked_requests` are `null` when the provider does not report them — never `0`. "Nothing was blocked" and "we cannot see what was blocked" are opposite answers.

Majibu

JinaAinaInayohitajikaKilicho hiki
domainsWaapDomain[]Ndiyo

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 429