support

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

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

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na hosting.php.manage; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

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

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

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

Mga Parameter

Pangalan	Uri	Kailangan	Ano ito
`siteId (path)`	`Uuid`	Oo	The site to check.

Katawan ng kahilingan

Pangalan	Uri	Kailangan	Ano ito
`apply_fixes`	`boolean`	Hindi	Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

Tugon

Pangalan	Uri	Kailangan	Ano ito
`complete`	`boolean`	Oo	False when any probe could not run.
`blind_probes`	`string[]`	Oo	The probes that could not look.
`probes`	`SiteDiagnosticProbe[]`	Oo	—
`findings`	`TicketDeflectionFinding[]`	Oo	—
`applied`	`string[]`	Oo	Remedies applied automatically, by key. Every one is audit-logged.
`refused`	`object[]`	Hindi	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[]`	Oo	—
`notified`	`integer`	Hindi	How many customers were e-mailed. At most one message per finding, ever.
`notify_skipped_not_in_good_standing`	`integer`	Hindi	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`	Hindi	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…

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose