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

ማረጋገጫ

የAPI ቁልፉን እንደ bearer token ይላኩ። ቁልፉ የsites.view ፈቃድ ሊኖረው ይገባል፤ ይህ ፈቃድ የሌለው ቁልፍ በ404 ሳይሆን በ403 ውድቅ ይደረጋል።

ይህ ኤንድፖይ መክፈቻ (endpoint) የድርጅት መታወቂያ (organisation id) አይወስድም። የእርስዎ ቁልፍ (key) እሱ የሚመለከተውን ድርጅት አስቀድሞ ይለያል፣ እና ምላሹም ለዚሁ የተወሰነ ነው።

ሞክሩት

በቅንፍ ውስጥ ያለውን ማንኛውንም ነገር በራስዎ እሴቶች ይተኩ፣ እና ቁልፍ ቦታ ያዢውን ከዳሽቦርድዎ በመጣ ቁልፍ ይተኩ።

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

ገብተዋል? የመቆጣጠሪያ ማዕከልዎ ውስጥ ያለው የኤፒአይ ኮንሶል ትክክለኛውን የድርጅት መታወቂያዎን እና የራስዎን ቁልፍ ይሞላል፣ እና ትክክለኛውን ምላሽ ማየት እንዲችሉ ጥያቄውን በቀጥታ ከሚሰራው ኤፒአይ ጋር ያካሂደዋል። ይህን ኤንድፖይንት በAPI ኮንሶል ውስጥ ይክፈቱ

ዝርዝሮች

Applies the **complete** desired state. An omitted name is cleared — 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. The change is **pushed to the machine as part of this call and read back**, so a `200` means the interpreter a visitor's request runs has actually loaded it. A value the box quietly declined is a failure here, never a success the customer discovers is untrue later. A value above the plan's ceiling is a `422` **naming the plan and the tier that would allow it**, so the panel can offer the upgrade rather than showing a dead end. A staff-only directive is also a `422` and not a `403`: the caller is entitled to change PHP settings, and this particular one is not among them — a `403` reads as "you need a different key" and sends them to support to ask for one that does not exist. Requires `sites.view` + `sites.panel_access`.

መለኪያዎች

የጥያቄ አካል

ምላሽ

ይህ ማብቂያ ሊመልሳቸው የሚችሉ ስህተቶች

401 · 403 · 404 · 422 · 429