Client area

GET · Diagnostics

Roll up website health for one target

Roll up website health for one target

GET /api/v1/diagnostics/website
R Read
Scope read:hosting

Description

Returns {target, kind:"website", verdict, summary, findings[], signals:{hosting, php, httpd, ssl}, notes}. verdict is the most severe finding (critical|warning|info|ok). Composes get_hosting_account, get_php_settings, get_httpd_config and get_ssl_status; a box-inert signal degrades to a note rather than an error.

Query parameters

Name Type Description
input required string A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.

Responses

The specification does not describe this response body; the note in the rail says what to expect. Every non-2xx response is an RFC 7807 problem with a stable code.

Commonly returned errors

The codes this operation reaches on its own path: the auth stack, its own validation and ownership checks, and the transport. Not a closed set — a shared code from the full registry can still surface. Each links to the code’s own page, the same URL its type dereferences to.

401 No token was presented, or the token is revoked, expired or unknown.
403 The token lacks a required scope, or this account does not own the resource.
404 No such resource for this account.
422 Validation error
429 The rate limit for this token is exhausted. See `Retry-After`.
500 Something went wrong on our side. The failure is logged against `requestId`.
Esc
navigate open Esc close