@hostinger/sdk 1.58.1 → 1.58.3

package/README.md

@@ -1,9 +1,9 @@
-## @hostinger/sdk@1.58.1
+## @hostinger/sdk@1.58.3
 
 For more information, please visit [https://developers.hostinger.com](https://developers.hostinger.com).
 
 ### Usage
 
 ```
-npm install @hostinger/sdk@1.58.1 --save
+npm install @hostinger/sdk@1.58.3 --save
 ```

package/api.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -16253,7 +16253,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestCredentials {
     'password': string;
 }
 /**
- * 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.
  * @export
  * @interface WordPressV1InstallationsInstallWordPressRequestDatabase
  */
@@ -16265,7 +16265,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestDatabase {
      */
     'name': string;
     /**
-     * 
+     * Password for a new database. Random when omitted or null. Ignored when the named database already exists.
      * @type {string}
      * @memberof WordPressV1InstallationsInstallWordPressRequestDatabase
      */
@@ -34098,7 +34098,7 @@ export type ListNodeJsVulnerabilitiesV1SeveritiesEnum = typeof ListNodeJsVulnera
 export const HostingOrdersApiAxiosParamCreator = function (configuration?: Configuration) {
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -34162,7 +34162,7 @@ export const HostingOrdersApiFp = function(configuration?: Configuration) {
     const localVarAxiosParamCreator = HostingOrdersApiAxiosParamCreator(configuration)
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -34187,7 +34187,7 @@ export const HostingOrdersApiFactory = function (configuration?: Configuration,
     const localVarFp = HostingOrdersApiFp(configuration)
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -34210,7 +34210,7 @@ export const HostingOrdersApiFactory = function (configuration?: Configuration,
  */
 export class HostingOrdersApi extends BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -35459,7 +35459,7 @@ export class HostingSSLApi extends BaseAPI {
 export const HostingWebsitesApiAxiosParamCreator = function (configuration?: Configuration) {
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest 
          * @param {*} [options] Override http request option.
@@ -35703,7 +35703,7 @@ export const HostingWebsitesApiFp = function(configuration?: Configuration) {
     const localVarAxiosParamCreator = HostingWebsitesApiAxiosParamCreator(configuration)
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest 
          * @param {*} [options] Override http request option.
@@ -35781,7 +35781,7 @@ export const HostingWebsitesApiFactory = function (configuration?: Configuration
     const localVarFp = HostingWebsitesApiFp(configuration)
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest 
          * @param {*} [options] Override http request option.
@@ -35849,7 +35849,7 @@ export const HostingWebsitesApiFactory = function (configuration?: Configuration
  */
 export class HostingWebsitesApi extends BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest 
      * @param {*} [options] Override http request option.
@@ -50296,7 +50296,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 
@@ -50597,7 +50597,7 @@ export const WordPressInstallationsApiFp = function(configuration?: Configuratio
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || 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 
@@ -50730,7 +50730,7 @@ export const WordPressInstallationsApiFactory = function (configuration?: Config
             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 
@@ -50863,7 +50863,7 @@ export class WordPressInstallationsApi extends BaseAPI {
     }
 
     /**
-     * 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/base.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/common.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/configuration.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -48,7 +48,7 @@ export class Configuration {
         this.baseOptions = {
             ...param.baseOptions,
             headers: {
-                'User-Agent': "hostinger-typescript-sdk/1.58.1",
+                'User-Agent': "hostinger-typescript-sdk/1.58.3",
                 ...param.baseOptions?.headers,
             },
         };

package/dist/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -15890,7 +15890,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestCredentials {
     'password': string;
 }
 /**
- * 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.
  * @export
  * @interface WordPressV1InstallationsInstallWordPressRequestDatabase
  */
@@ -15902,7 +15902,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestDatabase {
      */
     'name': string;
     /**
-     *
+     * Password for a new database. Random when omitted or null. Ignored when the named database already exists.
      * @type {string}
      * @memberof WordPressV1InstallationsInstallWordPressRequestDatabase
      */
@@ -25104,7 +25104,7 @@ export type ListNodeJsVulnerabilitiesV1SeveritiesEnum = typeof ListNodeJsVulnera
  */
 export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25121,7 +25121,7 @@ export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configu
  */
 export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25138,7 +25138,7 @@ export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingOrdersApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25157,7 +25157,7 @@ export declare const HostingOrdersApiFactory: (configuration?: Configuration, ba
  */
 export declare class HostingOrdersApi extends BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25776,7 +25776,7 @@ export declare class HostingSSLApi extends BaseAPI {
  */
 export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25830,7 +25830,7 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
  */
 export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25884,7 +25884,7 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingWebsitesApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25940,7 +25940,7 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
  */
 export declare class HostingWebsitesApi extends BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -32939,7 +32939,7 @@ export declare const WordPressInstallationsApiAxiosParamCreator: (configuration?
      */
     importWordPressWebsiteV1: (username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * 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
@@ -33038,7 +33038,7 @@ export declare const WordPressInstallationsApiFp: (configuration?: Configuration
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
-     * 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
@@ -33137,7 +33137,7 @@ export declare const WordPressInstallationsApiFactory: (configuration?: Configur
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
     /**
-     * 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
@@ -33243,7 +33243,7 @@ export declare class WordPressInstallationsApi extends BaseAPI {
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
-     * 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/api.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -17058,7 +17058,7 @@ exports.ListNodeJsVulnerabilitiesV1SeveritiesEnum = {
 const HostingOrdersApiAxiosParamCreator = function (configuration) {
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -17112,7 +17112,7 @@ const HostingOrdersApiFp = function (configuration) {
     const localVarAxiosParamCreator = (0, exports.HostingOrdersApiAxiosParamCreator)(configuration);
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -17140,7 +17140,7 @@ const HostingOrdersApiFactory = function (configuration, basePath, axios) {
     const localVarFp = (0, exports.HostingOrdersApiFp)(configuration);
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -17163,7 +17163,7 @@ exports.HostingOrdersApiFactory = HostingOrdersApiFactory;
  */
 class HostingOrdersApi extends base_1.BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -18346,7 +18346,7 @@ exports.HostingSSLApi = HostingSSLApi;
 const HostingWebsitesApiAxiosParamCreator = function (configuration) {
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18550,7 +18550,7 @@ const HostingWebsitesApiFp = function (configuration) {
     const localVarAxiosParamCreator = (0, exports.HostingWebsitesApiAxiosParamCreator)(configuration);
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18643,7 +18643,7 @@ const HostingWebsitesApiFactory = function (configuration, basePath, axios) {
     const localVarFp = (0, exports.HostingWebsitesApiFp)(configuration);
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18711,7 +18711,7 @@ exports.HostingWebsitesApiFactory = HostingWebsitesApiFactory;
  */
 class HostingWebsitesApi extends base_1.BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -32294,7 +32294,7 @@ const WordPressInstallationsApiAxiosParamCreator = 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
@@ -32575,7 +32575,7 @@ 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
@@ -32723,7 +32723,7 @@ const WordPressInstallationsApiFactory = function (configuration, basePath, axio
             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
@@ -32851,7 +32851,7 @@ class WordPressInstallationsApi extends base_1.BaseAPI {
         return (0, exports.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/base.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/base.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/common.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/common.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/configuration.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/configuration.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -16,7 +16,7 @@ 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.1" }, (_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.58.3" }, (_a = param.baseOptions) === null || _a === void 0 ? void 0 : _a.headers) });
         this.formDataCtor = param.formDataCtor;
     }
     /**

package/dist/esm/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -15890,7 +15890,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestCredentials {
     'password': string;
 }
 /**
- * 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.
  * @export
  * @interface WordPressV1InstallationsInstallWordPressRequestDatabase
  */
@@ -15902,7 +15902,7 @@ export interface WordPressV1InstallationsInstallWordPressRequestDatabase {
      */
     'name': string;
     /**
-     *
+     * Password for a new database. Random when omitted or null. Ignored when the named database already exists.
      * @type {string}
      * @memberof WordPressV1InstallationsInstallWordPressRequestDatabase
      */
@@ -25104,7 +25104,7 @@ export type ListNodeJsVulnerabilitiesV1SeveritiesEnum = typeof ListNodeJsVulnera
  */
 export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25121,7 +25121,7 @@ export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configu
  */
 export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25138,7 +25138,7 @@ export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingOrdersApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25157,7 +25157,7 @@ export declare const HostingOrdersApiFactory: (configuration?: Configuration, ba
  */
 export declare class HostingOrdersApi extends BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25776,7 +25776,7 @@ export declare class HostingSSLApi extends BaseAPI {
  */
 export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25830,7 +25830,7 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
  */
 export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25884,7 +25884,7 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingWebsitesApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25940,7 +25940,7 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
  */
 export declare class HostingWebsitesApi extends BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -32939,7 +32939,7 @@ export declare const WordPressInstallationsApiAxiosParamCreator: (configuration?
      */
     importWordPressWebsiteV1: (username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * 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
@@ -33038,7 +33038,7 @@ export declare const WordPressInstallationsApiFp: (configuration?: Configuration
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
-     * 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
@@ -33137,7 +33137,7 @@ export declare const WordPressInstallationsApiFactory: (configuration?: Configur
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
     /**
-     * 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
@@ -33243,7 +33243,7 @@ export declare class WordPressInstallationsApi extends BaseAPI {
      */
     importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
-     * 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/api.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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
@@ -16868,7 +16868,7 @@ export const ListNodeJsVulnerabilitiesV1SeveritiesEnum = {
 export const HostingOrdersApiAxiosParamCreator = function (configuration) {
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -16921,7 +16921,7 @@ export const HostingOrdersApiFp = function (configuration) {
     const localVarAxiosParamCreator = HostingOrdersApiAxiosParamCreator(configuration);
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -16948,7 +16948,7 @@ export const HostingOrdersApiFactory = function (configuration, basePath, axios)
     const localVarFp = HostingOrdersApiFp(configuration);
     return {
         /**
-         * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+         * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
          * @summary List orders
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -16970,7 +16970,7 @@ export const HostingOrdersApiFactory = function (configuration, basePath, axios)
  */
 export class HostingOrdersApi extends BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -18140,7 +18140,7 @@ export class HostingSSLApi extends BaseAPI {
 export const HostingWebsitesApiAxiosParamCreator = function (configuration) {
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18343,7 +18343,7 @@ export const HostingWebsitesApiFp = function (configuration) {
     const localVarAxiosParamCreator = HostingWebsitesApiAxiosParamCreator(configuration);
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18435,7 +18435,7 @@ export const HostingWebsitesApiFactory = function (configuration, basePath, axio
     const localVarFp = HostingWebsitesApiFp(configuration);
     return {
         /**
-         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+         * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
          * @summary Create website
          * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
          * @param {*} [options] Override http request option.
@@ -18502,7 +18502,7 @@ export const HostingWebsitesApiFactory = function (configuration, basePath, axio
  */
 export class HostingWebsitesApi extends BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -31956,7 +31956,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 +32236,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 +32383,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 +32510,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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1" }, (_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.58.3" }, (_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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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.1
+ * API Version: 1.58.3
  *
  * 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/HostingOrdersApi.md

@@ -9,7 +9,7 @@ All URIs are relative to *https://developers.hostinger.com*
 # **listOrdersV1**
 > HostingListOrdersV1200Response listOrdersV1()
 
-Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
 
 ### Example
 

package/docs/HostingWebsitesApi.md

@@ -13,7 +13,7 @@ All URIs are relative to *https://developers.hostinger.com*
 # **createWebsiteV1**
 > CommonSuccessEmptyResource createWebsiteV1(hostingV1WebsitesCreateWebsiteRequest)
 
-Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. 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. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
 
 ### Example
 

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
 

package/index.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.1
+ * API Version: 1.58.3
  *
  * 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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hostinger/sdk",
-  "version": "1.58.1",
+  "version": "1.58.3",
   "description": "Hostinger API TypeScript SDK",
   "author": "Hostinger",
   "repository": {