hosting

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

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

Wszystkie punkty końcowe hosting

Wszystkie dokumentacje dla programistów

Uwierzytelnianie

Wyślij klucz API jako token bearer. Klucz musi posiadać uprawnienie hosting.backup.manage; klucz bez niego jest odrzucany z kodem 403, a nie 404.

Ten punkt końcowy nie wymaga identyfikatora organizacji. Twój klucz już identyfikuje organizację, do której należy, a odpowiedź jest do niej ograniczona.

Wypróbuj

Zastąp wszystko w nawiasach ostrych własnymi wartościami, a zastępczy znacznik klucza kluczem ze swojego pulpitu nawigacyjnego.

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

Zalogowany? Konsola API w Twoim panelu uzupełnia rzeczywiste identyfikator organizacji oraz Twój własny klucz i wykonuje żądanie względem aktywnego API, dzięki czemu możesz zobaczyć rzeczywistą odpowiedź. Otwórz ten punkt końcowy w konsoli API

Szczegóły

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.

Parametry

NazwaTypWymaganeCo to jest
siteId (path)UuidTakSite ID (UUIDv7).

Treść żądania

NazwaTypWymaganeCo to jest
channelExternalBackupChannelTakHow 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_hoststringNieRequired when channel is ssh.
ssh_portintegerNie
ssh_usernamestringNieRequired when channel is ssh.
remote_pathstringNieThe document root, required when channel is ssh. Refused at configuration time rather than at 03:00 when the sweep runs.
ssh_secretstringNieThe private key (PEM) or password. Written to our secret store and never returned. Omit it to keep the credential already stored.

Odpowiedź

NazwaTypWymaganeCo to jest
configuredbooleanTakFalse 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<>TakEmpty string when configured is false.
enabledbooleanTakA disabled connection is paused, not deleted — the set-up survives.
can_restorebooleanTakWhether 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…
summarystringTakOne 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_hoststringTakEmpty on a connector connection.
ssh_portintegerTak
ssh_usernamestringTak
remote_pathstringTakThe site's document root — what we archive, and what we restore into.
credential_presentbooleanTakWhether a credential is stored in our secret store. The credential itself is never returned by any endpoint.
last_verified_atstringTakNull when the connection has never been checked.
last_verified_okbooleanTakNull means never checked, which is not the same as failing — the absence of a measurement is not a measurement.
last_verify_detailstringTak

Błędy, które ten punkt końcowy może zwrócić

401 · 403 · 404 · 422