hostinger-api-sdk 1.40.0 → 1.40.2

package/README.md

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

package/api.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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
@@ -26174,54 +26174,6 @@ export type ListWebsiteFilesAndDirectoriesV1FileTypesEnum = typeof ListWebsiteFi
  */
 export const HostingNodeJSApiAxiosParamCreator = function (configuration?: Configuration) {
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username 
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest 
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1: async (username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
-            // verify required parameter 'username' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'username', username)
-            // verify required parameter 'domain' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'domain', domain)
-            // verify required parameter 'hostingV1NodeJsCreateFromArchiveRequest' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'hostingV1NodeJsCreateFromArchiveRequest', hostingV1NodeJsCreateFromArchiveRequest)
-            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive`
-                .replace(`{${"username"}}`, encodeURIComponent(String(username)))
-                .replace(`{${"domain"}}`, encodeURIComponent(String(domain)));
-            // use dummy base URL string because the URL constructor only accepts absolute URLs.
-            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
-            let baseOptions;
-            if (configuration) {
-                baseOptions = configuration.baseOptions;
-            }
-
-            const localVarRequestOptions = { method: 'POST', ...baseOptions, ...options};
-            const localVarHeaderParameter = {} as any;
-            const localVarQueryParameter = {} as any;
-
-            // authentication apiToken required
-            // http bearer authentication required
-            await setBearerAuthToObject(localVarHeaderParameter, configuration)
-
-
-    
-            localVarHeaderParameter['Content-Type'] = 'application/json';
-
-            setSearchParams(localVarUrlObj, localVarQueryParameter);
-            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
-            localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
-            localVarRequestOptions.data = serializeDataIfNeeded(hostingV1NodeJsCreateFromArchiveRequest, localVarRequestOptions, configuration)
-
-            return {
-                url: toPathString(localVarUrlObj),
-                options: localVarRequestOptions,
-            };
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -26574,20 +26526,6 @@ export const HostingNodeJSApiAxiosParamCreator = function (configuration?: Confi
 export const HostingNodeJSApiFp = function(configuration?: Configuration) {
     const localVarAxiosParamCreator = HostingNodeJSApiAxiosParamCreator(configuration)
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username 
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest 
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        async createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildResource>> {
-            const localVarAxiosArgs = await localVarAxiosParamCreator.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options);
-            const localVarOperationServerBasePath = operationServerMap['HostingNodeJSApi.createNodeJSBuildFromArchiveV1']?.[0]?.url;
-            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -26698,18 +26636,6 @@ export const HostingNodeJSApiFp = function(configuration?: Configuration) {
 export const HostingNodeJSApiFactory = function (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) {
     const localVarFp = HostingNodeJSApiFp(configuration)
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username 
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest 
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildResource> {
-            return localVarFp.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(axios, basePath));
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -26806,20 +26732,6 @@ export const HostingNodeJSApiFactory = function (configuration?: Configuration,
  * @extends {BaseAPI}
  */
 export class HostingNodeJSApi extends BaseAPI {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username 
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest 
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     * @memberof HostingNodeJSApi
-     */
-    public createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig) {
-        return HostingNodeJSApiFp(this.configuration).createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(this.axios, this.basePath));
-    }
-
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs

package/base.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.40.0",
+                'User-Agent': "hostinger-typescript-sdk/1.40.2",
                 ...param.baseOptions?.headers,
             },
         };

package/dist/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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
@@ -19589,16 +19589,6 @@ export type ListWebsiteFilesAndDirectoriesV1FileTypesEnum = typeof ListWebsiteFi
  * @export
  */
 export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configuration) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1: (username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19677,16 +19667,6 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
  * @export
  */
 export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildResource>>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19765,16 +19745,6 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
  * @export
  */
 export declare const HostingNodeJSApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildResource>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19855,17 +19825,6 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
  * @extends {BaseAPI}
  */
 export declare class HostingNodeJSApi extends BaseAPI {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     * @memberof HostingNodeJSApi
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1NodeJsBuildResource, any, {}, any>>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs

package/dist/api.js

@@ -4,7 +4,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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
@@ -12443,47 +12443,6 @@ exports.ListWebsiteFilesAndDirectoriesV1FileTypesEnum = {
  */
 const HostingNodeJSApiAxiosParamCreator = function (configuration) {
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1: (username_1, domain_1, hostingV1NodeJsCreateFromArchiveRequest_1, ...args_1) => __awaiter(this, [username_1, domain_1, hostingV1NodeJsCreateFromArchiveRequest_1, ...args_1], void 0, function* (username, domain, hostingV1NodeJsCreateFromArchiveRequest, options = {}) {
-            // verify required parameter 'username' is not null or undefined
-            (0, common_1.assertParamExists)('createNodeJSBuildFromArchiveV1', 'username', username);
-            // verify required parameter 'domain' is not null or undefined
-            (0, common_1.assertParamExists)('createNodeJSBuildFromArchiveV1', 'domain', domain);
-            // verify required parameter 'hostingV1NodeJsCreateFromArchiveRequest' is not null or undefined
-            (0, common_1.assertParamExists)('createNodeJSBuildFromArchiveV1', 'hostingV1NodeJsCreateFromArchiveRequest', hostingV1NodeJsCreateFromArchiveRequest);
-            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive`
-                .replace(`{${"username"}}`, encodeURIComponent(String(username)))
-                .replace(`{${"domain"}}`, encodeURIComponent(String(domain)));
-            // use dummy base URL string because the URL constructor only accepts absolute URLs.
-            const localVarUrlObj = new URL(localVarPath, common_1.DUMMY_BASE_URL);
-            let baseOptions;
-            if (configuration) {
-                baseOptions = configuration.baseOptions;
-            }
-            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
-            const localVarHeaderParameter = {};
-            const localVarQueryParameter = {};
-            // authentication apiToken required
-            // http bearer authentication required
-            yield (0, common_1.setBearerAuthToObject)(localVarHeaderParameter, configuration);
-            localVarHeaderParameter['Content-Type'] = 'application/json';
-            (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
-            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
-            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
-            localVarRequestOptions.data = (0, common_1.serializeDataIfNeeded)(hostingV1NodeJsCreateFromArchiveRequest, localVarRequestOptions, configuration);
-            return {
-                url: (0, common_1.toPathString)(localVarUrlObj),
-                options: localVarRequestOptions,
-            };
-        }),
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -12786,23 +12745,6 @@ exports.HostingNodeJSApiAxiosParamCreator = HostingNodeJSApiAxiosParamCreator;
 const HostingNodeJSApiFp = function (configuration) {
     const localVarAxiosParamCreator = (0, exports.HostingNodeJSApiAxiosParamCreator)(configuration);
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-            return __awaiter(this, void 0, void 0, function* () {
-                var _a, _b;
-                const localVarAxiosArgs = yield localVarAxiosParamCreator.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options);
-                const localVarOperationServerBasePath = (_b = (_a = base_1.operationServerMap['HostingNodeJSApi.createNodeJSBuildFromArchiveV1']) === null || _a === void 0 ? void 0 : _a[0]) === null || _b === void 0 ? void 0 : _b.url;
-                return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
-            });
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -12934,18 +12876,6 @@ exports.HostingNodeJSApiFp = HostingNodeJSApiFp;
 const HostingNodeJSApiFactory = function (configuration, basePath, axios) {
     const localVarFp = (0, exports.HostingNodeJSApiFp)(configuration);
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-            return localVarFp.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(axios, basePath));
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -13042,19 +12972,6 @@ exports.HostingNodeJSApiFactory = HostingNodeJSApiFactory;
  * @extends {BaseAPI}
  */
 class HostingNodeJSApi extends base_1.BaseAPI {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     * @memberof HostingNodeJSApi
-     */
-    createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-        return (0, exports.HostingNodeJSApiFp)(this.configuration).createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(this.axios, this.basePath));
-    }
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs

