hosting

GET /v1/sites/provider-options

List the options available for a new site.

Všechny koncové body hosting

Všechny dokumenty pro vývojáře

Autentizace

Odešlete klíč API jako bearer token. Tento koncový bod ve specifikaci uvádí specifické oprávnění, takže svému klíči udělte to nejmenší možné a místo předpokladů zkontrolujte odpověď.

Sem patří ID vaší organizace

Tento koncový bod přijímá org_id jako parametr dotazu. Pokud ho vynecháte, volání pokryje celý podstrom vašeho nájemce; jeho odesláním volání zúžíte na jednu organizaci.

ID vaší organizace najdete na obrazovce API klíčů ve vašem přehledu, hned vedle samotného klíče. Je to stále stejné ID v každém volání, které provedete.

Vyzvednout

Nahraďte cokoli v závorkách vlastními hodnotami a zástupný symbol klíče klíčem z vašeho řídicího panelu.

curl -X GET https://api.zinndigital.com/v1/sites/provider-options \
  -H "Authorization: Bearer zdk_live_…"

Přihlášeni? Konzole API ve vašem dashboardu automaticky doplní vaše skutečné ID organizace i váš vlastní klíč a odešle požadavek na živé API, abyste viděli reálnou odpověď. Otevřete tento koncový bod v konzoli API

Podrobnosti

What a customer may choose on POST /v1/sites: cdn_vendor / dns_vendor, stack_type and source. The vendors are answered from the provider-account pool serving this organization — its own (BYO) accounts when it has any, otherwise the platform pool — so the picker can never offer a vendor the site would then fail to provision on. The CDN answer is managed: false on every line today, Footprint-Free included (owner ruling, 2026-09-09): the customer picks the vendor and the platform picks the account, spreading their sites across the pool without disclosing which account any of them landed on. separates_sites says whether a given vendor can deliver that spread at all, and dns.allowed_by_cdn carries the whole CDN→DNS pairing rule so the picker can re-filter without another request. stacks and sources answer the same question for the other two pickers — only what this deployment can actually build. Note there is deliberately no runtime: it is derived from the stack, not chosen.

Parametry

NázevTypPožadovánoCo to je
org_id (query)UuidNeThe organization to answer for. Defaults to the caller's first org in scope; an org outside scope is a 404 rather than a 403, so this cannot be used to probe which…
product_line (query)stringNeThe product line the site will be created on. Decides whether the CDN choice is platform-managed; omit for the unmanaged answer.
cdn_vendor (query)stringNeThe CDN the customer has chosen, which narrows the DNS answer. Choosing Cloudflare restricts DNS to Cloudflare: its edge proxies a record in place inside its own authoritative…
subscription_id (query)stringNeThe subscription the site will be created under, exactly as createSite takes it. Its plan decides the deploy target, and the target decides which stacks can run (#6071).…

Odpověď

NázevTypPožadovánoCo to je
product_linestringAnoThe product line the answer was computed for (echoed from the query).
cdnSiteCdnChoiceAno
dnsSiteDnsChoiceAno
stacksStackType[]AnoThe stack_type values that can actually be provisioned on stack_target — those with a published blueprint AND runnable where the plan places the site. The vendor one-click…
stack_targetstringAnoThe deploy target stacks was computed for — where a site created now with the same product_line and subscription_id would be placed.
sourcesSiteSource[]AnoThe source values a site can actually be built from. migrate and wayback appear only where the import workflows are deployed; elsewhere offering them would create a site…
deploy_targetsSiteDeployTargetOffer[]AnoThe edge hosts this organization can point a new site at — its own connected provider accounts, sold through the extra-externally-hosted-sites add-on. Every edge host appears,…

Chyby, které může tento koncový bod vrátit

401 · 403 · 404