hosting
DELETE /v1/site-blueprints/{siteBlueprintId}
Delete a site blueprint.
Xaqiijinta aqoonsiga
U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.blueprint.manage; 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 DELETE https://api.zinndigital.com/v1/site-blueprints/{siteBlueprintId} \
-H "Authorization: Bearer zdk_live_…"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
Details
Removes the template and its screenshot. ⛔ **The backup is not deleted** — it is one of the customer's restore points and always was; the blueprint only held it open past the org's ordinary retention, and deleting the blueprint releases that pin. A blueprint that sites have been built from is refused with a `422`: the deployment rows are the record of what a live site was made from. Requires `sites.blueprint.manage`.
Cabiraha
| Magaca | Nooc | Loo baahan yahay | Maxay tahay |
|---|---|---|---|
siteBlueprintId (path) | Uuid | Haa | A SITE blueprint's id (UUIDv7) — one of the customer's own captured sites. ⛔ Not a `blueprintId`: that names a published stack recipe, and the two are different resources that u… |
Cilladaha ay bartaani soo celin karto
401 · 403 · 404 · 422 · 429