hosting
GET /v1/sites/provider-options
List the options available for a new site.
Autentifikacija
Pošaljite API ključ kao bearer token. Ova krajnja točka ne navodi određenu dozvolu u specifikaciji, stoga dajte svom ključu najmanje što mu je potrebno i provjerite odgovor umjesto da pretpostavljate.
Gdje dolazi ID vaše organizacije
Ova krajnja točka uzima org_id kao parametar upita. Izostavite ga i poziv obuhvaćett cijelo stablo vašeg najma; pošaljite ga kako biste suzili poziv na jednu organizaciju.
ID vaše organizacije nalazi se na zaslonu API ključeva u vašoj nadzornoj ploči, pored samog ključa. To je isti ID u svakom pozivu koji uputite.
Isprobajte
Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.
curl -X GET https://api.zinndigital.com/v1/sites/provider-options \
-H "Authorization: Bearer zdk_live_…"Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli
Pojedinosti
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.
Parametri
| Naziv | Vrsta | Obavezno | Što je to |
|---|---|---|---|
org_id (query) | Uuid | Ne | The 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) | string | Ne | The product line the site will be created on. Decides whether the CDN choice is platform-managed; omit for the unmanaged answer. |
cdn_vendor (query) | string | Ne | The 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) | string | Ne | The 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).… |
Odgovor
| Naziv | Vrsta | Obavezno | Što je to |
|---|---|---|---|
product_line | string | Da | The product line the answer was computed for (echoed from the query). |
cdn | SiteCdnChoice | Da | — |
dns | SiteDnsChoice | Da | — |
stacks | StackType[] | Da | The 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_target | string | Da | The deploy target stacks was computed for — where a site created now with the same product_line and subscription_id would be placed. |
sources | SiteSource[] | Da | The 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_targets | SiteDeployTargetOffer[] | Da | The 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,… |
Pogreške koje ova krajnja točka može vratiti
401 · 403 · 404