hosting

POST /v1/sites/{siteId}/subdomains

Add a subdomain to a site.

Wszystkie punkty końcowe hosting

Wszystkie dokumentacje dla programistów

Uwierzytelnianie

Wyślij klucz API jako token bearer. Klucz musi posiadać uprawnienie sites.view; 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 POST https://api.zinndigital.com/v1/sites/{siteId}/subdomains \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string> }'

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

Adds one subdomain to the package. The effective ceiling is applied before the vendor is called: a package type that does not permit subdomains, and a customer who has used the last of their allowance, are both 422 with a sentence they can act on. ⛔ The response is the row the platform stored, not the name that was requested — the vendor normalises and namespaces it, so the client shows what came back. ⚖️ On our own fleet this spends one of the plan's site slots (owner ruling 2026-09-01), so the refusal at the cap is the same event as it is on site create and carries the same SITE_QUOTA_EXCEEDED code and figures. The row comes back pending: the DNS record, the virtual host and the chosen stack are built by a durable workflow, and the row reaches active when the name is serving. A build that cannot be done — a hostname whose DNS we do not control, or one this server's certificate cannot cover — lands in failed with the reason in status_detail. 404 for a site with no managed hosting package and no own-fleet placement. Requires sites.view and sites.panel_access.

Parametry

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

Treść żądania

NazwaTypWymaganeCo to jest
namestringTakThe subdomain to add. What the vendor actually created comes back in SiteSubdomain.name, and that — never this — is what the client shows.
stack_typestring<static, php, wordpress, woocommerce>NieWhat the subdomain should run. ⚖️ Owner ruling 2026-09-01 — a new subdomain "will start as whatever they select". static and php give an empty document root to upload or…

Odpowiedź

NazwaTypWymaganeCo to jest
namestringTakThe subdomain as the platform stored it. ⛔ Not necessarily what was requested — a vendor normalises it, and the client shows this value.
document_rootstringTakThe folder it serves. Relative to the package root on a resold package; an absolute path on our own fleet, where it is read back from the server's own configuration rather than…
stack_typestringNieWhat this subdomain runs, as the customer chose at creation. ⛔ Empty on a resold package, where the folder is the vendor's and there is no stack we chose — deliberately blank…
statusstring<pending, active, failed, deleting, >NieWhere the build has got to. pending while the record, the virtual host and the stack are being put in place; active once the name serves; deleting after a delete, when the…
status_detailstringNieWhy it failed, or a note about a build that partly succeeded — a sentence written for the customer. Empty on a healthy row.

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

401 · 403 · 404 · 409 · 422 · 429 · 503