support
POST /v1/sites/{siteId}/diagnose
Run the support AI against one site — check it, fix what is fixable, record the rest.
Authenticatie
Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie hosting.php.manage beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/diagnose \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
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`.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
siteId (path) | Uuid | Ja | The site to check. |
Aanvraaglichaam
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
apply_fixes | boolean | Nee | Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour. |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
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[] | Nee | 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 | Nee | How many customers were e-mailed. At most one message per finding, ever. |
notify_skipped_not_in_good_standing | integer | Nee | 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 | Nee | 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… |
Fouten die dit eindpunt kan retourneren
401 · 403 · 404 · 422