support

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

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

المصادقة

أرسل مفتاح واجهة برمجة التطبيقات (API key) كرمز حامل (bearer token). يجب أن يحمل المفتاح إذن 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

التفاصيل

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 st…
`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 i…

الأخطاء التي يمكن أن تُرجعها نقطة النهاية هذه

401 · 403 · 404 · 422

POST /v1/sites/{siteId}/diagnose