support
POST /v1/sites/{siteId}/diagnose
Run the support AI against one site — check it, fix what is fixable, record the rest.
Authentifizierung
Senden Sie einen API-Schlüssel als Bearer-Token. Der Schlüssel muss über die Berechtigung hosting.php.manage verfügen; ein Schlüssel ohne diese wird mit 403 statt 404 abgelehnt.
Dieser Endpunkt erfordert keine Organisations-ID. Ihr Schlüssel identifiziert bereits die zugehörige Organisation, und die Antwort ist entsprechend eingeschränkt.
Ausprobieren
Ersetzen Sie alles in spitzen Klammern durch Ihre eigenen Werte und den Platzhalter für den Schlüssel durch einen Schlüssel aus Ihrem Dashboard.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/diagnose \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Angemeldet? Die API-Konsole in Ihrem Dashboard trägt automatisch Ihre echte Organisations-ID sowie Ihren eigenen Schlüssel ein und führt die Anfrage gegen die Live-API aus, sodass Sie die tatsächliche Antwort sehen können. Öffnen Sie diesen Endpunkt in der API-Konsole
Details
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`.
Parameter
| Name | Typ | Erforderlich | Was es ist |
|---|---|---|---|
siteId (path) | Uuid | Ja | The site to check. |
Anfragekörper
| Name | Typ | Erforderlich | Was es ist |
|---|---|---|---|
apply_fixes | boolean | Nein | Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour. |
Antwort
| Name | Typ | Erforderlich | Was es ist |
|---|---|---|---|
complete | boolean | Ja | False when any probe could not run. |
blind_probes | string[] | Ja | The probes that could not look. |
probes | SiteDiagnosticProbe[] | Ja | — |
findings | TicketDeflectionFinding[] | Ja | — |
applied | string[] | Ja | Remedies applied automatically, by key. Every one is audit-logged. |
refused | object[] | Nein | 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[] | Ja | — |
notified | integer | Nein | How many customers were e-mailed. At most one message per finding, ever. |
notify_skipped_not_in_good_standing | integer | Nein | 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 | Nein | 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… |
Fehler, die dieser Endpunkt zurückgeben kann
401 · 403 · 404 · 422