Get Platform Status

GET /system/status

What a customer sees when their runs stopped working.

Public, because a status page behind a login is a status page nobody can read during the incident it exists for. That constrains the content rather than the access: see :class:PlatformStatus on why there is not a single number in it.

Four components, and the second and third are the reason this endpoint exists at all. /system/health answers “is this process alive”, which is true of an API in front of a dead fleet and an unreachable aggregator — precisely the two outages a customer feels and the API cannot see from inside itself.

No credential

This operation is public: it authenticates by its own mechanism — a webhook signature or a channel token — rather than by a platform credential.

Responses

Status	Description	Body
200	Successful Response	PlatformStatus

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/system/status

Response — PlatformStatus

Field	Type		Notes
status	string	required	—
components	ComponentStatus[]	required	—
checked_at	string (date-time)	required	—