hosting

GET /v1/sites/{siteId}/ssh-keys

List a site's authorised SSH keys.

Све hosting крајње тачке

Сва документација за програмере →

Аутентификација

Пошаљите API кључ као bearer токен. Кључ мора имати дозволу sites.view; кључ без ње се одбија уз 403, а не 404.

Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/ssh-keys \
  -H "Authorization: Bearer zdk_live_…"

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

Every public key that can open a shell on the site's hosting package, together with whether the package restricts SSH to a list of addresses. ssh has been rendered as an included plan feature since the Hosting tab shipped — from a vendor flag that really is true on both package types we sell — with no way anywhere in the product to upload a key, so until this resource existed the entitlement was sold and read by nothing. ⛔ ip_restricted is its own field and must never be derived from ip_allowlist == []. The vendor answers "no restriction" as null, and an empty list rendered as a restriction would tell the customer they are protected when the truth is the opposite. ip_allowlist_editable is false today for a vendor reason rather than a plan one, so a client renders the list read-only instead of an editor that cannot save. A site that is not on a vendor hosting package has no such resource and returns 404, exactly as an out-of-scope or unknown id does — never a 403, never an existence oracle. Requires sites.view and sites.panel_access: the list is the access-control state of a shell on the customer's server, which is strictly more than the phpMyAdmin and file-manager access that key already names.

Параметри

НазивТипОбавезноШта је ово
siteId (path)UuidДаSite ID (UUIDv7).

Одговор

НазивТипОбавезноШта је ово
permittedbooleanДаWhether the package type includes SSH at all. This is the flag behind "your plan does not include this".
can_createbooleanДаpermitted, and the package has room for another key. Two fields rather than one because those are different sentences, and a single flag makes the screen say the wrong one.
keysSiteSshKey[]ДаThe keys currently authorised on the package.
ip_allowliststring[]ДаThe addresses SSH is restricted to, when it is restricted.
ip_restrictedbooleanДаWhether an address restriction is actually in force. ⛔ Distinct from ip_allowlist == [] and never derived from it. The vendor answers "no restriction" as null, and an empty…
ip_allowlist_editablebooleanДаWhether the allow-list can be written. False today for a vendor reason rather than a plan one, so a client renders the list read-only instead of an editor that cannot save.
hoststringДаWhat the customer puts after @. ⛔ Before this field existed the surface managed keys for a destination it never named: a customer could add a key, see it listed, and find no…
portintegerДаThe TCP port to connect to. 22 unless a host is wired otherwise.
usernamestringДаThe account name to log in as — the site's own system account, not the customer's email or panel login. "" when unknown.

Грешке које ова крајња тачка може вратити

401 · 403 · 404 · 422 · 429 · 503