POST /v1/reseller/services/{siteId}/package

Аутентификација

Пошаљите API кључ као bearer токен. Кључ мора имати дозволу reseller.provision; кључ без ње се одбија уз 403, а не 404.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

curl -X POST https://api.zinndigital.com/v1/reseller/services/{siteId}/package \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "plan_code": <string> }'

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

Performs the upgrade or downgrade your panel just sold. The vendor package is moved, the client's entitlements follow it, and on our own fleet the box is given the new plan's quota. Requires reseller.provision. ⛔ Your client is not charged by us, and cannot be. Under a reseller programme Zinn® bills you — the new plan appears on your next wholesale statement, because that statement is built from your clients' live subscriptions — and you bill your client through your own panel, which has already taken their money for this upgrade. There is no second charge and no card is touched. That is why this operation exists beside changeSitePlan rather than instead of it: the customer-facing one mints an order against the client organization, which under a reseller holds no payment instrument at all. Takes a plan code, not a version id. A code is what your admin typed into the product's module settings and it stays valid for years; the engine always resolves the newest active version of it, so a plan we have since re-priced cannot be bought at its old price by a panel nobody has updated. Every refusal listResellerServicePackages reports is applied again here on fresh numbers, so a downgrade that has become unsafe since the picker was rendered is still refused. Repeating an identical request is safe and is the documented recovery: each step is idempotent, and a service already on the target plan is a 422 saying so rather than a second move. 422 for an unknown plan code, for a plan on a different product line or infrastructure, and for a downgrade the client's usage does not fit. 503 when the hosting platform behind the service cannot change a package type at all. 404 for a service that is not one of your clients'.

Параметри

Тело захтева

Одговор

Грешке које ова крајња тачка може вратити

401 · 403 · 404 · 422 · 429 · 503