support

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

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

احراز هویت

یک کلید 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 زنده اجرا می‌کند تا بتوانید پاسخ واقعی را ببینید. این نقطه پایانی را در کنسول 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_fixes`	`boolean`	خیر	Set `false` to diagnose without applying anything. The default applies the safe list, which is the platform's ruled behaviour.

پاسخ

نام	نوع	الزامی	چیست
`complete`	`boolean`	بله	False when any probe could not run.
`blind_probes`	`string[]`	بله	The probes that could not look.
`probes`	`SiteDiagnosticProbe[]`	بله	—
`findings`	`TicketDeflectionFinding[]`	بله	—
`applied`	`string[]`	بله	Remedies applied automatically, by key. Every one is audit-logged.
`refused`	`object[]`	خیر	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…
`recommendations`	`SupportRecommendation[]`	بله	—
`notified`	`integer`	خیر	How many customers were e-mailed. At most one message per finding, ever.
`notify_skipped_not_in_good_standing`	`integer`	خیر	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`	خیر	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…

خطاهایی که این نقطه پایانی می‌تواند برگرداند

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose