hosting

GET /v1/hosting/fleet-applications

List the applications we install ourselves on our own fleet.

Gbogbo àwọn hosting endpoints

Ìfàṣẹ́pọ̀

Fi bọ́kì kọ́kọ́ (bearer token) ránṣẹ́ gẹ́gẹ́ bí àmì ìdánimọ̀ API. Ibùdó yìí kò sọ àṣẹ pàtó kan nínú àlàyé rẹ̀, nítorí náà fún kọ́kọ́ rẹ̀ ní ohun tó kéré jù lọ tí ó nílò kí o sì ṣàyẹ̀wò ìdáhùn náà dípò kí o kàn rò ó.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X GET https://api.zinndigital.com/v1/hosting/fleet-applications \
  -H "Authorization: Bearer zdk_live_…"

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

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.

Àwọn ìpìlẹ̀

OrúkọIruTí a nílòKini o jẹ
stack_type (query)StackTypeBẹẹkọ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…

Idahun

OrúkọIruTí a nílòKini o jẹ
dataFleetApplication[]Bẹẹni

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403 · 429