support

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

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

Doğrulama

API açarını bearer token kimi göndərin. Açar hosting.php.manage icazəsinə malik olmalıdır; bu icazəsi olmayan açar 404 deyil, 403 xətası ilə rədd edilir.

Bu endpoint heç bir təşkilat ID-si tələb etmir. Sizin açarınız artıq aid olduğu təşkilatı müəyyən edir və cavab həmin təşkilat üçün məhdudlaşdırılır.

Sınaqdan keçir

Bucaqlı mötərizələrdə olan hór şeyi öz qiymətlərinizlə, açar yertutucusunu isə idarə panelinizdən bir açarla əvəz edin.

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

Sistemə daxil olmusunuz? İdarə panelinizdəki API konsolu real təşkilatınızın identifikatorunu və öz açarınızı avtomatik doldurur, sorğunu canlı API-yə qarşı icra edir ki, siz faktiki cavabı görə biləsiniz. Bu son nöqtəni API konsolunda açın

Təfərrüatlar

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

Parametrlər

Ad	Tip	Tələb olunur	Nədir
`siteId (path)`	`Uuid`	Bəli	The site to check.

Sorğu gövdəsi

Ad	Tip	Tələb olunur	Nədir
`apply_fixes`	`boolean`	Xeyr	Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

Cavab

Ad	Tip	Tələb olunur	Nədir
`complete`	`boolean`	Bəli	False when any probe could not run.
`blind_probes`	`string[]`	Bəli	The probes that could not look.
`probes`	`SiteDiagnosticProbe[]`	Bəli	—
`findings`	`TicketDeflectionFinding[]`	Bəli	—
`applied`	`string[]`	Bəli	Remedies applied automatically, by key. Every one is audit-logged.
`refused`	`object[]`	Xeyr	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[]`	Bəli	—
`notified`	`integer`	Xeyr	How many customers were e-mailed. At most one message per finding, ever.
`notify_skipped_not_in_good_standing`	`integer`	Xeyr	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`	Xeyr	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…

Bu son nöqtənin qaytara biləcəyi xətalar

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose