@hostinger/sdk 1.58.2 → 1.59.0

package/dist/esm/api.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api
@@ -530,6 +530,12 @@ export const HostingV1OnboardingsOnboardingResourceStatusEnum = {
     Completed: 'completed',
     Failed: 'failed'
 };
+export const HostingV1OnboardingsStartOnboardingRequestTypeEnum = {
+    Wordpress: 'wordpress',
+    HeadlessWordpress: 'headless_wordpress',
+    HeadlessEcommerce: 'headless_ecommerce',
+    HeadlessPocketbase: 'headless_pocketbase'
+};
 export const HostingV1SslSslStatusResourceStatusEnum = {
     NotInstalled: 'not_installed',
     Installing: 'installing',
@@ -18246,13 +18252,15 @@ export const HostingWebsitesApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first.  Meant for polling right after creating a website: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `failed` means the setup stopped before finishing or has not reported progress for over an hour. Setups older than 24 hours are not listed.
+         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first. Narrow the list with the `order_id`, `subscription_id` or `domain` filters.  Meant for polling right after creating a website or starting a website setup: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `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.
          * @summary List website setups
+         * @param {number | null} [orderId] Order ID
+         * @param {string | null} [subscriptionId] Filter by hosting order subscription ID
          * @param {string | null} [domain] Filter by domain name (exact match)
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listWebsiteSetupsV1: (domain_1, ...args_1) => __awaiter(this, [domain_1, ...args_1], void 0, function* (domain, options = {}) {
+        listWebsiteSetupsV1: (orderId_1, subscriptionId_1, domain_1, ...args_1) => __awaiter(this, [orderId_1, subscriptionId_1, domain_1, ...args_1], void 0, function* (orderId, subscriptionId, domain, options = {}) {
             const localVarPath = `/api/hosting/v1/onboardings`;
             // use dummy base URL string because the URL constructor only accepts absolute URLs.
             const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
@@ -18266,6 +18274,12 @@ export const HostingWebsitesApiAxiosParamCreator = function (configuration) {
             // authentication apiToken required
             // http bearer authentication required
             yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            if (orderId !== undefined) {
+                localVarQueryParameter['order_id'] = orderId;
+            }
+            if (subscriptionId !== undefined) {
+                localVarQueryParameter['subscription_id'] = subscriptionId;
+            }
             if (domain !== undefined) {
                 localVarQueryParameter['domain'] = domain;
             }
@@ -18333,6 +18347,43 @@ export const HostingWebsitesApiAxiosParamCreator = function (configuration) {
                 options: localVarRequestOptions,
             };
         }),
+        /**
+         * 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.  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.  The order must already have a hosting account: to create the first website on a new hosting plan use the create website endpoint, which takes the `datacenter_code`. Returns 404 when the order does not exist or is not accessible to the authenticated client, and 409 with a `Retry-After` header while a setup for the same domain is still running.
+         * @summary Start website setup
+         * @param {number} orderId Hosting order ID. List orders to find available IDs.
+         * @param {HostingV1OnboardingsStartOnboardingRequest} hostingV1OnboardingsStartOnboardingRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        startWebsiteSetupV1: (orderId_1, hostingV1OnboardingsStartOnboardingRequest_1, ...args_1) => __awaiter(this, [orderId_1, hostingV1OnboardingsStartOnboardingRequest_1, ...args_1], void 0, function* (orderId, hostingV1OnboardingsStartOnboardingRequest, options = {}) {
+            // verify required parameter 'orderId' is not null or undefined
+            assertParamExists('startWebsiteSetupV1', 'orderId', orderId);
+            // verify required parameter 'hostingV1OnboardingsStartOnboardingRequest' is not null or undefined
+            assertParamExists('startWebsiteSetupV1', 'hostingV1OnboardingsStartOnboardingRequest', hostingV1OnboardingsStartOnboardingRequest);
+            const localVarPath = `/api/hosting/v1/orders/{order_id}/onboardings`
+                .replace(`{${"order_id"}}`, encodeURIComponent(String(orderId)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            // authentication apiToken required
+            // http bearer authentication required
+            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            localVarHeaderParameter['Content-Type'] = 'application/json';
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = serializeDataIfNeeded(hostingV1OnboardingsStartOnboardingRequest, localVarRequestOptions, configuration);
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
     };
 };
 /**
@@ -18390,16 +18441,18 @@ export const HostingWebsitesApiFp = function (configuration) {
             });
         },
         /**
-         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first.  Meant for polling right after creating a website: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `failed` means the setup stopped before finishing or has not reported progress for over an hour. Setups older than 24 hours are not listed.
+         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first. Narrow the list with the `order_id`, `subscription_id` or `domain` filters.  Meant for polling right after creating a website or starting a website setup: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `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.
          * @summary List website setups
+         * @param {number | null} [orderId] Order ID
+         * @param {string | null} [subscriptionId] Filter by hosting order subscription ID
          * @param {string | null} [domain] Filter by domain name (exact match)
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listWebsiteSetupsV1(domain, options) {
+        listWebsiteSetupsV1(orderId, subscriptionId, domain, options) {
             return __awaiter(this, void 0, void 0, function* () {
                 var _a, _b;
-                const localVarAxiosArgs = yield localVarAxiosParamCreator.listWebsiteSetupsV1(domain, options);
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.listWebsiteSetupsV1(orderId, subscriptionId, domain, options);
                 const localVarOperationServerBasePath = (_b = (_a = operationServerMap['HostingWebsitesApi.listWebsiteSetupsV1']) === null || _a === void 0 ? void 0 : _a[0]) === null || _b === void 0 ? void 0 : _b.url;
                 return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
             });
@@ -18425,6 +18478,22 @@ export const HostingWebsitesApiFp = function (configuration) {
                 return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
             });
         },
+        /**
+         * 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.  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.  The order must already have a hosting account: to create the first website on a new hosting plan use the create website endpoint, which takes the `datacenter_code`. Returns 404 when the order does not exist or is not accessible to the authenticated client, and 409 with a `Retry-After` header while a setup for the same domain is still running.
+         * @summary Start website setup
+         * @param {number} orderId Hosting order ID. List orders to find available IDs.
+         * @param {HostingV1OnboardingsStartOnboardingRequest} hostingV1OnboardingsStartOnboardingRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options);
+                const localVarOperationServerBasePath = (_b = (_a = operationServerMap['HostingWebsitesApi.startWebsiteSetupV1']) === null || _a === void 0 ? void 0 : _a[0]) === null || _b === void 0 ? void 0 : _b.url;
+                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
     };
 };
 /**
@@ -18467,14 +18536,16 @@ export const HostingWebsitesApiFactory = function (configuration, basePath, axio
             return localVarFp.deployStaticSiteArchiveV1(username, domain, hostingV1WebsitesDeployArchiveRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first.  Meant for polling right after creating a website: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `failed` means the setup stopped before finishing or has not reported progress for over an hour. Setups older than 24 hours are not listed.
+         * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first. Narrow the list with the `order_id`, `subscription_id` or `domain` filters.  Meant for polling right after creating a website or starting a website setup: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `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.
          * @summary List website setups
+         * @param {number | null} [orderId] Order ID
+         * @param {string | null} [subscriptionId] Filter by hosting order subscription ID
          * @param {string | null} [domain] Filter by domain name (exact match)
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listWebsiteSetupsV1(domain, options) {
-            return localVarFp.listWebsiteSetupsV1(domain, options).then((request) => request(axios, basePath));
+        listWebsiteSetupsV1(orderId, subscriptionId, domain, options) {
+            return localVarFp.listWebsiteSetupsV1(orderId, subscriptionId, domain, options).then((request) => request(axios, basePath));
         },
         /**
          * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use `website_types` to list only websites of a given detected type, e.g. only WordPress websites (`website_types=wordpress`) or only Node.js websites (`website_types=nodejs`). Combine with the other available query parameters to filter by username, order ID, enabled status, or domain name for more targeted results.  A website appears in this list before its server-side setup has finished, and `is_enabled` reflects suspension, not readiness. To know when a newly created website is ready for file, deploy or database operations, poll the list website setups endpoint instead.
@@ -18492,6 +18563,17 @@ export const HostingWebsitesApiFactory = function (configuration, basePath, axio
         listWebsitesV1(page, perPage, username, orderId, isEnabled, domain, websiteTypes, options) {
             return localVarFp.listWebsitesV1(page, perPage, username, orderId, isEnabled, domain, websiteTypes, options).then((request) => request(axios, basePath));
         },
+        /**
+         * 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.  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.  The order must already have a hosting account: to create the first website on a new hosting plan use the create website endpoint, which takes the `datacenter_code`. Returns 404 when the order does not exist or is not accessible to the authenticated client, and 409 with a `Retry-After` header while a setup for the same domain is still running.
+         * @summary Start website setup
+         * @param {number} orderId Hosting order ID. List orders to find available IDs.
+         * @param {HostingV1OnboardingsStartOnboardingRequest} hostingV1OnboardingsStartOnboardingRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options) {
+            return localVarFp.startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options).then((request) => request(axios, basePath));
+        },
     };
 };
 /**
@@ -18537,15 +18619,17 @@ export class HostingWebsitesApi extends BaseAPI {
         return HostingWebsitesApiFp(this.configuration).deployStaticSiteArchiveV1(username, domain, hostingV1WebsitesDeployArchiveRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first.  Meant for polling right after creating a website: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `failed` means the setup stopped before finishing or has not reported progress for over an hour. Setups older than 24 hours are not listed.
+     * Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first. Narrow the list with the `order_id`, `subscription_id` or `domain` filters.  Meant for polling right after creating a website or starting a website setup: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `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.
      * @summary List website setups
+     * @param {number | null} [orderId] Order ID
+     * @param {string | null} [subscriptionId] Filter by hosting order subscription ID
      * @param {string | null} [domain] Filter by domain name (exact match)
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof HostingWebsitesApi
      */
-    listWebsiteSetupsV1(domain, options) {
-        return HostingWebsitesApiFp(this.configuration).listWebsiteSetupsV1(domain, options).then((request) => request(this.axios, this.basePath));
+    listWebsiteSetupsV1(orderId, subscriptionId, domain, options) {
+        return HostingWebsitesApiFp(this.configuration).listWebsiteSetupsV1(orderId, subscriptionId, domain, options).then((request) => request(this.axios, this.basePath));
     }
     /**
      * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use `website_types` to list only websites of a given detected type, e.g. only WordPress websites (`website_types=wordpress`) or only Node.js websites (`website_types=nodejs`). Combine with the other available query parameters to filter by username, order ID, enabled status, or domain name for more targeted results.  A website appears in this list before its server-side setup has finished, and `is_enabled` reflects suspension, not readiness. To know when a newly created website is ready for file, deploy or database operations, poll the list website setups endpoint instead.
@@ -18564,6 +18648,18 @@ export class HostingWebsitesApi extends BaseAPI {
     listWebsitesV1(page, perPage, username, orderId, isEnabled, domain, websiteTypes, options) {
         return HostingWebsitesApiFp(this.configuration).listWebsitesV1(page, perPage, username, orderId, isEnabled, domain, websiteTypes, options).then((request) => request(this.axios, this.basePath));
     }
+    /**
+     * 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.  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.  The order must already have a hosting account: to create the first website on a new hosting plan use the create website endpoint, which takes the `datacenter_code`. Returns 404 when the order does not exist or is not accessible to the authenticated client, and 409 with a `Retry-After` header while a setup for the same domain is still running.
+     * @summary Start website setup
+     * @param {number} orderId Hosting order ID. List orders to find available IDs.
+     * @param {HostingV1OnboardingsStartOnboardingRequest} hostingV1OnboardingsStartOnboardingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingWebsitesApi
+     */
+    startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options) {
+        return HostingWebsitesApiFp(this.configuration).startWebsiteSetupV1(orderId, hostingV1OnboardingsStartOnboardingRequest, options).then((request) => request(this.axios, this.basePath));
+    }
 }
 /**
  * @export
@@ -31956,7 +32052,7 @@ export const WordPressInstallationsApiAxiosParamCreator = function (configuratio
             };
         }),
         /**
-         * 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.  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.
+         * 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.  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.  Returns 422 when the account already uses all the databases its plan allows, unless `database.name` is an existing database on the account.
          * @summary Install WordPress
          * @param {string} username
          * @param {WordPressV1InstallationsInstallWordPressRequest} wordPressV1InstallationsInstallWordPressRequest
@@ -32236,7 +32332,7 @@ export const WordPressInstallationsApiFp = function (configuration) {
             });
         },
         /**
-         * 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.  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.
+         * 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.  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.  Returns 422 when the account already uses all the databases its plan allows, unless `database.name` is an existing database on the account.
          * @summary Install WordPress
          * @param {string} username
          * @param {WordPressV1InstallationsInstallWordPressRequest} wordPressV1InstallationsInstallWordPressRequest
@@ -32383,7 +32479,7 @@ export const WordPressInstallationsApiFactory = function (configuration, basePat
             return localVarFp.importWordPressWebsiteV1(username, domain, wordPressV1InstallationsImportWordPressRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * 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.  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.
+         * 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.  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.  Returns 422 when the account already uses all the databases its plan allows, unless `database.name` is an existing database on the account.
          * @summary Install WordPress
          * @param {string} username
          * @param {WordPressV1InstallationsInstallWordPressRequest} wordPressV1InstallationsInstallWordPressRequest
@@ -32510,7 +32606,7 @@ export class WordPressInstallationsApi extends BaseAPI {
         return WordPressInstallationsApiFp(this.configuration).importWordPressWebsiteV1(username, domain, wordPressV1InstallationsImportWordPressRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * 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.  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.
+     * 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.  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.  Returns 422 when the account already uses all the databases its plan allows, unless `database.name` is an existing database on the account.
      * @summary Install WordPress
      * @param {string} username
      * @param {WordPressV1InstallationsInstallWordPressRequest} wordPressV1InstallationsInstallWordPressRequest

package/dist/esm/base.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/base.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/common.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/common.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/configuration.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/configuration.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api
@@ -13,7 +13,7 @@ export class Configuration {
         var _a;
         this.accessToken = param.accessToken;
         this.basePath = param.basePath;
-        this.baseOptions = Object.assign(Object.assign({}, param.baseOptions), { headers: Object.assign({ 'User-Agent': "hostinger-typescript-sdk/1.58.2" }, (_a = param.baseOptions) === null || _a === void 0 ? void 0 : _a.headers) });
+        this.baseOptions = Object.assign(Object.assign({}, param.baseOptions), { headers: Object.assign({ 'User-Agent': "hostinger-typescript-sdk/1.59.0" }, (_a = param.baseOptions) === null || _a === void 0 ? void 0 : _a.headers) });
         this.formDataCtor = param.formDataCtor;
     }
     /**

package/dist/esm/index.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/esm/index.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/index.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/dist/index.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.2
+ * API Version: 1.59.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/docs/HostingV1OnboardingsOnboardingResource.md

@@ -7,6 +7,7 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **domain** | **string** | Domain of the website being set up. | [default to undefined]
 **username** | **string** | Hosting account username. | [default to undefined]
+**type** | **string** | Website type requested for the setup: `wordpress`, `headless_wordpress`, `headless_ecommerce` or `headless_pocketbase`. `null` for an empty website. Setups started outside this API may report other legacy types. | [optional] [default to undefined]
 **status** | **string** | `running` while the website is still being set up, `completed` once the setup has finished, `failed` when it stopped before finishing or has not reported progress for over an hour. | [default to undefined]
 **created_at** | **string** | When the setup was requested. | [default to undefined]
 **updated_at** | **string** | When the setup last reported progress. | [default to undefined]
@@ -19,6 +20,7 @@ import { HostingV1OnboardingsOnboardingResource } from '@hostinger/sdk';
 const instance: HostingV1OnboardingsOnboardingResource = {
     domain,
     username,
+    type,
     status,
     created_at,
     updated_at,

package/docs/HostingV1OnboardingsStartOnboardingRequest.md

@@ -0,0 +1,25 @@
+# HostingV1OnboardingsStartOnboardingRequest
+
+Website type, domain and WordPress settings for a new website setup
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **string** | 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. | [optional] [default to undefined]
+**domain** | **string** | Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain. | [optional] [default to undefined]
+**wordpress** | [**HostingV1OnboardingsStartOnboardingRequestWordpress**](HostingV1OnboardingsStartOnboardingRequestWordpress.md) |  | [optional] [default to undefined]
+
+## Example
+
+```typescript
+import { HostingV1OnboardingsStartOnboardingRequest } from '@hostinger/sdk';
+
+const instance: HostingV1OnboardingsStartOnboardingRequest = {
+    type,
+    domain,
+    wordpress,
+};
+```
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/HostingV1OnboardingsStartOnboardingRequestWordpress.md

@@ -0,0 +1,25 @@
+# HostingV1OnboardingsStartOnboardingRequestWordpress
+
+WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**language** | **string** | WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted. | [optional] [default to undefined]
+**is_ai_builder** | **boolean** | When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted. | [optional] [default to undefined]
+**admin** | [**HostingV1OnboardingsStartOnboardingRequestWordpressAdmin**](HostingV1OnboardingsStartOnboardingRequestWordpressAdmin.md) |  | [default to undefined]
+
+## Example
+
+```typescript
+import { HostingV1OnboardingsStartOnboardingRequestWordpress } from '@hostinger/sdk';
+
+const instance: HostingV1OnboardingsStartOnboardingRequestWordpress = {
+    language,
+    is_ai_builder,
+    admin,
+};
+```
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/HostingV1OnboardingsStartOnboardingRequestWordpressAdmin.md

@@ -0,0 +1,25 @@
+# HostingV1OnboardingsStartOnboardingRequestWordpressAdmin
+
+WordPress administrator account
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**user** | **string** | WordPress admin username (letters, numbers, and underscore) | [default to undefined]
+**password** | **string** | WordPress admin password (8-50 characters, mixed case, a digit, and not compromised) | [default to undefined]
+**email** | **string** | WordPress admin email address | [default to undefined]
+
+## Example
+
+```typescript
+import { HostingV1OnboardingsStartOnboardingRequestWordpressAdmin } from '@hostinger/sdk';
+
+const instance: HostingV1OnboardingsStartOnboardingRequestWordpressAdmin = {
+    user,
+    password,
+    email,
+};
+```
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/HostingWebsitesApi.md

@@ -9,6 +9,7 @@ All URIs are relative to *https://developers.hostinger.com*
 |[**deployStaticSiteArchiveV1**](#deploystaticsitearchivev1) | **POST** /api/hosting/v1/accounts/{username}/websites/{domain}/deploy | Deploy static site archive|
 |[**listWebsiteSetupsV1**](#listwebsitesetupsv1) | **GET** /api/hosting/v1/onboardings | List website setups|
 |[**listWebsitesV1**](#listwebsitesv1) | **GET** /api/hosting/v1/websites | List websites|
+|[**startWebsiteSetupV1**](#startwebsitesetupv1) | **POST** /api/hosting/v1/orders/{order_id}/onboardings | Start website setup|
 
 # **createWebsiteV1**
 > CommonSuccessEmptyResource createWebsiteV1(hostingV1WebsitesCreateWebsiteRequest)
@@ -183,7 +184,7 @@ const { status, data } = await apiInstance.deployStaticSiteArchiveV1(
 # **listWebsiteSetupsV1**
 > Array<HostingV1OnboardingsOnboardingResource> listWebsiteSetupsV1()
 
-Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first.  Meant for polling right after creating a website: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `failed` means the setup stopped before finishing or has not reported progress for over an hour. Setups older than 24 hours are not listed.
+Returns the website setups started in the last 24 hours for the hosting accounts accessible to the authenticated client, newest first. Narrow the list with the `order_id`, `subscription_id` or `domain` filters.  Meant for polling right after creating a website or starting a website setup: the website shows up in the websites list before its server-side setup has finished, and while the setup is `running` endpoints that operate on that website may respond with `404` or `409`. Poll this endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. `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.
 
 ### Example
 
@@ -196,9 +197,13 @@ import {
 const configuration = new Configuration();
 const apiInstance = new HostingWebsitesApi(configuration);
 
+let orderId: number; //Order ID (optional) (default to undefined)
+let subscriptionId: string; //Filter by hosting order subscription ID (optional) (default to undefined)
 let domain: string; //Filter by domain name (exact match) (optional) (default to undefined)
 
 const { status, data } = await apiInstance.listWebsiteSetupsV1(
+    orderId,
+    subscriptionId,
     domain
 );
 ```
@@ -207,6 +212,8 @@ const { status, data } = await apiInstance.listWebsiteSetupsV1(
 
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
+| **orderId** | [**number**] | Order ID | (optional) defaults to undefined|
+| **subscriptionId** | [**string**] | Filter by hosting order subscription ID | (optional) defaults to undefined|
 | **domain** | [**string**] | Filter by domain name (exact match) | (optional) defaults to undefined|
 
 
@@ -305,3 +312,63 @@ const { status, data } = await apiInstance.listWebsitesV1(
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
+# **startWebsiteSetupV1**
+> HostingV1OnboardingsOnboardingResource startWebsiteSetupV1(hostingV1OnboardingsStartOnboardingRequest)
+
+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.  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.  The order must already have a hosting account: to create the first website on a new hosting plan use the create website endpoint, which takes the `datacenter_code`. Returns 404 when the order does not exist or is not accessible to the authenticated client, and 409 with a `Retry-After` header while a setup for the same domain is still running.
+
+### Example
+
+```typescript
+import {
+    HostingWebsitesApi,
+    Configuration,
+    HostingV1OnboardingsStartOnboardingRequest
+} from '@hostinger/sdk';
+
+const configuration = new Configuration();
+const apiInstance = new HostingWebsitesApi(configuration);
+
+let orderId: number; //Hosting order ID. List orders to find available IDs. (default to undefined)
+let hostingV1OnboardingsStartOnboardingRequest: HostingV1OnboardingsStartOnboardingRequest; //
+
+const { status, data } = await apiInstance.startWebsiteSetupV1(
+    orderId,
+    hostingV1OnboardingsStartOnboardingRequest
+);
+```
+
+### Parameters
+
+|Name | Type | Description  | Notes|
+|------------- | ------------- | ------------- | -------------|
+| **hostingV1OnboardingsStartOnboardingRequest** | **HostingV1OnboardingsStartOnboardingRequest**|  | |
+| **orderId** | [**number**] | Hosting order ID. List orders to find available IDs. | defaults to undefined|
+
+
+### Return type
+
+**HostingV1OnboardingsOnboardingResource**
+
+### Authorization
+
+[apiToken](../README.md#apiToken)
+
+### HTTP request headers
+
+ - **Content-Type**: application/json
+ - **Accept**: application/json
+
+
+### HTTP response details
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+|**201** | Created response |  -  |
+|**422** | Validation error response |  -  |
+|**401** | Unauthenticated response |  -  |
+|**404** | Error response |  -  |
+|**409** | Conflict response. &#x60;Retry-After&#x60;, when present, is the number of seconds to wait before retrying. |  * Retry-After - Seconds to wait before retrying the request <br>  |
+|**500** | Error response |  -  |
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
+

package/docs/WordPressInstallationsApi.md

@@ -307,7 +307,7 @@ const { status, data } = await apiInstance.importWordPressWebsiteV1(
 # **installWordPressV1**
 > CommonSuccessEmptyResource installWordPressV1(wordPressV1InstallationsInstallWordPressRequest)
 
-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.  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.
+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.  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.  Returns 422 when the account already uses all the databases its plan allows, unless `database.name` is an existing database on the account.
 
 ### Example
 

package/docs/WordPressV1InstallationsInstallWordPressRequestDatabase.md

@@ -1,13 +1,13 @@
 # WordPressV1InstallationsInstallWordPressRequestDatabase
 
-Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.
+Optional. If the named database already exists on the account, it is used for this WordPress install. Otherwise a new database is created with this name, or with a generated name when database is omitted or null. A new database gets a random database user and counts toward the plan\'s database limit.
 
 ## Properties
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **name** | **string** | Database name (username prefix added if missing) | [optional] [default to undefined]
-**password** | **string** |  | [optional] [default to undefined]
+**password** | **string** | Password for a new database. Random when omitted or null. Ignored when the named database already exists. | [optional] [default to undefined]
 
 ## Example