ai

GET /v1/ai/site-builds/targets

Where a draft can be published, and what is already on each destination.

Всички крайни точки в ai

Упълномощаване

Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението hosting.deploy.manage; ключ без него се отхвърля с 403, а не с 404.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X GET https://api.zinndigital.com/v1/ai/site-builds/targets \
  -H "Authorization: Bearer zdk_live_…"

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

Lists every site the caller may deploy to, and — the part that did not exist before — **what is already there**. Publishing used to take a site id with no way to discover which ids were valid, and no way to learn that a destination had a live business on it. `occupancy` is the field to read, never `known_files`: * `empty` — nothing is deployed. Publishing here destroys nothing. * `ours` — we published the current contents ourselves, from an earlier draft. * `occupied` — something is there and we can read it, because the site has a connected repository. * `unknown` — something may be there and we **cannot** read it. This is deliberately not reported as `empty`: an empty destination is precisely the one where overwriting is safe, so the two must never collapse. A destination we cannot read offers `replace` only, and the customer is told to connect a repository if they want to add to it instead. `allowed_dispositions` is advisory — the screen uses it to decide which buttons to show, and the engine re-derives it when a publication is started. A client that offers a disposition this list omits is refused with `disposition_not_available`. Requires `hosting.deploy.manage`, even though this only reads: the list is "places you may publish to", and offering a destination the caller cannot use both answers the wrong question and discloses sites they may only view.

Параметри

ИмеТипЗадължителноКакво представлява
search (query)stringНеMatch against the destination's primary domain.

Отговор

ИмеТипЗадължителноКакво представлява
targetsSiteMakerTarget[]Да
truncatedbooleanДа`true` when `targets` is a full page and more destinations exist beyond it. The list is ordered by hostname and capped, so a site that sorts past the cap is absent rather than l…
dispositionsobject[]ДаThe catalogue, so a client never hardcodes the choices and adding one cannot leave a stale copy behind.

Грешки, които този крайpoint може да върне

401 · 403 · 429