hosting
GET /v1/hosting/fleet-applications
List the applications we install ourselves on our own fleet.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/hosting/fleet-applications \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The own-fleet counterpart of `GET /v1/hosting/applications`, and deliberately a separate operation rather than a flag on it, because the two answer different questions from different authorities. That one reports what the **resold platform's** installer offers and is read live from the vendor. This one reports what **we** have written an installer for, which is a fact about this platform at this release — Nextcloud, ownCloud, and the headless-CMS choice (docs/139). Authenticated but not tenant-scoped: like the locations and applications endpoints it is a statement about what this platform sells, and the create-site form needs it at the one moment no site exists to read it from.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
stack_type (query) | StackType | No | Narrow to the applications that answer one stack. `headless_cms` returns the CMS choice; `nextcloud` and `owncloud` return exactly one entry each, because for those the stack *i… |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | FleetApplication[] | Yes | — |
Errors this endpoint can return
401 · 403 · 429