public

POST `/v1/public/order/recommend`

Recommend hosting from the guided form's answers, with the reasoning.

Санҷиши ҳаққоният

Ин нуқтаи поёни оммавӣ аст. Он ҳеҷ гуна маълумоти эътимоднок ва ҳеҷ гуна созмонро талаб намекунад — он ҳамон чизест, ки сайти маркетингӣ ва муҳаррикони ҷавоби сунъии худи мо мехонанд.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X POST https://api.zinndigital.com/v1/public/order/recommend \
  -H "Content-Type: application/json" \
  -d '{  }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

Owner, 2026-09-09: "maybe we also need some smart hosting finder, where they can complete a form type thing to choose what they need like cms, if for pbn, and some other questions and then we recommend them the hosting they need with options on it etc". Computed from entitlements, never from a mapping. A hardcoded {"wordpress": "some_plan"} table is right on the day it is written and wrong the first time a plan is renamed, repriced or retired — and it fails silently, recommending a plan the visitor then cannot buy. Every rule reads a number off the plan they would actually receive. A plan that cannot meet a stated hard requirement — fewer sites than asked for, no SSH when SSH was asked for, no footprint promise when the answer was PBN — is dropped rather than ranked lower. Everything else that does not fit comes back as a caveat on a plan that is still offered: a finder that returns nothing because every plan is a pound over budget has answered nobody's question. reasons and caveats are machine codes, never sentences: we serve 58 languages and every surface renders its own copy, so an English string minted here would reach an Arabic page inside an RTL document. A POST that writes nothing. It is a POST because the answers are a structured body, and because a visitor's traffic, budget and site count do not belong in a URL that proxies, logs and Referer headers all carry.

Параметрҳо

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`currency (query)`	`string`	Не	ISO-4217 code to price this response in, and the currency `budget_max_minor` is read in. Same contract as on `getPublicOrderConfig`.

Ҷисми дархост

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`purpose`	`string`	Не	`pbn` \| `single_site` \| `store` \| `agency` \| `reseller` \| `app`.
`cms`	`string`	Не	A key from `getPublicHostingFinderOptions`, or `static` / `none`.
`sites`	`integer`	Не	—
`monthly_visits`	`integer`	Не	—
`needs_email`	`boolean`	Не	—
`needs_domain`	`boolean`	Не	—
`needs_ssh`	`boolean`	Не	—
`budget_max_minor`	`integer`	Не	A ceiling in the response currency's minor units. Over-budget plans are still returned, carrying an `over_budget` caveat: a finder that returns nothing because every plan is a…
`limit`	`integer`	Не	—

Ҷавоб

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`data`	`HostingRecommendation[]`	Бале	—

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

422 · 429

POST /v1/public/order/recommend