connections

GET /v1/waap/domains

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

Barcha connections yakuniy nuqtalari

Autentifikatsiya

API kalitini bearer token sifatida yuboring. Ushbu yakuniy nuqta spetsifikatsiyada ma'lum bir ruxsatni ko'rsatmaydi, shuning uchun kalitingizga eng kam kerakli huquqni bering va taxmin qilish o'rniga javobni tekshiring.

Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.

Sinab ko'rish

Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.

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

Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching

Tafsilotlar

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.

Javob

NomiTuriMajburiyNima bu
domainsWaapDomain[]Ha

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

401 · 429