PUT /v1/sites/{siteId}/php-config

Autentifikatsiya

API kalitini bearer token sifatida yuboring. Kalit sites.view ruxsatiga ega boʻlishi shart; ruxsatsiz kalit 404 emas, balki 403 xatosi bilan rad etiladi.

Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.

Sinab ko'rish

Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/php-config \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "values": <object> }'

Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching

Tafsilotlar

Applies the **complete** set of overrides. An omitted name is cleared, and `{}` resets every setting to the machine's defaults — deliberately not a PATCH, because *"return this to the platform default"* and *"pin it to the value that default happens to have today"* are different intentions and only a whole-set write can express the first. Values are validated against the **machine's own published range** before the vendor sees them, so a bad value is refused in our words rather than failing later as an unexplained vendor error. The write is then **read back off the machine** and a value it quietly declined is a failure here, never a success the customer discovers is untrue. `409` when the site has no machine to hold the setting. Requires `sites.view` + `sites.panel_access`.

Parametrlar

Soʻrov tanasi

Javob

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

401 · 403 · 404 · 409 · 422 · 429 · 503