hosting

GET /v1/sites/provider-options

List the options available for a new site.

Tüm hosting uç noktaları

Tüm geliştirici belgeleri

Kimlik Doğrulama

Bir API anahtarını bearer token olarak gönderin. Bu uç nokta, teknik özelliklerde belirli bir yetki belirtmemektedir; bu nedenle, varsaymak yerine anahtarınıza ihtiyaç duyduğu en az yetkiyi verin ve yanıtı kontrol edin.

Kurum kimliğinizin yazılacağı yer

Bu uç nokta, org_id parametresini bir sorgu parametresi olarak alır. Bu parametreyi dışarıda bırakırsanız çağrı tüm kiracı alt ağacınızı kapsar; çağrıyı tek bir kuruluşa daraltmak için gönderin.

Kuruluş kimliğiniz (id), kontrol panelinizdeki API anahtarları ekranında, anahtarın hemen yanında yer alır. Yaptığınız her çağrıda aynı kimlik kullanılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

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

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

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.

Parametreler

AdTürZorunluNe olduğu
org_id (query)UuidHayırThe 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)stringHayırThe product line the site will be created on. Decides whether the CDN choice is platform-managed; omit for the unmanaged answer.
cdn_vendor (query)stringHayırThe 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)stringHayırThe 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).…

Yanıt

AdTürZorunluNe olduğu
product_linestringEvetThe product line the answer was computed for (echoed from the query).
cdnSiteCdnChoiceEvet
dnsSiteDnsChoiceEvet
stacksStackType[]EvetThe 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_targetstringEvetThe deploy target stacks was computed for — where a site created now with the same product_line and subscription_id would be placed.
sourcesSiteSource[]EvetThe 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[]EvetThe 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,…

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404