@hostinger/mcp 3.2.0 → 3.2.2

package/src/core/tools/wordpress.js

@@ -376,7 +376,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/orders/{order_id}/onboardings\n(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -398,9 +398,17 @@ export default [
           "type": "string",
           "description": "WordPress locale. Defaults to en_US when omitted."
         },
+        "type": {
+          "type": "string",
+          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.",
+          "enum": [
+            "default",
+            "headless"
+          ]
+        },
         "directory": {
           "type": "string",
-          "description": "Relative directory to install WordPress into. Defaults to the website root when omitted."
+          "description": "Installation subdirectory relative to the document root; omit for the root. Not allowed with `type: headless`, which always installs into `cms`."
         },
         "overwrite": {
           "type": "boolean",

package/src/core/tools/wordpress.ts

@@ -392,7 +392,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/websites and poll\nGET /api/hosting/v1/websites until it appears.\n\nCall GET /api/hosting/v1/wordpress/installations filtered by username and\ndomain before proceeding to check whether WordPress is already installed on\nthe target domain/path. If WordPress already exists and `overwrite` is false\n(the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered\nby username and domain to track progress. When the installation appears in\nthat list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
+    "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/orders/{order_id}/onboardings\n(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
     "inputSchema": {
@@ -414,9 +414,17 @@ const tools: OpenApiTool[] = [
           "type": "string",
           "description": "WordPress locale. Defaults to en_US when omitted."
         },
+        "type": {
+          "type": "string",
+          "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.",
+          "enum": [
+            "default",
+            "headless"
+          ]
+        },
         "directory": {
           "type": "string",
-          "description": "Relative directory to install WordPress into. Defaults to the website root when omitted."
+          "description": "Installation subdirectory relative to the document root; omit for the root. Not allowed with `type: headless`, which always installs into `cms`."
         },
         "overwrite": {
           "type": "boolean",

package/src/servers/agency-hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.2.0', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.2.2', tools, instructions });

package/src/servers/agency-hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 import instructions from '../core/instructions.agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.2.0', tools, instructions });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.2.2', tools, instructions });

package/src/servers/agent-readiness.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.2.2', tools });

package/src/servers/agent-readiness.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.2.2', tools });

package/src/servers/all.js

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '3.2.0', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.2.2', tools, instructions, skills });

package/src/servers/all.ts

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '3.2.0', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '3.2.2', tools, instructions, skills });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.2.2', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '3.2.2', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.2.2', tools });

package/src/servers/dns.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '3.2.2', tools });

package/src/servers/domains.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.2.2', tools });

package/src/servers/domains.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '3.2.2', tools });

package/src/servers/ecommerce.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.2.2', tools });

package/src/servers/ecommerce.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '3.2.2', tools });

package/src/servers/horizons.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.2.2', tools });

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '3.2.2', tools });

package/src/servers/hosting.js

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '3.2.0', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.2.2', tools, instructions });

package/src/servers/hosting.ts

@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 import instructions from '../core/instructions.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '3.2.0', tools, instructions });
+startServer({ name: 'hostinger-hosting-mcp', version: '3.2.2', tools, instructions });

package/src/servers/mail.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.2.2', tools });

package/src/servers/mail.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '3.2.2', tools });

package/src/servers/reach.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.2.2', tools });

package/src/servers/reach.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '3.2.2', tools });

package/src/servers/vps.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.2.2', tools });

package/src/servers/vps.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '3.2.2', tools });

package/src/servers/wordpress.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.2.2', tools });

package/src/servers/wordpress.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '3.2.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '3.2.2', tools });

package/types.d.ts

@@ -3387,7 +3387,8 @@ interface in the provided website URL.
    * Permanently clears all server-side cache for the website at once. Use it when content was
 updated and needs to be visible immediately, or after making major changes.
 
-Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress
+Also purges the Hostinger CDN cache when CDN is enabled on the website. To purge only the CDN
+cache and leave the server cache untouched, use `Purge CDN cache`. For a WordPress
 installation living in a subdirectory, pass the directory query parameter to clear its cache.
    */
   "hosting_cache_clear-website": {
@@ -3459,6 +3460,101 @@ Does nothing if caching is already in the requested state.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Turns off the Hostinger CDN for the website domain. Once DNS propagation completes, the
+website content is served directly from the origin server. Repeating the call is safe; when
+CDN is already disabled, it applies the DNS change again.
+
+Returns 422 for platform-managed domains (for example `*.hostingersite.com` and
+`*.app-preview.com`), where CDN cannot be disabled, even when CDN is already off. Also returns
+422 while the account is being moved to another server (retry after the move finishes), or
+when the CDN provider rejects the change. Returns 404 when the domain is not a website on the
+account.
+   */
+  "hosting_cdn_disable": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Turns on the Hostinger CDN for the website domain, which speeds up page loads and reduces the
+load on the server. Works for the main domain, parked domains and subdomains of the account.
+
+Enabling changes the domain's DNS records and usually takes a few seconds. After that, DNS
+propagation can take a few more minutes before visitors are served through the CDN.
+
+Repeating the call is safe, for example after a timeout. When CDN is already enabled, it
+applies the DNS change again and refreshes the CDN SSL certificate.
+
+Returns 422 when the account is disabled, while the account is being moved to another
+server (retry after the move finishes), or when the CDN provider rejects the change.
+Returns 404 when the domain is not a website on the account.
+   */
+  "hosting_cdn_enable": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Purges the website's content from the Hostinger CDN edge cache only. The origin server cache
+is not touched; to clear both, use `Clear website cache`.
+
+Returns 422 when CDN is not enabled on the website. Returns 404 when the domain is not a
+website on the account.
+   */
+  "hosting_cdn_purge-cache": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Returns whether the Hostinger CDN is enabled for the website domain. Works for the main
+domain, parked domains and subdomains of the account.
+
+The domain must be the exact website name as listed on the account, without a `www.` prefix.
+Returns 404 when the domain is not a website on the account.
+   */
+  "hosting_cdn_status": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Returns the list of cron jobs configured for the specified account, including their schedule and command.
    */
@@ -4957,8 +5053,9 @@ wait for `status: completed` before uploading files, deploying or creating datab
 `failed` means the setup stopped before finishing or has not reported progress for
 over an hour. Setups older than 24 hours are not listed.
 
-`type` is the website type the setup was started with (`wordpress`, `headless_wordpress`,
-`headless_ecommerce`, `headless_pocketbase`), or `null` for an empty website.
+`type` is the website type the setup was started with (`wordpress`, `headless_empty`,
+`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`), or `null` for an empty
+website.
    */
   "hosting_websites_list-setups": {
     params: {
@@ -4981,17 +5078,25 @@ over an hour. Setups older than 24 hours are not listed.
   /**
    * Starts a website setup on a Web or Cloud hosting order and returns the created setup
 right away; the website itself is provisioned asynchronously. Poll the list website
-setups endpoint with the `domain` filter every 10 to 15 seconds and wait for
-`status: completed` before uploading files, deploying or creating databases.
+setups endpoint (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15
+seconds and wait for `status: completed` before uploading files, deploying or creating
+databases.
 
 Omit `type` for an empty website. `type: wordpress` installs WordPress in the website
 root with the admin user, email and password from `wordpress`, the domain as the site
 title, and `en_US` when `wordpress.language` is omitted. The headless types
-(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless
-website; `headless_wordpress` additionally installs WordPress into the `cms` directory
-of the website root with generated credentials.
-
-Omit `domain` to set the website up on a generated temporary free subdomain.
+(`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)
+create a headless website; `headless_wordpress` additionally installs WordPress into the
+`cms` directory of the website root with generated credentials. `headless_empty` installs
+nothing: WordPress can be added later through
+`POST /api/hosting/v1/accounts/{username}/wordpress/installations`
+(`wordpress_installations_install`) with `type: headless`.
+
+Omit `domain` to set the website up on a generated temporary free subdomain. To know the
+free subdomain before the call, so a timed-out call can be looked up and retried on the
+same domain, generate one through `POST /api/hosting/v1/domains/free-subdomains`
+(`hosting_domains_generate-free-subdomain`) and send it as `domain`. It is accepted for
+24 hours, only from the client that generated it.
 
 When the order has no hosting account yet, the setup creates one first, in the datacenter
 given by `datacenter_code` or the order's default datacenter when it is omitted.
@@ -5006,11 +5111,11 @@ running.
        */
       order_id: number;
       /**
-       * Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials.
+       * Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials. `headless_empty` installs nothing, so WordPress can be added later through `POST /api/hosting/v1/accounts/{username}/wordpress/installations` (`wordpress_installations_install`) with `type: headless`.
        */
       type?: string;
       /**
-       * Customer-owned domain. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain.
+       * Customer-owned domain, or a free subdomain you generated through `POST /api/hosting/v1/domains/free-subdomains` (`hosting_domains_generate-free-subdomain`) in the last 24 hours. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain.
        */
       domain?: string;
       /**
@@ -9666,19 +9771,29 @@ database files that have been uploaded to the website's directory.
    * Install WordPress on an existing website.
 
 The website must already exist before calling this endpoint. To create a new
-website first, use POST /api/hosting/v1/websites and poll
-GET /api/hosting/v1/websites until it appears.
-
-Call GET /api/hosting/v1/wordpress/installations filtered by username and
-domain before proceeding to check whether WordPress is already installed on
-the target domain/path. If WordPress already exists and `overwrite` is false
-(the default), the async job will fail.
+website first, use POST /api/hosting/v1/orders/{order_id}/onboardings
+(`hosting_websites_start-setup`) and poll GET /api/hosting/v1/onboardings
+(`hosting_websites_list-setups`) with the `domain` filter until its `status` is
+`completed`.
+
+Send `type: headless` to turn a headless website (for example one created by
+`hosting_websites_start-setup` with `type: headless_empty`) into a headless WordPress
+website: WordPress is installed into the `cms` directory with the Hostinger headless
+MU plugin and the website is marked as a headless WordPress website. `directory` is
+not allowed with it. The target website must already be headless: the headless
+install rewrites the root `.htaccess`, so on any other website the request is
+rejected with 422.
+
+Call GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)
+filtered by username and domain before proceeding to check whether WordPress is
+already installed on the target domain/path. If WordPress already exists and
+`overwrite` is false (the default), the async job will fail.
 
 This operation is asynchronous: a successful response only means the install
 job has been queued, not that WordPress is ready. Installation typically
-takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered
-by username and domain to track progress. When the installation appears in
-that list, WordPress is ready.
+takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations
+(`wordpress_installations_list`) filtered by username and domain to track
+progress. When the installation appears in that list, WordPress is ready.
 
 Returns 422 when the account already uses all the databases its plan allows,
 unless `database.name` is an existing database on the account.
@@ -9702,7 +9817,11 @@ unless `database.name` is an existing database on the account.
        */
       language?: string;
       /**
-       * Relative directory to install WordPress into. Defaults to the website root when omitted.
+       * Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_start-setup`) with `type: headless_empty`; any other website is rejected with 422.
+       */
+      type?: string;
+      /**
+       * Installation subdirectory relative to the document root; omit for the root. Not allowed with `type: headless`, which always installs into `cms`.
        */
       directory?: string;
       /**