public

GET /v1/public/order/config/{planCode}

Everything a buyer configures for one plan, in one call.

Всички крайни точки в public

Всички документи за разработчици

Упълномощаване

Този крайpoint е публичен. Той не изисква данни за удостоверяване и организация — това е съдържанието, което нашият собствен маркетинг сайт и AI машини за отговори четат.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X GET https://api.zinndigital.com/v1/public/order/config/{planCode}

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

Owner ruling 2026-09-09, on a competitor's order flow: "when you buy something it has a clear config page for that hosting where all the options reside nice and neatly including the domain and things … we should have these config pages in full too inside our app, so you select the hosting type then they config for it both public and in the app". One call by design, not as an optimisation. A configuration page assembled from five endpoints renders in five stages, and the two that matter most — the free-domain allowance and the eligible addons — would arrive last, after the visitor has already decided. Everything here is derived from live rows: the terms and their saving are the plan's own two prices subtracted, default_interval is the cheapest per month rather than a literal, the free-domain allowance and its TLDs are the included_domains entitlement, the regions come from the activated data centres for this product line (empty on Footprint-Free by owner ruling), and the addons are the extras Extra.is_eligible_for admits on this line. A choice the platform cannot apply is deliberately absent. There is no PHP-version option: measured on the live catalogue, no plan carries a PHP entitlement — PHP is chosen per site after provisioning — so a picker here would be a control that changes nothing. Lines the owner ruled sellable only inside the app are not served here; the signed-in console reads the same shape from getOrderConfig.

Параметри

ИмеТипЗадължителноКакво представлява
planCode (path)stringДаThe catalogue code of the plan being configured (pbn_5, …).
currency (query)stringНеISO-4217 code to price this response in — the same assertion X-Zinn-Currency makes, in a form a caller that cannot send custom headers can use. The public funnel is exactly that…

Отговор

ИмеТипЗадължителноКакво представлява
plan_codestringДа
plan_namestringДа
plan_idstringДаThe plan's stable identity — what a URL or an analytics event refers to.
plan_version_idstringДаThe purchasable identifier: what a hosting_plan cart line pins. Not plan_id — a price change mints a new version rather than mutating the sold one, so this value changes…
plan_versionintegerДа
product_linestringДа
product_line_namestringДаThe line's display name from the engine's one source table, so a client never has to render a raw code to a customer.
currencystringДаWhat everything on this payload is priced in. It may differ from the currency asked for: a currency with no derived price row yet falls back to USD and says so here rather…
termsOrderTerm[]ДаCheapest per month first, which is what default_interval names.
default_intervalstringДаThe cadence to select on first render — derived as the cheapest per month rather than typed beside the price table. A typed default is a comment that happens to run: correct…
trial_daysobjectДаThe free trial this plan offers, or null for none. A trial takes no card and starts immediately, so the button beneath the configuration has to say "start trial" rather than…
included_domainsintegerДаHow many domain registrations the plan includes free — the "use the free domain this plan includes" branch. 0 is the common case: render that branch only when the allowance is…
included_domain_tldsstring[]ДаWhich extensions the free registration may be spent on. Empty alongside a non-zero included_domains means the plan grants any offered TLD.
domain_term_yearsinteger[]Да
regionsOrderRegion[]ДаThe data centres a site on this plan may be created in. Empty is a real answer — the Footprint-Free line offers no region by owner ruling, because a PBN customer is…
specOrderSpecItem[]ДаThe read-only "what is included" panel, ordered for display. Not a filtered allow-list: every resolved entitlement appears, so a capability added to the catalogue tomorrow is…
addonsOrderAddon[]ДаThe services offered on this product line and deliverable today — a PBN addon never appears on a mainstream plan, and an addon whose fulfilment handler has been withdrawn…

Грешки, които този крайpoint може да върне

404 · 429