@hostinger/sdk 1.58.3 → 1.59.1

package/dist/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.3
+ * 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
@@ -8702,6 +8702,12 @@ export interface HostingV1OnboardingsOnboardingResource {
      * @memberof HostingV1OnboardingsOnboardingResource
      */
     'username': 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.
+     * @type {string}
+     * @memberof HostingV1OnboardingsOnboardingResource
+     */
+    'type': string | null;
     /**
      * `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.
      * @type {string}
@@ -8727,6 +8733,88 @@ export declare const HostingV1OnboardingsOnboardingResourceStatusEnum: {
     readonly Failed: "failed";
 };
 export type HostingV1OnboardingsOnboardingResourceStatusEnum = typeof HostingV1OnboardingsOnboardingResourceStatusEnum[keyof typeof HostingV1OnboardingsOnboardingResourceStatusEnum];
+/**
+ * Website type, domain and WordPress settings for a new website setup
+ * @export
+ * @interface HostingV1OnboardingsStartOnboardingRequest
+ */
+export interface HostingV1OnboardingsStartOnboardingRequest {
+    /**
+     * 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.
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequest
+     */
+    'type': HostingV1OnboardingsStartOnboardingRequestTypeEnum | null;
+    /**
+     * Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain.
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequest
+     */
+    'domain': string | null;
+    /**
+     *
+     * @type {HostingV1OnboardingsStartOnboardingRequestWordpress}
+     * @memberof HostingV1OnboardingsStartOnboardingRequest
+     */
+    'wordpress': HostingV1OnboardingsStartOnboardingRequestWordpress | null;
+}
+export declare const HostingV1OnboardingsStartOnboardingRequestTypeEnum: {
+    readonly Wordpress: "wordpress";
+    readonly HeadlessWordpress: "headless_wordpress";
+    readonly HeadlessEcommerce: "headless_ecommerce";
+    readonly HeadlessPocketbase: "headless_pocketbase";
+};
+export type HostingV1OnboardingsStartOnboardingRequestTypeEnum = typeof HostingV1OnboardingsStartOnboardingRequestTypeEnum[keyof typeof HostingV1OnboardingsStartOnboardingRequestTypeEnum];
+/**
+ * WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.
+ * @export
+ * @interface HostingV1OnboardingsStartOnboardingRequestWordpress
+ */
+export interface HostingV1OnboardingsStartOnboardingRequestWordpress {
+    /**
+     * WordPress locale, for example `en_US` or `lt_LT`. Defaults to `en_US` when omitted.
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpress
+     */
+    'language': string | null;
+    /**
+     * When `true`, installs the Hostinger AI theme (`hostinger-ai-theme`). Defaults to `false` when omitted.
+     * @type {boolean}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpress
+     */
+    'is_ai_builder': boolean | null;
+    /**
+     *
+     * @type {HostingV1OnboardingsStartOnboardingRequestWordpressAdmin}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpress
+     */
+    'admin': HostingV1OnboardingsStartOnboardingRequestWordpressAdmin;
+}
+/**
+ * WordPress administrator account
+ * @export
+ * @interface HostingV1OnboardingsStartOnboardingRequestWordpressAdmin
+ */
+export interface HostingV1OnboardingsStartOnboardingRequestWordpressAdmin {
+    /**
+     * WordPress admin username (letters, numbers, and underscore)
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpressAdmin
+     */
+    'user': string;
+    /**
+     * WordPress admin password (8-50 characters, mixed case, a digit, and not compromised)
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpressAdmin
+     */
+    'password': string;
+    /**
+     * WordPress admin email address
+     * @type {string}
+     * @memberof HostingV1OnboardingsStartOnboardingRequestWordpressAdmin
+     */
+    'email': string;
+}
 /**
  *
  * @export
@@ -25802,13 +25890,15 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
      */
     deployStaticSiteArchiveV1: (username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * 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?: string | null, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    listWebsiteSetupsV1: (orderId?: number | null, subscriptionId?: string | null, domain?: string | null, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * 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.
      * @summary List websites
@@ -25823,6 +25913,15 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
      * @throws {RequiredError}
      */
     listWebsitesV1: (page?: number, perPage?: number, username?: string | null, orderId?: number | null, isEnabled?: boolean | null, domain?: string | null, websiteTypes?: Array<ListWebsitesV1WebsiteTypesEnum>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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: number, hostingV1OnboardingsStartOnboardingRequest: HostingV1OnboardingsStartOnboardingRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
 };
 /**
  * HostingWebsitesApi - functional programming interface
@@ -25856,13 +25955,15 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
      */
     deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
-     * 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?: string | null, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1OnboardingsOnboardingResource>>>;
+    listWebsiteSetupsV1(orderId?: number | null, subscriptionId?: string | null, domain?: string | null, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1OnboardingsOnboardingResource>>>;
     /**
      * 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.
      * @summary List websites
@@ -25877,6 +25978,15 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     listWebsitesV1(page?: number, perPage?: number, username?: string | null, orderId?: number | null, isEnabled?: boolean | null, domain?: string | null, websiteTypes?: Array<ListWebsitesV1WebsiteTypesEnum>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingListWebsitesV1200Response>>;
+    /**
+     * 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: number, hostingV1OnboardingsStartOnboardingRequest: HostingV1OnboardingsStartOnboardingRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1OnboardingsOnboardingResource>>;
 };
 /**
  * HostingWebsitesApi - factory interface
@@ -25910,13 +26020,15 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
      */
     deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
     /**
-     * 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?: string | null, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1OnboardingsOnboardingResource>>;
+    listWebsiteSetupsV1(orderId?: number | null, subscriptionId?: string | null, domain?: string | null, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1OnboardingsOnboardingResource>>;
     /**
      * 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.
      * @summary List websites
@@ -25931,6 +26043,15 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
      * @throws {RequiredError}
      */
     listWebsitesV1(page?: number, perPage?: number, username?: string | null, orderId?: number | null, isEnabled?: boolean | null, domain?: string | null, websiteTypes?: Array<ListWebsitesV1WebsiteTypesEnum>, options?: RawAxiosRequestConfig): AxiosPromise<HostingListWebsitesV1200Response>;
+    /**
+     * 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: number, hostingV1OnboardingsStartOnboardingRequest: HostingV1OnboardingsStartOnboardingRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1OnboardingsOnboardingResource>;
 };
 /**
  * HostingWebsitesApi - object-oriented interface
@@ -25969,14 +26090,16 @@ export declare class HostingWebsitesApi extends BaseAPI {
      */
     deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
-     * 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?: string | null, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1OnboardingsOnboardingResource[], any, {}, any>>;
+    listWebsiteSetupsV1(orderId?: number | null, subscriptionId?: string | null, domain?: string | null, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1OnboardingsOnboardingResource[], any, {}, any>>;
     /**
      * 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.
      * @summary List websites
@@ -25992,6 +26115,16 @@ export declare class HostingWebsitesApi extends BaseAPI {
      * @memberof HostingWebsitesApi
      */
     listWebsitesV1(page?: number, perPage?: number, username?: string | null, orderId?: number | null, isEnabled?: boolean | null, domain?: string | null, websiteTypes?: Array<ListWebsitesV1WebsiteTypesEnum>, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingListWebsitesV1200Response, any, {}, any>>;
+    /**
+     * 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: number, hostingV1OnboardingsStartOnboardingRequest: HostingV1OnboardingsStartOnboardingRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1OnboardingsOnboardingResource, any, {}, any>>;
 }
 /**
  * @export