support

POST `/v1/sites/{siteId}/diagnose`

Run the support AI against one site — check it, fix what is fixable, record the rest.

Hitelesítés

Küldjön egy API-kulcsot bearer tokenként. A kulcsnak rendelkeznie kell a(z) hosting.php.manage jogosultsággal; az ezzel nem rendelkező kulcsok esetén a rendszer 403-as hibát ad vissza 404 helyett.

Ez a végpont nem fogad el szervezeti azonosítót. Az Ön kulcsa már azonosítja azt a szervezetet, amelyhez tartozik, és a válasz is erre vonatkozik.

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 POST https://api.zinndigital.com/v1/sites/{siteId}/diagnose \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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

Runs every diagnostic probe against the named site: whether it is being throttled by its plan's LVE limits (the cause of `508 Resource Limit Is Reached`), whether a `php.ini` value is below what the plan already allows, whether it runs a retired PHP version, and how much of its disk allowance is used. Remedies on the platform's named safe list are then applied — audit-logged and reversible — and everything that cannot be fixed becomes a **recommendation** the customer and staff can both see. ⛔⛔ **A remedy can never grant a limit the plan does not include.** Every one runs through the same customer-band service a person would use, and an application that moved what the site is entitled to is refused rather than reported as applied. ⛔ `complete` is `false` and `blind_probes` names what could not be read. "We found nothing wrong" and "we could not look" are different answers and the client must render them differently. Requires `hosting.php.manage`.

Paraméterek

Név	Típus	Kötelező	Mi ez
`siteId (path)`	`Uuid`	Igen	The site to check.

Kérés törzse

Név	Típus	Kötelező	Mi ez
`apply_fixes`	`boolean`	Nem	Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

Válasz

Név	Típus	Kötelező	Mi ez
`complete`	`boolean`	Igen	False when any probe could not run.
`blind_probes`	`string[]`	Igen	The probes that could not look.
`probes`	`SiteDiagnosticProbe[]`	Igen	—
`findings`	`TicketDeflectionFinding[]`	Igen	—
`applied`	`string[]`	Igen	Remedies applied automatically, by key. Every one is audit-logged.
`refused`	`object[]`	Nem	Remedies that were attempted and refused, with the reason code. `ENTITLEMENT_DRIFT` means the platform detected that a fix would have changed what the site is entitled to and st…
`recommendations`	`SupportRecommendation[]`	Igen	—
`notified`	`integer`	Nem	How many customers were e-mailed. At most one message per finding, ever.
`notify_skipped_not_in_good_standing`	`integer`	Nem	Notifications skipped because the account is suspended or unpaid. ⛔ Counted rather than silently dropped — a skip and a broken emitter look identical otherwise.
`notify_failed`	`integer`	Nem	Notifications that were attempted and raised. ⛔ Its own number: a broken emitter and a quiet run both report `notified: 0`, so a customer who was never told would otherwise be i…

Hibák, amelyeket ez a végpont visszaadhattatlan

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose