Meta API
GET /api/v1/meta/health
Section titled “GET /api/v1/meta/health”Health
Responses
| Status | Description | Schema |
|---|---|---|
| 200 | Successful Response | any |
GET /api/v1/meta/onboarding
Section titled “GET /api/v1/meta/onboarding”Onboarding
Where setup has got to.
PUBLIC by necessity, so it answers a stranger with the three booleans the
pre-session screens genuinely cannot work without and nothing else:
admin_exists (step 1 of the wizard, and whether this is a fresh
install), complete (the redirect both shell.tsx and the wizard route
make before any session exists) and oidc (whether the login page draws
an SSO button).
host_added and ssh_pending are a different kind of fact: they say
this install manages Proxmox hosts and that a root SSH key is enrolled
but not yet working, which is reconnaissance for anyone who can reach the
port. The wizard only reads them from step 2 onwards, and step 1 signs
the new admin in before it gets there (components/AdminAccountStep.tsx
posts /users then /auth/login), so a session always exists by the time
they matter. Absent rather than faked for everyone else: a hardcoded
False would send a signed-out caller to the wrong wizard step.
Responses
| Status | Description | Schema |
|---|---|---|
| 200 | Successful Response | any |
GET /api/v1/meta/update
Section titled “GET /api/v1/meta/update”Update Status
Responses
| Status | Description | Schema |
|---|---|---|
| 200 | Successful Response | any |
POST /api/v1/meta/update
Section titled “POST /api/v1/meta/update”Apply Update
Request body (required), application/json, proxploy__api__meta__UpdateIn
| Field | Type | Required | Description |
|---|---|---|---|
version | string | yes |
Responses
| Status | Description | Schema |
|---|---|---|
| 202 | Successful Response | any |
| 422 | Validation Error | HTTPValidationError |
GET /api/v1/meta/version
Section titled “GET /api/v1/meta/version”Version
Responses
| Status | Description | Schema |
|---|---|---|
| 200 | Successful Response | any |