support

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

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

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати hosting.php.manage бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/diagnose \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

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`.

Параметрҳо

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`siteId (path)`	`Uuid`	Бале	The site to check.

Ҷисми дархост

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`apply_fixes`	`boolean`	Не	Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

Ҷавоб

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`complete`	`boolean`	Бале	False when any probe could not run.
`blind_probes`	`string[]`	Бале	The probes that could not look.
`probes`	`SiteDiagnosticProbe[]`	Бале	—
`findings`	`TicketDeflectionFinding[]`	Бале	—
`applied`	`string[]`	Бале	Remedies applied automatically, by key. Every one is audit-logged.
`refused`	`object[]`	Не	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[]`	Бале	—
`notified`	`integer`	Не	How many customers were e-mailed. At most one message per finding, ever.
`notify_skipped_not_in_good_standing`	`integer`	Не	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`	Не	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…

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose