hosting

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

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

Всички крайни точки в hosting

Всички документи за разработчици

Упълномощаване

Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението hosting.backup.manage; ключ без него се отхвърля с 403, а не с 404.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

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

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

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.

Параметри

ИмеТипЗадължителноКакво представлява
siteId (path)UuidДаSite ID (UUIDv7).

Тяло на заявката

ИмеТипЗадължителноКакво представлява
channelExternalBackupChannelДаHow 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 back…
ssh_hoststringНеRequired when channel is ssh.
ssh_portintegerНе
ssh_usernamestringНеRequired when channel is ssh.
remote_pathstringНеThe document root, required when channel is ssh. Refused at configuration time rather than at 03:00 when the sweep runs.
ssh_secretstringНеThe private key (PEM) or password. Written to our secret store and never returned. Omit it to keep the credential already stored.

Отговор

ИмеТипЗадължителноКакво представлява
configuredbooleanДаFalse 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 absence…
channelExternalBackupChannel | string<>ДаEmpty string when configured is false.
enabledbooleanДаA disabled connection is paused, not deleted — the set-up survives.
can_restorebooleanДаWhether 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 too…
summarystringДаOne 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_hoststringДаEmpty on a connector connection.
ssh_portintegerДа
ssh_usernamestringДа
remote_pathstringДаThe site's document root — what we archive, and what we restore into.
credential_presentbooleanДаWhether a credential is stored in our secret store. The credential itself is never returned by any endpoint.
last_verified_atstringДаNull when the connection has never been checked.
last_verified_okbooleanДаNull means never checked, which is not the same as failing — the absence of a measurement is not a measurement.
last_verify_detailstringДа

Грешки, които този крайpoint може да върне

401 · 403 · 404 · 422