Websites
Create and manage Windows or Linux websites inside an existing plan. The platform is selected by choosing a planId; website creation does not accept an arbitrary operating-system override.
Typical lifecycle
- Call
hosting_list_plansand select an existing Windows or Linux plan with capacity. - Call
website_createwith the plan ID, a 2–20 character ASCII display name, PHP preference, and a new idempotency key. - Call
websites_listto obtain the newsiteIdand temporary URL. - Configure supported site functions, secrets, domains, DNS, and SSL.
- Deploy through GitHub Actions using IIS WebDeploy for compatible Windows plans or FTPS for Linux plans.
Site functions
website_get_function returns explicitly allow-listed public fields and current values for a supported control-panel drawer. Use website_update_function with the returned function key, supported action, documented fields, and an idempotency key. Reusing that key with identical arguments replays the recorded outcome; reusing it with different arguments is rejected. GitHub integration, Visitor Statistics, Schedule Tasks, Outgoing Port rules, and browser-only drawers are intentionally excluded.
Runtime operations
| Tool | Behavior | Confirmation |
|---|---|---|
website_start | Starts the site runtime. | Idempotency key |
website_restart | Restarts the site runtime. | Idempotency key |
website_stop | Makes the site unavailable. | Exact site ID |
website_delete | Deletes the site through the existing cleanup flow. | Exact site ID and file-deletion choice |
Inventory the mapped domains, deployment configuration, and application data before deleting a website. Use a new idempotency key for a newly intended deletion.