support

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

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

تصدیق‌هویت

یو API کی د بیئرر ټوکن (bearer token) په توګه ولیکئ. کی باید د hosting.php.manage اجازه ولري؛ له دې اجازې پرته کی د 404 پرځای د 403 په واسطه رد کیږي.

دا پای نقطه د سازمان هېڅ آی ډي نه اخلي. ستاسو کیلي مخکې تر مخکې هغه سازمان په ګوته کوي چې پورې اړه لري، او ځواب ورته محدود دی.

هڅه وکړئ

د انګلیسي په زاوي پنسونو کې هرڅه د خپلو ارزښتونو سره بدل کړئ، او د کلي ځای لرونکی ستاسو د ډشبورډ د کلي سره.

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

ننوتي یاست؟ ستاسو په ډشبورډ کې د API کنسول ستاسو د اصلي سازمان ID او ستاسو خپله کیلي ډکوي، او غوښتنه د ژوندی API په وړاندې پرمخ وړي ترڅو تاسو وکولی شئ اصلي ځواب وګورئ. دا پای ټکی (endpoint) د 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