hosting

GET /v1/hosting/fleet-applications

List the applications we install ourselves on our own fleet.

All hosting endpoints

All developer docs →

Authentication

Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.

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, the headless-CMS choice (docs/139) and the PHP applications of the php_app stack: Drupal, Joomla, Moodle, PrestaShop and the rest of the application range (docs/681). 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

NameTypeRequiredWhat it is
stack_type (query)StackTypeNoNarrow to the applications that answer one stack. headless_cms returns the CMS choice and php_app the PHP application choice; nextcloud and owncloud return exactly one…

Response

NameTypeRequiredWhat it is
dataFleetApplication[]Yes—

Errors this endpoint can return

401 · 403 · 429