hosting

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

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

Toate punctele finale hosting

Autentificare

Trimiteți o cheie API ca token de tip bearer. Cheia trebuie să aibă permisiunea hosting.backup.manage; o cheie care nu o are va fi respinsă cu 403, nu 404.

Acest endpoint nu necesită un ID de organizație. Cheia ta identifică deja organizația căreia îi aparține, iar răspunsul este limitat la aceasta.

Încearcă

Înlocuiți tot ce se află între paranteze unghiulare cu propriile valori și substituentul cheie cu o cheie din tabloul de bord.

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> }'

Autentificat? Consola API din panoul de control îți completează ID-ul real al organizației și propria cheie și rulează cererea în API-ul live, astfel încât să poți vedea răspunsul efectiv. Deschideți acest punct final în consola API

Detalii

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`.

Parametri

NumeTipObligatoriuCe este
siteId (path)UuidDaSite ID (UUIDv7).

Corp cerere

NumeTipObligatoriuCe este
channelExternalBackupChannelDaHow 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_hoststringNuRequired when `channel` is `ssh`.
ssh_portintegerNu
ssh_usernamestringNuRequired when `channel` is `ssh`.
remote_pathstringNuThe document root, required when `channel` is `ssh`. Refused at configuration time rather than at 03:00 when the sweep runs.
ssh_secretstringNuThe private key (PEM) or password. Written to our secret store and never returned. Omit it to keep the credential already stored.

Răspuns

NumeTipObligatoriuCe este
configuredbooleanDaFalse 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<>DaEmpty string when `configured` is false.
enabledbooleanDaA disabled connection is paused, not deleted — the set-up survives.
can_restorebooleanDaWhether 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…
summarystringDaOne 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_hoststringDaEmpty on a `connector` connection.
ssh_portintegerDa
ssh_usernamestringDa
remote_pathstringDaThe site's document root — what we archive, and what we restore into.
credential_presentbooleanDaWhether a credential is stored in our secret store. The credential itself is never returned by any endpoint.
last_verified_atstringDaNull when the connection has never been checked.
last_verified_okbooleanDaNull means never checked, which is not the same as failing — the absence of a measurement is not a measurement.
last_verify_detailstringDa

Erori pe care le poate returna acest punct final

401 · 403 · 404 · 422