---
title: "List Fleet"
method: GET
path: "/admin/fleet"
tags: ["admin-fleet"]
---

# List Fleet

`GET /admin/fleet`

## Request

- Base URL: `https://app.zeno-works.ch` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zeno-works.ch/admin/fleet`
- Auth: none declared

Which tenants need attention right now, worst first (admin).

One row per real, active tenant — fixtures and deactivated companies are excluded,
because an attention list that includes the e2e seed teaches its reader to skim. Each
row carries a band (blocked / degrading / ok) and the signal that produced it.

Bands rather than a health score on purpose: a number hides its own reasoning, and two
tenants scoring the same can need completely different things. "Blocked" is reserved
for something having *stopped* — a storage connection down, documents failing to
archive — rather than something merely being large, because those are the failures a
customer experiences as the product being broken and usually does not report.

Gated with ``AdminUserInSession`` so the list stays readable from inside a support
session: an operator visiting one tenant still needs to see who else is waiting.

## Headers

- `authorization` string, nullable

## Cookies

- `access_token` string, nullable

## Response `200`

Successful Response

- FleetOut
  - `rows` FleetRowOut[], required
    - `company_id` string, required
    - `company_name` string, required
    - `band` string, required
    - `reason` string, required
    - `held` integer, required
    - `unmatched_bank` integer, required
    - `failed_items` integer, required
    - `broken_connections` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zeno-works/apis/zeno-api.md) · [All operations](https://skmtc.dev/zeno-works/apis/zeno-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zeno-works/apis/zeno-api/revisions/1eb93dde146c?raw)