hosting

POST /v1/sites/{siteId}/wordpress/staging/publish

Publish a site's staging WordPress over the live site.

सबै hosting इन्डपइन्टहरू

सबै विकासकर्ता कागजातहरू

प्रमाणीकरण

एपिआई कुञ्जीलाई बियरर टोकन (bearer token) को रूपमा पठाउनुहोस्। कुञ्जीसँग sites.view अनुमति हुनुपर्छ; अनुमति नभएको कुञ्जीलाई 404 होइन, 403 मार्फत अस्वीकार गरिन्छ।

यो इन्डपोइन्टले कुनै संस्थाको आइडी लिँदैन। तपाईंको कुञ्जीले यस अन्तर्गत पर्ने संस्थालाई पहिल्यै पहिचान गर्छ, र प्रतिक्रिया त्यसैमा सीमित हुन्छ।

प्रयास गर्नुहोस्

कोणीय कोष्ठकभित्र भएका जुनसुकै कुरालाई आफ्नो मानहरूद्वारा बदल्नुहोस्, र मुख्य स्थानहोल्डरलाई तपाईंको ड्यासबोर्डको कुञ्जीद्वारा बदल्नुहोस्।

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

लगइन गर्नुभएको छ? तपाईंको ड्यासबोर्डमा रहेको API कन्सोलले तपाईंको वास्तविक संस्थाको आईडी र आफ्नै कुञ्जी भरिदिन्छ, र लाइभ API विरुद्ध अनुरोध चलाउँछ ताकि तपाईंले वास्तविक प्रतिक्रिया हेर्न सक्नुहोस्। यो एन्डपोइन्टलाई API कन्सोलमा खोल्नुहोस्

विवरणहरू

The most destructive operation on the managed hosting line: the live site's files and database are replaced by the staging clone's. Its own path, so no request aimed at any other staging operation can reach it. ⛔⛤ The one optional field, mode, selects SCOPE and never DIRECTION. This path exists separately from createSiteWordPressStaging precisely so that no field can flip which way the copy runs — on managed shared hosting both directions are driven from a single value, and one passthrough endpoint would let a request reading as "refresh my staging copy" publish a stale clone over a live shop. Every value of mode copies staging onto live; it says only how much travels. A field that could change the direction must never be added here. ⛔ A scope the site's platform cannot honour is refused 422. Read publish_modes on SiteWordPressStaging first and offer only what it lists: the Zinn® autoscaling platform performs files, db and both, and managed shared hosting performs both only, because its staging operation takes no scope at all. That is a property of the platform, not of the customer's plan — a larger package does not add a database-only publish. Refused 422 when the site has no staging clone — the platform does not check, and would happily publish an empty staging environment over a live shop. The client is required to take a typed confirmation naming the site. 202 because the publish continues at the vendor after the acknowledgement. 404 for a site whose platform has no WordPress to manage. Requires sites.view and sites.panel_access.

प्यारामिटरहरू

नामप्रकारआवश्यकयो के हो
siteId (path)Uuidहुन्छSite ID (UUIDv7).

अनुरोध बडी

नामप्रकारआवश्यकयो के हो
modestring<files, db, both>हैनfiles copies the document root and leaves the live database alone; db copies the database and search-replaces the staging URL back to the live one, leaving the live files…

प्रतिक्रिया

नामप्रकारआवश्यकयो के हो
permittedbooleanहुन्छWhether this site may use WordPress staging at all — on the resold range the package type's own flag, and on our own fleet the plan's staging entitlement.
publish_modesstring<files, db, both>[]हुन्छWhich publish scopes this site's platform can actually perform, for publishSiteWordPressStaging. A client offers exactly these and no more. ⛔⛔…
publishablebooleanहुन्छWhether the plan also carries publish to live, which is a separate permission from creating a staging copy. ⛔ Not folded into permitted, because the catalogue sells the two…
reinstallablebooleanहुन्छWhether the plan carries reinstalling the platform software over the staging copy. A fifth question for the same reason as publishable: the catalogue sells it separately, so…
idle_removal_daysintegerहुन्छAfter how many days with no change a staging copy is removed automatically, or null when nothing ever removes it. ⛔⛔…
idle_notice_daysintegerहुन्छHow many days' warning the customer is emailed before that removal, or null when idle_removal_days is null.
operationsSiteWordPressStagingOperation[]हुन्छThe site's recent staging operations, newest first — the client's window onto work that runs after the request returns. ⛔⛔…
dataSiteWordPressStagingClone[]हुन्छThe staging copies that exist.

यो इन्डपोइन्टले फर्काउन सक्ने त्रुटिहरू

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