hosting
GET /v1/sites/provider-options
List the options available for a new site.
Autentikasi
Kirimkan kunci API sebagai token bearer. Titik akhir ini tidak menyatakan izin tertentu dalam spesifikasi, jadi berikan kunci Anda izin minimum yang diperlukan dan periksa responsnya alih-alih berasumsi.
Tempat ID organisasi Anda dimasukkan
Titik akhir ini menerima org_id sebagai parameter kueri. Kosongkan parameter tersebut dan panggilan ini akan mencakup seluruh subpohon penyewa Anda; kirimkan untuk mempersempit panggilan ke satu organisasi.
ID organisasi Anda berada di layar kunci API di dasbor Anda, di sebelah kunci itu sendiri. Itu adalah ID yang sama dalam setiap panggilan yang Anda buat.
Coba
Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.
curl -X GET https://api.zinndigital.com/v1/sites/provider-options \
-H "Authorization: Bearer zdk_live_…"Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API
Detail
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. On a managed line the CDN answer is `managed: true` with an empty vendor list: the platform spreads Footprint-Free sites across the pool deliberately and does not disclose which vendor fronts a site. `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.
Parameter
| Nama | Jenis | Wajib | Tentang apa ini |
|---|---|---|---|
org_id (query) | Uuid | Tidak | 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 organizat… |
product_line (query) | string | Tidak | 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 | Tidak | 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 authoritati… |
Tanggapan
| Nama | Jenis | Wajib | Tentang apa ini |
|---|---|---|---|
product_line | string | Ya | The product line the answer was computed for (echoed from the query). |
cdn | SiteCdnChoice | Ya | — |
dns | SiteDnsChoice | Ya | — |
stacks | StackType[] | Ya | The `stack_type` values that can actually be provisioned — those with a published blueprint. Every other `StackType` member is a `422` on create. |
sources | SiteSource[] | Ya | 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 w… |
deploy_targets | SiteDeployTargetOffer[] | Ya | 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 appear… |
Kesalahan yang dapat dikembalikan oleh titik akhir ini
401 · 403 · 404