hosting

GET /v1/sites/provider-options

List the options available for a new site.

모든 hosting 엔드포인트

모든 개발자 문서

인증

Bearer 토큰으로 API 키를 전송하세요. 이 엔드포인트는 명세에 특정 권한을 명시하지 않으므로, 가정하기보다는 키에 필요한 최소한의 권한을 부여하고 응답을 확인하세요.

조직 ID가 들어가는 위치

이 엔드포인트는 org_id을(를) 쿼리 매개변수로 사용합니다. 생략하면 테넌트 하위 트리 전체가 호출 대상이 되며, 값을 전달하면 특정 조직으로 호출 범위를 좁힐 수 있습니다.

조직 ID는 대시보드의 API 키 화면에서 키 바로 옆에 있습니다. 이는 실행하는 모든 호출에서 동일한 ID입니다.

무료 체험하기

대괄호 안에 있는 모든 내용을 사용자 지정 값으로 바꾸고, 키 플레이스홀더는 대시보드의 키로 바꾸세요.

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

로그인하셨나요? 대시보드의 API 콘솔이 실제 조직 ID와 본인의 키를 자동으로 채우고 라이브 API를 대상으로 요청을 실행하므로 실제 응답을 확인할 수 있습니다. API 콘솔에서 이 엔드포인트를 여세요

상세 정보

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.

매개변수

이름유형필수설명
org_id (query)Uuid아니요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아니요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아니요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아니요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).…

응답

이름유형필수설명
product_linestringThe product line the answer was computed for (echoed from the query).
cdnSiteCdnChoice
dnsSiteDnsChoice
stacksStackType[]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_targetstringThe deploy target stacks was computed for — where a site created now with the same product_line and subscription_id would be placed.
sourcesSiteSource[]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_targetsSiteDeployTargetOffer[]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,…

이 엔드포인트가 반환할 수 있는 오류

401 · 403 · 404