POST /v1/public/order/recommend

認証

このエンドポイントは公開されています。認証情報や組織情報は不要で、当社のマーケティングサイトやAI回答エンジンが読み取っているものと同じです。

このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。

試してみる

アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。

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

ログインしていますか？ダッシュボード内のAPIコンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブ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.

パラメータ

リクエスト本文

返信

このエンドポイントが返すエラー

422 · 429