POST /v1/sites/{siteId}/error-pages

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.panel_access; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/error-pages \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "status": <integer>, "value": <string> }'

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

Sends **one** rule; the others are preserved. ⛔ The vendor endpoint underneath is a **whole-set** write — it replaces every rule on every call — so the engine reads the current set, applies this one change and sends the whole thing back. Two edits made inside one vendor round trip are therefore last-writer-wins, which cannot be fixed from our side: there is no per-rule identifier and no conditional write. A client should re-read after a write rather than assume its own optimistic copy is current. Only `400`–`599` may carry a custom page: a rule on any other code would replace a working response. Requires `sites.panel_access`.

Cabiraha

Codsiga jidhkiisa

Jawaab

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 422 · 429 · 503