package/dist/base.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.40.0" }, (_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.40.2" }, (_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.42.0
+ * API Version: 1.42.2
  *
  * 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
@@ -19589,16 +19589,6 @@ export type ListWebsiteFilesAndDirectoriesV1FileTypesEnum = typeof ListWebsiteFi
  * @export
  */
 export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configuration) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1: (username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19677,16 +19667,6 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
  * @export
  */
 export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildResource>>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19765,16 +19745,6 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
  * @export
  */
 export declare const HostingNodeJSApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildResource>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs
@@ -19855,17 +19825,6 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
  * @extends {BaseAPI}
  */
 export declare class HostingNodeJSApi extends BaseAPI {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     * @memberof HostingNodeJSApi
-     */
-    createNodeJSBuildFromArchiveV1(username: string, domain: string, hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1NodeJsBuildResource, any, {}, any>>;
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs

package/dist/esm/api.js

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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
@@ -12279,47 +12279,6 @@ export const ListWebsiteFilesAndDirectoriesV1FileTypesEnum = {
  */
 export const HostingNodeJSApiAxiosParamCreator = function (configuration) {
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1: (username_1, domain_1, hostingV1NodeJsCreateFromArchiveRequest_1, ...args_1) => __awaiter(this, [username_1, domain_1, hostingV1NodeJsCreateFromArchiveRequest_1, ...args_1], void 0, function* (username, domain, hostingV1NodeJsCreateFromArchiveRequest, options = {}) {
-            // verify required parameter 'username' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'username', username);
-            // verify required parameter 'domain' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'domain', domain);
-            // verify required parameter 'hostingV1NodeJsCreateFromArchiveRequest' is not null or undefined
-            assertParamExists('createNodeJSBuildFromArchiveV1', 'hostingV1NodeJsCreateFromArchiveRequest', hostingV1NodeJsCreateFromArchiveRequest);
-            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive`
-                .replace(`{${"username"}}`, encodeURIComponent(String(username)))
-                .replace(`{${"domain"}}`, encodeURIComponent(String(domain)));
-            // use dummy base URL string because the URL constructor only accepts absolute URLs.
-            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
-            let baseOptions;
-            if (configuration) {
-                baseOptions = configuration.baseOptions;
-            }
-            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
-            const localVarHeaderParameter = {};
-            const localVarQueryParameter = {};
-            // authentication apiToken required
-            // http bearer authentication required
-            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
-            localVarHeaderParameter['Content-Type'] = 'application/json';
-            setSearchParams(localVarUrlObj, localVarQueryParameter);
-            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
-            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
-            localVarRequestOptions.data = serializeDataIfNeeded(hostingV1NodeJsCreateFromArchiveRequest, localVarRequestOptions, configuration);
-            return {
-                url: toPathString(localVarUrlObj),
-                options: localVarRequestOptions,
-            };
-        }),
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -12621,23 +12580,6 @@ export const HostingNodeJSApiAxiosParamCreator = function (configuration) {
 export const HostingNodeJSApiFp = function (configuration) {
     const localVarAxiosParamCreator = HostingNodeJSApiAxiosParamCreator(configuration);
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-            return __awaiter(this, void 0, void 0, function* () {
-                var _a, _b;
-                const localVarAxiosArgs = yield localVarAxiosParamCreator.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options);
-                const localVarOperationServerBasePath = (_b = (_a = operationServerMap['HostingNodeJSApi.createNodeJSBuildFromArchiveV1']) === null || _a === void 0 ? void 0 : _a[0]) === null || _b === void 0 ? void 0 : _b.url;
-                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
-            });
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -12768,18 +12710,6 @@ export const HostingNodeJSApiFp = function (configuration) {
 export const HostingNodeJSApiFactory = function (configuration, basePath, axios) {
     const localVarFp = HostingNodeJSApiFp(configuration);
     return {
-        /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-         * @summary Create NodeJS build from archive
-         * @param {string} username
-         * @param {string} domain Domain name
-         * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-         * @param {*} [options] Override http request option.
-         * @throws {RequiredError}
-         */
-        createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-            return localVarFp.createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(axios, basePath));
-        },
         /**
          * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
          * @summary Get NodeJS build logs
@@ -12875,19 +12805,6 @@ export const HostingNodeJSApiFactory = function (configuration, basePath, axios)
  * @extends {BaseAPI}
  */
 export class HostingNodeJSApi extends BaseAPI {
-    /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-     * @summary Create NodeJS build from archive
-     * @param {string} username
-     * @param {string} domain Domain name
-     * @param {HostingV1NodeJsCreateFromArchiveRequest} hostingV1NodeJsCreateFromArchiveRequest
-     * @param {*} [options] Override http request option.
-     * @throws {RequiredError}
-     * @memberof HostingNodeJSApi
-     */
-    createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options) {
-        return HostingNodeJSApiFp(this.configuration).createNodeJSBuildFromArchiveV1(username, domain, hostingV1NodeJsCreateFromArchiveRequest, options).then((request) => request(this.axios, this.basePath));
-    }
     /**
      * Retrieve logs from a specific Node.js build process.  To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
      * @summary Get NodeJS build logs

package/dist/esm/base.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.40.0" }, (_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.40.2" }, (_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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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.42.0
+ * API Version: 1.42.2
  *
  * 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/HostingNodeJSApi.md

@@ -4,7 +4,6 @@ All URIs are relative to *https://developers.hostinger.com*
 
 |Method | HTTP request | Description|
 |------------- | ------------- | -------------|
-|[**createNodeJSBuildFromArchiveV1**](#createnodejsbuildfromarchivev1) | **POST** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive | Create NodeJS build from archive|
 |[**getNodeJSBuildLogsV1**](#getnodejsbuildlogsv1) | **GET** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs | Get NodeJS build logs|
 |[**getNodeJsBuildSettingsFromArchiveV1**](#getnodejsbuildsettingsfromarchivev1) | **GET** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/from-archive | Get Node.js build settings from archive|
 |[**listNodeJSBuildsV1**](#listnodejsbuildsv1) | **GET** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds | List NodeJS builds|
@@ -13,67 +12,6 @@ All URIs are relative to *https://developers.hostinger.com*
 |[**restartNodeJsApplicationV1**](#restartnodejsapplicationv1) | **POST** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/server/restart | Restart Node.js application|
 |[**startNodeJsBuildV1**](#startnodejsbuildv1) | **POST** /api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds | Start Node.js build|
 
-# **createNodeJSBuildFromArchiveV1**
-> HostingV1NodeJsBuildResource createNodeJSBuildFromArchiveV1(hostingV1NodeJsCreateFromArchiveRequest)
-
-Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website\'s file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.  Before archiving, exclude `node_modules/` and any build output directories (e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.  Example (zip): ``` zip -r archive.zip . --exclude \"node_modules/_*\" --exclude \"dist/_*\" ```  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
-
-### Example
-
-```typescript
-import {
-    HostingNodeJSApi,
-    Configuration,
-    HostingV1NodeJsCreateFromArchiveRequest
-} from 'hostinger-api-sdk';
-
-const configuration = new Configuration();
-const apiInstance = new HostingNodeJSApi(configuration);
-
-let username: string; // (default to undefined)
-let domain: string; //Domain name (default to undefined)
-let hostingV1NodeJsCreateFromArchiveRequest: HostingV1NodeJsCreateFromArchiveRequest; //
-
-const { status, data } = await apiInstance.createNodeJSBuildFromArchiveV1(
-    username,
-    domain,
-    hostingV1NodeJsCreateFromArchiveRequest
-);
-```
-
-### Parameters
-
-|Name | Type | Description  | Notes|
-|------------- | ------------- | ------------- | -------------|
-| **hostingV1NodeJsCreateFromArchiveRequest** | **HostingV1NodeJsCreateFromArchiveRequest**|  | |
-| **username** | [**string**] |  | defaults to undefined|
-| **domain** | [**string**] | Domain name | defaults to undefined|
-
-
-### Return type
-
-**HostingV1NodeJsBuildResource**
-
-### Authorization
-
-[apiToken](../README.md#apiToken)
-
-### HTTP request headers
-
- - **Content-Type**: application/json
- - **Accept**: application/json
-
-
-### HTTP response details
-| Status code | Description | Response headers |
-|-------------|-------------|------------------|
-|**200** | Success response |  -  |
-|**422** | Validation error response |  -  |
-|**401** | Unauthenticated response |  -  |
-|**500** | Error response |  -  |
-
-[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
-
 # **getNodeJSBuildLogsV1**
 > HostingV1NodeJsBuildLogsResource getNodeJSBuildLogsV1()
 

package/index.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.42.0
+ * API Version: 1.42.2
  *
  * 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-api-sdk",
-  "version": "1.40.0",
+  "version": "1.40.2",
   "description": "Hostinger API TypeScript SDK",
   "author": "Hostinger",
   "repository": {