GET /v1/alerts

Hitelesítés

Küldjön egy API-kulcsot bearer tokenként. Ez a végpont nem határoz meg konkrét jogosultságot a specifikációban, ezért adja meg a kulcsnak a legkevesebbet, amire szüksége van, és a feltételezés helyett ellenőrizze a választ.

Próbálja ki

Cserélje ki a hegyes zárójelek közötti részt a saját értékeivel, a kulcshelyőrzőt pedig a vezérlőpultján található kulccsal.

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

Be van jelentkezve? A vezérlőpultban lévő API-konzol kitölti a valós szervezetazonosítóját és a saját kulcsát, és a kérést az éles API-n futtatja, hogy láthassa a tényleges választ. Nyissa meg ezt a végpontot az API konzolban

Részletek

docs/87. What the bell in the dashboard header reads. ⚖️ Owner ask 2026-08-26: "maybe have an alerts bit somewhere like the other hosting platfroms do that has like an ! when something is open and then a list of them, like in other enterprise apps type of thing." Unions seven sources: the customer's live notices (maintenance, DNS drift, a lost delegation, a paused posting run, a stranded card, a new PHP build, a certificate lapsing), an expired or expiring stored card, a past-due subscription, domains expiring without auto-renew or already lapsed, suspended / restricted / quarantined sites and orgs, any supplier we depend on reporting degraded or out, our own published open incidents and announced windows, and sites with malware on them. ⛔ The last two are each deliberately distinct from the one before it. incidents is not upstream — that reports a supplier being unwell, this reports Zinn®, and a customer whose site is slow wants the second far more. security is not the suspended/restricted/quarantined family — those are enforcement outcomes and the site is already off, where an infected site inside its grace window is still serving and the customer can still act. A site that is both appears in both, and that is deliberate: the second alert is the reason for the first. ⛔ No permission key — being told your card has expired is not a privilege. Gating it would mean a member whose role lacks org.read silently never learns their sites are suspended. ⛔⛔ This shipped in the same change that stopped platform notices bannering on every page. Landing that alone would have made maintenance unreachable from /sites rather than merely quieter — a false all-clear with nothing red (§2.44). A banner policy without a bell is not a smaller feature, it is a worse one. ⛔ The header calls this on every page, so it is seven bounded queries against indexed columns and reaches no vendor (§2.16). Every count that could be per-site is a grouped aggregate returning ONE row, so an estate with 40,000 suspended or infected sites produces one alert saying so rather than 40,000.

Paraméterek

Válasz

Hibák, amelyeket ez a végpont visszaadhattatlan

401 · 429