hosting

PUT /v1/sites/{siteId}/external-backup

Connect an externally hosted site so we can back it up.

Semua titik akhir hosting

Pengesahan

Hantar kunci API sebagai token pembawa. Kunci tersebut mesti membawa kebenaran hosting.backup.manage; kunci yang tidak mempunyainya akan ditolak dengan 403, bukan 404.

Titik akhir ini tidak memerlukan id organisasi. Kunci anda telah mengenal pasti organisasi kepunyaannya, dan respons dis skopkan kepadanya.

Cuba

Gantikan apa sahaja di dalam kurungan sudut dengan nilai anda sendiri, dan pemegang tempat kunci dengan kunci dari papan pemuka anda.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/external-backup \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "channel": <ExternalBackupChannel> }'

Sudah log masuk? Konsol API dalam papan pemuka anda mengisi id organisasi sebenar dan kunci anda sendiri, serta menjalankan permintaan terhadap API langsung supaya anda boleh melihat respons sebenar. Buka penamat ini dalam konsol API

Butiran

Configures one of two channels. `connector` — the customer installs the Zinn® Connector plugin and pairs it. Nothing else is needed and we never hold a server credential. The plugin makes outbound calls only; it opens no route on their site. Backup only: it cannot restore. `ssh` — the customer gives us a host, a username, the document root and a private key. This channel can also **push a site back**, including when the site itself will not load, which is the only way a one-click restore can be honest. `ssh_secret` is write-only. It goes straight to our secret store and only a pointer to it is kept; it is never returned by this or any other endpoint. Re-connecting a `connector` site mints a fresh pairing token and invalidates whatever the previous install held. Requires `hosting.backup.manage`.

Parameter

NamaJenisDiperlukanApakah ia
siteId (path)UuidYaSite ID (UUIDv7).

Badan permintaan

NamaJenisDiperlukanApakah ia
channelExternalBackupChannelYaHow we reach a site we do not host. `connector` is the Zinn® Connector plugin (outbound-only, backup but no restore); `ssh` is SSH/SFTP, the only channel that can push a site ba…
ssh_hoststringTidakRequired when `channel` is `ssh`.
ssh_portintegerTidak
ssh_usernamestringTidakRequired when `channel` is `ssh`.
remote_pathstringTidakThe document root, required when `channel` is `ssh`. Refused at configuration time rather than at 03:00 when the sweep runs.
ssh_secretstringTidakThe private key (PEM) or password. Written to our secret store and never returned. Omit it to keep the credential already stored.

Respons

NamaJenisDiperlukanApakah ia
configuredbooleanYaFalse when nobody has connected this site yet. The rest of the object is still present and empty — a screen must not have to tell "not set up" from "failed to load" by the absen…
channelExternalBackupChannel | string<>YaEmpty string when `configured` is false.
enabledbooleanYaA disabled connection is paused, not deleted — the set-up survives.
can_restorebooleanYaWhether we can push a backup back down this channel. **False for `connector`**, and that is not a limitation to route around: a WordPress plugin cannot run inside a WordPress to…
summarystringYaOne sentence stating what this connection can and cannot do, composed server-side so every surface says the same thing about the backup/restore asymmetry.
ssh_hoststringYaEmpty on a `connector` connection.
ssh_portintegerYa
ssh_usernamestringYa
remote_pathstringYaThe site's document root — what we archive, and what we restore into.
credential_presentbooleanYaWhether a credential is stored in our secret store. The credential itself is never returned by any endpoint.
last_verified_atstringYaNull when the connection has never been checked.
last_verified_okbooleanYaNull means never checked, which is not the same as failing — the absence of a measurement is not a measurement.
last_verify_detailstringYa

Ralat yang boleh dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422