support

POST /v1/sites/{siteId}/diagnose

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

Всички крайни точки в support

Всички документи за разработчици

Упълномощаване

Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението hosting.php.manage; ключ без него се отхвърля с 403, а не с 404.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

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

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в 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_fixesbooleanНеSet false to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

Отговор

ИмеТипЗадължителноКакво представлява
completebooleanДаFalse when any probe could not run.
blind_probesstring[]ДаThe probes that could not look.
probesSiteDiagnosticProbe[]Да
findingsTicketDeflectionFinding[]Да
appliedstring[]ДаRemedies applied automatically, by key. Every one is audit-logged.
refusedobject[]Не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…
recommendationsSupportRecommendation[]Да
notifiedintegerНеHow many customers were e-mailed. At most one message per finding, ever.
notify_skipped_not_in_good_standingintegerНеNotifications skipped because the account is suspended or unpaid. ⛔ Counted rather than silently dropped — a skip and a broken emitter look identical otherwise.
notify_failedintegerНе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…

Грешки, които този крайpoint може да върне

401 · 403 · 404 · 422