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 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。
このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。
試してみる
アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。
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に対してリクエストが実行されるため、実際のレスポンスを確認することができます。 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