hostinger-api-sdk 1.37.0 → 1.39.0

package/api.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.39.0
+ * API Version: 1.41.0
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api
@@ -5307,6 +5307,50 @@ export const HostingV1FilesFilesResourceItemsInnerTypeEnum = {
 
 export type HostingV1FilesFilesResourceItemsInnerTypeEnum = typeof HostingV1FilesFilesResourceItemsInnerTypeEnum[keyof typeof HostingV1FilesFilesResourceItemsInnerTypeEnum];
 
+/**
+ * 
+ * @export
+ * @interface HostingV1FilesGenerateUploadUrlRequest
+ */
+export interface HostingV1FilesGenerateUploadUrlRequest {
+    /**
+     * Account username
+     * @type {string}
+     * @memberof HostingV1FilesGenerateUploadUrlRequest
+     */
+    'username': string;
+    /**
+     * Website domain
+     * @type {string}
+     * @memberof HostingV1FilesGenerateUploadUrlRequest
+     */
+    'domain': string;
+}
+/**
+ * 
+ * @export
+ * @interface HostingV1FilesUploadUrlResource
+ */
+export interface HostingV1FilesUploadUrlResource {
+    /**
+     * The TUS upload endpoint URL to send upload requests to
+     * @type {string}
+     * @memberof HostingV1FilesUploadUrlResource
+     */
+    'url': string;
+    /**
+     * Authentication token to pass as the `X-Auth` header in TUS upload requests
+     * @type {string}
+     * @memberof HostingV1FilesUploadUrlResource
+     */
+    'auth_key': string;
+    /**
+     * Authentication token to pass as the `X-Auth-Rest` header in TUS upload requests
+     * @type {string}
+     * @memberof HostingV1FilesUploadUrlResource
+     */
+    'rest_auth_key': string;
+}
 /**
  * 
  * @export
@@ -5471,6 +5515,93 @@ export const HostingV1NodeJsBuildResourceStateEnum = {
 
 export type HostingV1NodeJsBuildResourceStateEnum = typeof HostingV1NodeJsBuildResourceStateEnum[keyof typeof HostingV1NodeJsBuildResourceStateEnum];
 
+/**
+ * 
+ * @export
+ * @interface HostingV1NodeJsBuildSettingsResource
+ */
+export interface HostingV1NodeJsBuildSettingsResource {
+    /**
+     * Node.js application type
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'app_type': HostingV1NodeJsBuildSettingsResourceAppTypeEnum | null;
+    /**
+     * Node.js version
+     * @type {number}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'node_version': number | null;
+    /**
+     * Application root directory
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'root_directory': string | null;
+    /**
+     * Build output directory
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'output_directory': string | null;
+    /**
+     * The npm script to run to build the application
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'build_script': string | null;
+    /**
+     * The main entry point file for the application
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'entry_file': string | null;
+    /**
+     * Package manager
+     * @type {string}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'package_manager': HostingV1NodeJsBuildSettingsResourcePackageManagerEnum | null;
+    /**
+     * The scripts configured in the package.json file
+     * @type {Array<string>}
+     * @memberof HostingV1NodeJsBuildSettingsResource
+     */
+    'available_scripts': Array<string>;
+}
+
+export const HostingV1NodeJsBuildSettingsResourceAppTypeEnum = {
+    CreateReactApp: 'create-react-app',
+    Gatsby: 'gatsby',
+    Vite: 'vite',
+    Angular: 'angular',
+    React: 'react',
+    Vue: 'vue',
+    Parcel: 'parcel',
+    Next: 'next',
+    Nuxt: 'nuxt',
+    Nest: 'nest',
+    Express: 'express',
+    Fastify: 'fastify',
+    Astro: 'astro',
+    Svelte: 'svelte',
+    SvelteKit: 'svelte-kit',
+    Hono: 'hono',
+    ReactRouter: 'react-router',
+    Nitro: 'nitro',
+    Other: 'other'
+} as const;
+
+export type HostingV1NodeJsBuildSettingsResourceAppTypeEnum = typeof HostingV1NodeJsBuildSettingsResourceAppTypeEnum[keyof typeof HostingV1NodeJsBuildSettingsResourceAppTypeEnum];
+export const HostingV1NodeJsBuildSettingsResourcePackageManagerEnum = {
+    Npm: 'npm',
+    Yarn: 'yarn',
+    Pnpm: 'pnpm'
+} as const;
+
+export type HostingV1NodeJsBuildSettingsResourcePackageManagerEnum = typeof HostingV1NodeJsBuildSettingsResourcePackageManagerEnum[keyof typeof HostingV1NodeJsBuildSettingsResourcePackageManagerEnum];
+
 /**
  * 
  * @export
@@ -5566,6 +5697,19 @@ export const HostingV1NodeJsCreateFromArchiveRequestPackageManagerEnum = {
 
 export type HostingV1NodeJsCreateFromArchiveRequestPackageManagerEnum = typeof HostingV1NodeJsCreateFromArchiveRequestPackageManagerEnum[keyof typeof HostingV1NodeJsCreateFromArchiveRequestPackageManagerEnum];
 
+/**
+ * 
+ * @export
+ * @interface HostingV1NodeJsGetBuildSettingsRequest
+ */
+export interface HostingV1NodeJsGetBuildSettingsRequest {
+    /**
+     * The path to the archive file relative to the document root of the vhost
+     * @type {string}
+     * @memberof HostingV1NodeJsGetBuildSettingsRequest
+     */
+    'archive_path': string;
+}
 /**
  * 
  * @export
@@ -5623,6 +5767,125 @@ export interface HostingV1NodeJsSourceOptionsResource {
      */
     'archive_path': string | null;
 }
+/**
+ * 
+ * @export
+ * @interface HostingV1NodeJsStartBuildRequest
+ */
+export interface HostingV1NodeJsStartBuildRequest {
+    /**
+     * Node.js version
+     * @type {number}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'node_version': HostingV1NodeJsStartBuildRequestNodeVersionEnum;
+    /**
+     * Node.js application type
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'app_type': HostingV1NodeJsStartBuildRequestAppTypeEnum | null;
+    /**
+     * Application root directory (where package.json is located) relative to public_html
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'root_directory': string | null;
+    /**
+     * Build output directory relative to the root directory
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'output_directory': string | null;
+    /**
+     * Build script that will be ran to build the application
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'build_script': string | null;
+    /**
+     * The main entry point file for the application
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'entry_file': string | null;
+    /**
+     * Package manager
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'package_manager': HostingV1NodeJsStartBuildRequestPackageManagerEnum | null;
+    /**
+     * The source type of the files
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'source_type': HostingV1NodeJsStartBuildRequestSourceTypeEnum;
+    /**
+     * 
+     * @type {HostingV1NodeJsStartBuildRequestSourceOptions}
+     * @memberof HostingV1NodeJsStartBuildRequest
+     */
+    'source_options': HostingV1NodeJsStartBuildRequestSourceOptions | null;
+}
+
+export const HostingV1NodeJsStartBuildRequestNodeVersionEnum = {
+    NUMBER_18: 18,
+    NUMBER_20: 20,
+    NUMBER_22: 22,
+    NUMBER_24: 24
+} as const;
+
+export type HostingV1NodeJsStartBuildRequestNodeVersionEnum = typeof HostingV1NodeJsStartBuildRequestNodeVersionEnum[keyof typeof HostingV1NodeJsStartBuildRequestNodeVersionEnum];
+export const HostingV1NodeJsStartBuildRequestAppTypeEnum = {
+    CreateReactApp: 'create-react-app',
+    Gatsby: 'gatsby',
+    Vite: 'vite',
+    Angular: 'angular',
+    React: 'react',
+    Vue: 'vue',
+    Parcel: 'parcel',
+    Next: 'next',
+    Nuxt: 'nuxt',
+    Nest: 'nest',
+    Express: 'express',
+    Fastify: 'fastify',
+    Astro: 'astro',
+    Svelte: 'svelte',
+    SvelteKit: 'svelte-kit',
+    Hono: 'hono',
+    ReactRouter: 'react-router',
+    Nitro: 'nitro',
+    Other: 'other'
+} as const;
+
+export type HostingV1NodeJsStartBuildRequestAppTypeEnum = typeof HostingV1NodeJsStartBuildRequestAppTypeEnum[keyof typeof HostingV1NodeJsStartBuildRequestAppTypeEnum];
+export const HostingV1NodeJsStartBuildRequestPackageManagerEnum = {
+    Npm: 'npm',
+    Yarn: 'yarn',
+    Pnpm: 'pnpm'
+} as const;
+
+export type HostingV1NodeJsStartBuildRequestPackageManagerEnum = typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum[keyof typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum];
+export const HostingV1NodeJsStartBuildRequestSourceTypeEnum = {
+    Archive: 'archive'
+} as const;
+
+export type HostingV1NodeJsStartBuildRequestSourceTypeEnum = typeof HostingV1NodeJsStartBuildRequestSourceTypeEnum[keyof typeof HostingV1NodeJsStartBuildRequestSourceTypeEnum];
+
+/**
+ * Source-specific options
+ * @export
+ * @interface HostingV1NodeJsStartBuildRequestSourceOptions
+ */
+export interface HostingV1NodeJsStartBuildRequestSourceOptions {
+    /**
+     * The path to the archive file relative to the document root of the vhost (required if source is \"archive\")
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
+     */
+    'archive_path': string;
+}
 /**
  * 
  * @export
@@ -6032,6 +6295,19 @@ export interface HostingV1WebsitesCreateWebsiteRequest {
      */
     'datacenter_code': string | null;
 }
+/**
+ * 
+ * @export
+ * @interface HostingV1WebsitesDeployArchiveRequest
+ */
+export interface HostingV1WebsitesDeployArchiveRequest {
+    /**
+     * Relative path to the archive file from website root directory
+     * @type {string}
+     * @memberof HostingV1WebsitesDeployArchiveRequest
+     */
+    'archive_path': string;
+}
 /**
  * 
  * @export
@@ -6039,17 +6315,17 @@ export interface HostingV1WebsitesCreateWebsiteRequest {
  */
 export interface HostingV1WebsitesWebsiteResource {
     /**
-     * Website domain
+     * Website domain. Null for U4S websites with no domain attached.
      * @type {string}
      * @memberof HostingV1WebsitesWebsiteResource
      */
-    'domain': string;
+    'domain': string | null;
     /**
-     * Virtual host type
+     * Virtual host type. Only present for CloudLinux websites.
      * @type {string}
      * @memberof HostingV1WebsitesWebsiteResource
      */
-    'vhost_type': HostingV1WebsitesWebsiteResourceVhostTypeEnum;
+    'vhost_type': HostingV1WebsitesWebsiteResourceVhostTypeEnum | null;
     /**
      * Whether website is enabled
      * @type {boolean}
@@ -6057,11 +6333,11 @@ export interface HostingV1WebsitesWebsiteResource {
      */
     'is_enabled': boolean;
     /**
-     * Username
+     * Username. Not applicable for U4S websites.
      * @type {string}
      * @memberof HostingV1WebsitesWebsiteResource
      */
-    'username': string;
+    'username': string | null;
     /**
      * Client ID
      * @type {number}
@@ -6081,17 +6357,29 @@ export interface HostingV1WebsitesWebsiteResource {
      */
     'created_at': string;
     /**
-     * Root directory path
+     * Root directory path. Only present for CloudLinux websites.
      * @type {string}
      * @memberof HostingV1WebsitesWebsiteResource
      */
-    'root_directory': string;
+    'root_directory': string | null;
     /**
      * Parent domain
      * @type {string}
      * @memberof HostingV1WebsitesWebsiteResource
      */
     'parent_domain': string | null;
+    /**
+     * Type of website detected on the underlying platform.
+     * @type {string}
+     * @memberof HostingV1WebsitesWebsiteResource
+     */
+    'website_type': HostingV1WebsitesWebsiteResourceWebsiteTypeEnum;
+    /**
+     * Horizons UUID. Only present for horizons websites.
+     * @type {string}
+     * @memberof HostingV1WebsitesWebsiteResource
+     */
+    'horizons_uuid': string | null;
 }
 
 export const HostingV1WebsitesWebsiteResourceVhostTypeEnum = {
@@ -6102,6 +6390,15 @@ export const HostingV1WebsitesWebsiteResourceVhostTypeEnum = {
 } as const;
 
 export type HostingV1WebsitesWebsiteResourceVhostTypeEnum = typeof HostingV1WebsitesWebsiteResourceVhostTypeEnum[keyof typeof HostingV1WebsitesWebsiteResourceVhostTypeEnum];
+export const HostingV1WebsitesWebsiteResourceWebsiteTypeEnum = {
+    Wordpress: 'wordpress',
+    Builder: 'builder',
+    Horizons: 'horizons',
+    Nodejs: 'nodejs',
+    Other: 'other'
+} as const;
+
+export type HostingV1WebsitesWebsiteResourceWebsiteTypeEnum = typeof HostingV1WebsitesWebsiteResourceWebsiteTypeEnum[keyof typeof HostingV1WebsitesWebsiteResourceWebsiteTypeEnum];
 
 /**
  * 
@@ -12222,6 +12519,25 @@ export interface WordPressV1InstallationsDeleteInstallationRequest {
      */
     'delete_database': boolean;
 }
+/**
+ * 
+ * @export
+ * @interface WordPressV1InstallationsImportWordPressRequest
+ */
+export interface WordPressV1InstallationsImportWordPressRequest {
+    /**
+     * Path to the WordPress archive file (relative to website root)
+     * @type {string}
+     * @memberof WordPressV1InstallationsImportWordPressRequest
+     */
+    'archive_path': string;
+    /**
+     * Path to the database SQL file (relative to website root)
+     * @type {string}
+     * @memberof WordPressV1InstallationsImportWordPressRequest
+     */
+    'sql_path': string;
+}
 /**
  * 
  * @export
@@ -12790,6 +13106,25 @@ export interface WordPressV1PluginsDeactivatePluginRequest {
      */
     'plugin': string;
 }
+/**
+ * 
+ * @export
+ * @interface WordPressV1PluginsDeployPluginRequest
+ */
+export interface WordPressV1PluginsDeployPluginRequest {
+    /**
+     * Slug of the plugin
+     * @type {string}
+     * @memberof WordPressV1PluginsDeployPluginRequest
+     */
+    'slug': string;
+    /**
+     * Relative path to the plugin directory from wp-content/plugins
+     * @type {string}
+     * @memberof WordPressV1PluginsDeployPluginRequest
+     */
+    'plugin_path': string;
+}
 /**
  * 
  * @export
@@ -13085,6 +13420,31 @@ export interface WordPressV1ThemesActivateThemeRequest {
      */
     'theme': string;
 }
+/**
+ * 
+ * @export
+ * @interface WordPressV1ThemesDeployThemeRequest
+ */
+export interface WordPressV1ThemesDeployThemeRequest {
+    /**
+     * Slug of the theme
+     * @type {string}
+     * @memberof WordPressV1ThemesDeployThemeRequest
+     */
+    'slug': string;
+    /**
+     * Relative path to the theme directory from wp-content/themes
+     * @type {string}
+     * @memberof WordPressV1ThemesDeployThemeRequest
+     */
+    'theme_path': string;
+    /**
+     * Whether to activate the theme after deployment
+     * @type {boolean}
+     * @memberof WordPressV1ThemesDeployThemeRequest
+     */
+    'is_activated': boolean | null;
+}
 /**
  * 
  * @export
@@ -14613,6 +14973,44 @@ export class AgencyHostingDomainsApi extends BaseAPI {
  */
 export const AgencyHostingFilesApiAxiosParamCreator = function (configuration?: Configuration) {
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s file storage via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside the website\'s file storage, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {string} websiteUid Agency Plan website UID
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateUploadURLV1: async (websiteUid: string, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'websiteUid' is not null or undefined
+            assertParamExists('generateUploadURLV1', 'websiteUid', websiteUid)
+            const localVarPath = `/api/agency-hosting/v1/websites/{website_uid}/files/upload-urls`
+                .replace(`{${"website_uid"}}`, encodeURIComponent(String(websiteUid)));
+            // 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)
+
+
+    
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * Imports an Agency Plan website from an already-uploaded archive.  Upload the archive to the website\'s root directory via file browser first, then provide its filename in this request. Website contents are overwritten by the archive contents. Supported archive types: .zip, .tar, .tar.gz, .tgz.
          * @summary Import website from archive
@@ -14667,6 +15065,18 @@ export const AgencyHostingFilesApiAxiosParamCreator = function (configuration?:
 export const AgencyHostingFilesApiFp = function(configuration?: Configuration) {
     const localVarAxiosParamCreator = AgencyHostingFilesApiAxiosParamCreator(configuration)
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s file storage via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside the website\'s file storage, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {string} websiteUid Agency Plan website UID
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async generateUploadURLV1(websiteUid: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<AgencyHostingV1FilesUploadUrlResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.generateUploadURLV1(websiteUid, options);
+            const localVarOperationServerBasePath = operationServerMap['AgencyHostingFilesApi.generateUploadURLV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * Imports an Agency Plan website from an already-uploaded archive.  Upload the archive to the website\'s root directory via file browser first, then provide its filename in this request. Website contents are overwritten by the archive contents. Supported archive types: .zip, .tar, .tar.gz, .tgz.
          * @summary Import website from archive
@@ -14690,6 +15100,16 @@ export const AgencyHostingFilesApiFp = function(configuration?: Configuration) {
 export const AgencyHostingFilesApiFactory = function (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) {
     const localVarFp = AgencyHostingFilesApiFp(configuration)
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s file storage via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside the website\'s file storage, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {string} websiteUid Agency Plan website UID
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateUploadURLV1(websiteUid: string, options?: RawAxiosRequestConfig): AxiosPromise<AgencyHostingV1FilesUploadUrlResource> {
+            return localVarFp.generateUploadURLV1(websiteUid, options).then((request) => request(axios, basePath));
+        },
         /**
          * Imports an Agency Plan website from an already-uploaded archive.  Upload the archive to the website\'s root directory via file browser first, then provide its filename in this request. Website contents are overwritten by the archive contents. Supported archive types: .zip, .tar, .tar.gz, .tgz.
          * @summary Import website from archive
@@ -14711,6 +15131,18 @@ export const AgencyHostingFilesApiFactory = function (configuration?: Configurat
  * @extends {BaseAPI}
  */
 export class AgencyHostingFilesApi extends BaseAPI {
+    /**
+     * Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s file storage via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside the website\'s file storage, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+     * @summary Generate upload URL
+     * @param {string} websiteUid Agency Plan website UID
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AgencyHostingFilesApi
+     */
+    public generateUploadURLV1(websiteUid: string, options?: RawAxiosRequestConfig) {
+        return AgencyHostingFilesApiFp(this.configuration).generateUploadURLV1(websiteUid, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * Imports an Agency Plan website from an already-uploaded archive.  Upload the archive to the website\'s root directory via file browser first, then provide its filename in this request. Website contents are overwritten by the archive contents. Supported archive types: .zip, .tar, .tar.gz, .tgz.
      * @summary Import website from archive
@@ -24924,6 +25356,46 @@ export class HostingDomainsApi extends BaseAPI {
  */
 export const HostingFilesApiAxiosParamCreator = function (configuration?: Configuration) {
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files directly to a website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {HostingV1FilesGenerateUploadUrlRequest} hostingV1FilesGenerateUploadUrlRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateUploadURLV1: async (hostingV1FilesGenerateUploadUrlRequest: HostingV1FilesGenerateUploadUrlRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'hostingV1FilesGenerateUploadUrlRequest' is not null or undefined
+            assertParamExists('generateUploadURLV1', 'hostingV1FilesGenerateUploadUrlRequest', hostingV1FilesGenerateUploadUrlRequest)
+            const localVarPath = `/api/hosting/v1/files/upload-urls`;
+            // 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(hostingV1FilesGenerateUploadUrlRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * Get a single file\'s content, relative to a website\'s document root.  Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint.
          * @summary Get website file content
@@ -25060,6 +25532,18 @@ export const HostingFilesApiAxiosParamCreator = function (configuration?: Config
 export const HostingFilesApiFp = function(configuration?: Configuration) {
     const localVarAxiosParamCreator = HostingFilesApiAxiosParamCreator(configuration)
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files directly to a website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {HostingV1FilesGenerateUploadUrlRequest} hostingV1FilesGenerateUploadUrlRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest: HostingV1FilesGenerateUploadUrlRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1FilesUploadUrlResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['HostingFilesApi.generateUploadURLV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * Get a single file\'s content, relative to a website\'s document root.  Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint.
          * @summary Get website file content
@@ -25104,6 +25588,16 @@ export const HostingFilesApiFp = function(configuration?: Configuration) {
 export const HostingFilesApiFactory = function (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) {
     const localVarFp = HostingFilesApiFp(configuration)
     return {
+        /**
+         * Generate a file browser upload URL with authentication credentials for uploading files directly to a website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+         * @summary Generate upload URL
+         * @param {HostingV1FilesGenerateUploadUrlRequest} hostingV1FilesGenerateUploadUrlRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest: HostingV1FilesGenerateUploadUrlRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1FilesUploadUrlResource> {
+            return localVarFp.generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest, options).then((request) => request(axios, basePath));
+        },
         /**
          * Get a single file\'s content, relative to a website\'s document root.  Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint.
          * @summary Get website file content
@@ -25144,6 +25638,18 @@ export const HostingFilesApiFactory = function (configuration?: Configuration, b
  * @extends {BaseAPI}
  */
 export class HostingFilesApi extends BaseAPI {
+    /**
+     * Generate a file browser upload URL with authentication credentials for uploading files directly to a website\'s file storage.  Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the website\'s `public_html` directory via the TUS resumable upload protocol (TUS 1.0.0). Send `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.  1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers    `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or    `PATCH` requests with an `upload-offset` header tracking progress) until complete.  `relative_file_path` is the destination path inside `public_html`, e.g. `app.zip`.  Instead of a TUS client, plain `curl` also works: ``` FILE=app.zip SIZE=$(stat -f%z \"$FILE\")   # stat -c%s on Linux  curl -i -X POST \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Upload-Length: ${SIZE}\" \\   -H \"Upload-Offset: 0\" # -> 201 Created  curl -i -X PATCH \"{url}/${FILE}?override=true\" \\   -H \"X-Auth: {auth_key}\" \\   -H \"X-Auth-Rest: {rest_auth_key}\" \\   -H \"Tus-Resumable: 1.0.0\" \\   -H \"Content-Type: application/offset+octet-stream\" \\   -H \"Upload-Offset: 0\" \\   --data-binary \"@${FILE}\" # -> 204 No Content, Upload-Offset response header equals SIZE when done ```
+     * @summary Generate upload URL
+     * @param {HostingV1FilesGenerateUploadUrlRequest} hostingV1FilesGenerateUploadUrlRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingFilesApi
+     */
+    public generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest: HostingV1FilesGenerateUploadUrlRequest, options?: RawAxiosRequestConfig) {
+        return HostingFilesApiFp(this.configuration).generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * Get a single file\'s content, relative to a website\'s document root.  Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint.
      * @summary Get website file content
@@ -25198,7 +25704,7 @@ 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.  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.
+         * 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
@@ -25287,6 +25793,55 @@ export const HostingNodeJSApiAxiosParamCreator = function (configuration?: Confi
 
 
     
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
+        /**
+         * Auto-detect Node.js build settings from a package.json inside an archive already on the server.  Use this before calling `Start Node.js Build` to preview what settings will be used, or to let the user review and override values (framework, node version, root directory, output directory, build script) before committing to a build.  The archive must already be present on the website\'s file storage. Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. To upload an archive and start a build in one step without inspecting settings first, use the `Create Node.js Build from Archive` endpoint instead.
+         * @summary Get Node.js build settings from archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {string} archivePath The path to the archive file relative to the document root of the vhost
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        getNodeJsBuildSettingsFromArchiveV1: async (username: string, domain: string, archivePath: string, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('getNodeJsBuildSettingsFromArchiveV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('getNodeJsBuildSettingsFromArchiveV1', 'domain', domain)
+            // verify required parameter 'archivePath' is not null or undefined
+            assertParamExists('getNodeJsBuildSettingsFromArchiveV1', 'archivePath', archivePath)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/settings/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: 'GET', ...baseOptions, ...options};
+            const localVarHeaderParameter = {} as any;
+            const localVarQueryParameter = {} as any;
+
+            // authentication apiToken required
+            // http bearer authentication required
+            await setBearerAuthToObject(localVarHeaderParameter, configuration)
+
+            if (archivePath !== undefined) {
+                localVarQueryParameter['archive_path'] = archivePath;
+            }
+
+
+    
             setSearchParams(localVarUrlObj, localVarQueryParameter);
             let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
             localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
@@ -25485,6 +26040,54 @@ export const HostingNodeJSApiAxiosParamCreator = function (configuration?: Confi
             let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
             localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
 
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
+        /**
+         * Start a Node.js build process using files already present on the website\'s file storage.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  The `source_type` must be `archive` and `source_options.archive_path` must point to an existing archive file on the server (relative to the website document root). Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.  To auto-detect build settings from an archive before starting, first call the `Get Node.js Build Settings from Archive` endpoint. To upload an archive and start a build in one step, use the `Create Node.js Build from Archive` endpoint instead.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+         * @summary Start Node.js build
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1NodeJsStartBuildRequest} hostingV1NodeJsStartBuildRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        startNodeJsBuildV1: async (username: string, domain: string, hostingV1NodeJsStartBuildRequest: HostingV1NodeJsStartBuildRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('startNodeJsBuildV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('startNodeJsBuildV1', 'domain', domain)
+            // verify required parameter 'hostingV1NodeJsStartBuildRequest' is not null or undefined
+            assertParamExists('startNodeJsBuildV1', 'hostingV1NodeJsStartBuildRequest', hostingV1NodeJsStartBuildRequest)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds`
+                .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(hostingV1NodeJsStartBuildRequest, localVarRequestOptions, configuration)
+
             return {
                 url: toPathString(localVarUrlObj),
                 options: localVarRequestOptions,
@@ -25501,7 +26104,7 @@ 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.  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.
+         * 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
@@ -25529,6 +26132,20 @@ export const HostingNodeJSApiFp = function(configuration?: Configuration) {
             const localVarOperationServerBasePath = operationServerMap['HostingNodeJSApi.getNodeJSBuildLogsV1']?.[0]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * Auto-detect Node.js build settings from a package.json inside an archive already on the server.  Use this before calling `Start Node.js Build` to preview what settings will be used, or to let the user review and override values (framework, node version, root directory, output directory, build script) before committing to a build.  The archive must already be present on the website\'s file storage. Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. To upload an archive and start a build in one step without inspecting settings first, use the `Create Node.js Build from Archive` endpoint instead.
+         * @summary Get Node.js build settings from archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {string} archivePath The path to the archive file relative to the document root of the vhost
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async getNodeJsBuildSettingsFromArchiveV1(username: string, domain: string, archivePath: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildSettingsResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.getNodeJsBuildSettingsFromArchiveV1(username, domain, archivePath, options);
+            const localVarOperationServerBasePath = operationServerMap['HostingNodeJSApi.getNodeJsBuildSettingsFromArchiveV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * Retrieve a paginated list of Node.js build processes for a specific website.  Each build represents a single run of the Node.js build pipeline. Use the `states` query parameter to filter results by build state (pending, running, completed, failed). Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
          * @summary List NodeJS builds
@@ -25586,6 +26203,20 @@ export const HostingNodeJSApiFp = function(configuration?: Configuration) {
             const localVarOperationServerBasePath = operationServerMap['HostingNodeJSApi.restartNodeJsApplicationV1']?.[0]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * Start a Node.js build process using files already present on the website\'s file storage.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  The `source_type` must be `archive` and `source_options.archive_path` must point to an existing archive file on the server (relative to the website document root). Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.  To auto-detect build settings from an archive before starting, first call the `Get Node.js Build Settings from Archive` endpoint. To upload an archive and start a build in one step, use the `Create Node.js Build from Archive` endpoint instead.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+         * @summary Start Node.js build
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1NodeJsStartBuildRequest} hostingV1NodeJsStartBuildRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async startNodeJsBuildV1(username: string, domain: string, hostingV1NodeJsStartBuildRequest: HostingV1NodeJsStartBuildRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.startNodeJsBuildV1(username, domain, hostingV1NodeJsStartBuildRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['HostingNodeJSApi.startNodeJsBuildV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
     }
 };
 
@@ -25597,7 +26228,7 @@ export const HostingNodeJSApiFactory = function (configuration?: Configuration,
     const localVarFp = HostingNodeJSApiFp(configuration)
     return {
         /**
-         * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  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.
+         * 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
@@ -25621,6 +26252,18 @@ export const HostingNodeJSApiFactory = function (configuration?: Configuration,
         getNodeJSBuildLogsV1(username: string, domain: string, uuid: string, fromLine?: number | null, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildLogsResource> {
             return localVarFp.getNodeJSBuildLogsV1(username, domain, uuid, fromLine, options).then((request) => request(axios, basePath));
         },
+        /**
+         * Auto-detect Node.js build settings from a package.json inside an archive already on the server.  Use this before calling `Start Node.js Build` to preview what settings will be used, or to let the user review and override values (framework, node version, root directory, output directory, build script) before committing to a build.  The archive must already be present on the website\'s file storage. Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. To upload an archive and start a build in one step without inspecting settings first, use the `Create Node.js Build from Archive` endpoint instead.
+         * @summary Get Node.js build settings from archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {string} archivePath The path to the archive file relative to the document root of the vhost
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        getNodeJsBuildSettingsFromArchiveV1(username: string, domain: string, archivePath: string, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildSettingsResource> {
+            return localVarFp.getNodeJsBuildSettingsFromArchiveV1(username, domain, archivePath, options).then((request) => request(axios, basePath));
+        },
         /**
          * Retrieve a paginated list of Node.js build processes for a specific website.  Each build represents a single run of the Node.js build pipeline. Use the `states` query parameter to filter results by build state (pending, running, completed, failed). Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
          * @summary List NodeJS builds
@@ -25670,6 +26313,18 @@ export const HostingNodeJSApiFactory = function (configuration?: Configuration,
         restartNodeJsApplicationV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
             return localVarFp.restartNodeJsApplicationV1(username, domain, options).then((request) => request(axios, basePath));
         },
+        /**
+         * Start a Node.js build process using files already present on the website\'s file storage.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  The `source_type` must be `archive` and `source_options.archive_path` must point to an existing archive file on the server (relative to the website document root). Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.  To auto-detect build settings from an archive before starting, first call the `Get Node.js Build Settings from Archive` endpoint. To upload an archive and start a build in one step, use the `Create Node.js Build from Archive` endpoint instead.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+         * @summary Start Node.js build
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1NodeJsStartBuildRequest} hostingV1NodeJsStartBuildRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        startNodeJsBuildV1(username: string, domain: string, hostingV1NodeJsStartBuildRequest: HostingV1NodeJsStartBuildRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildResource> {
+            return localVarFp.startNodeJsBuildV1(username, domain, hostingV1NodeJsStartBuildRequest, options).then((request) => request(axios, basePath));
+        },
     };
 };
 
@@ -25681,7 +26336,7 @@ export const HostingNodeJSApiFactory = function (configuration?: Configuration,
  */
 export class HostingNodeJSApi extends BaseAPI {
     /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  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.
+     * 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
@@ -25709,6 +26364,20 @@ export class HostingNodeJSApi extends BaseAPI {
         return HostingNodeJSApiFp(this.configuration).getNodeJSBuildLogsV1(username, domain, uuid, fromLine, options).then((request) => request(this.axios, this.basePath));
     }
 
+    /**
+     * Auto-detect Node.js build settings from a package.json inside an archive already on the server.  Use this before calling `Start Node.js Build` to preview what settings will be used, or to let the user review and override values (framework, node version, root directory, output directory, build script) before committing to a build.  The archive must already be present on the website\'s file storage. Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first. To upload an archive and start a build in one step without inspecting settings first, use the `Create Node.js Build from Archive` endpoint instead.
+     * @summary Get Node.js build settings from archive
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {string} archivePath The path to the archive file relative to the document root of the vhost
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingNodeJSApi
+     */
+    public getNodeJsBuildSettingsFromArchiveV1(username: string, domain: string, archivePath: string, options?: RawAxiosRequestConfig) {
+        return HostingNodeJSApiFp(this.configuration).getNodeJsBuildSettingsFromArchiveV1(username, domain, archivePath, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * Retrieve a paginated list of Node.js build processes for a specific website.  Each build represents a single run of the Node.js build pipeline. Use the `states` query parameter to filter results by build state (pending, running, completed, failed). Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
      * @summary List NodeJS builds
@@ -25765,6 +26434,20 @@ export class HostingNodeJSApi extends BaseAPI {
     public restartNodeJsApplicationV1(username: string, domain: string, options?: RawAxiosRequestConfig) {
         return HostingNodeJSApiFp(this.configuration).restartNodeJsApplicationV1(username, domain, options).then((request) => request(this.axios, this.basePath));
     }
+
+    /**
+     * Start a Node.js build process using files already present on the website\'s file storage.  WARNING: on success this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  The `source_type` must be `archive` and `source_options.archive_path` must point to an existing archive file on the server (relative to the website document root). Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.  To auto-detect build settings from an archive before starting, first call the `Get Node.js Build Settings from Archive` endpoint. To upload an archive and start a build in one step, use the `Create Node.js Build from Archive` endpoint instead.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+     * @summary Start Node.js build
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {HostingV1NodeJsStartBuildRequest} hostingV1NodeJsStartBuildRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingNodeJSApi
+     */
+    public startNodeJsBuildV1(username: string, domain: string, hostingV1NodeJsStartBuildRequest: HostingV1NodeJsStartBuildRequest, options?: RawAxiosRequestConfig) {
+        return HostingNodeJSApiFp(this.configuration).startNodeJsBuildV1(username, domain, hostingV1NodeJsStartBuildRequest, options).then((request) => request(this.axios, this.basePath));
+    }
 }
 
 /**
@@ -26872,7 +27555,55 @@ export const HostingWebsitesApiAxiosParamCreator = function (configuration?: Con
             };
         },
         /**
-         * Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
+         * Deploy a static application from an archive file.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website\'s directory.  This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use `Create NodeJS build from archive` instead, or `Start Node.js build` if the archive is already uploaded. For WordPress sites, use `Import WordPress website`.
+         * @summary Deploy static site archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1WebsitesDeployArchiveRequest} hostingV1WebsitesDeployArchiveRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployStaticSiteArchiveV1: async (username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('deployStaticSiteArchiveV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('deployStaticSiteArchiveV1', 'domain', domain)
+            // verify required parameter 'hostingV1WebsitesDeployArchiveRequest' is not null or undefined
+            assertParamExists('deployStaticSiteArchiveV1', 'hostingV1WebsitesDeployArchiveRequest', hostingV1WebsitesDeployArchiveRequest)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/deploy`
+                .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(hostingV1WebsitesDeployArchiveRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
+        /**
+         * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
          * @summary List websites
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -26970,7 +27701,21 @@ export const HostingWebsitesApiFp = function(configuration?: Configuration) {
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
+         * Deploy a static application from an archive file.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website\'s directory.  This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use `Create NodeJS build from archive` instead, or `Start Node.js build` if the archive is already uploaded. For WordPress sites, use `Import WordPress website`.
+         * @summary Deploy static site archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1WebsitesDeployArchiveRequest} hostingV1WebsitesDeployArchiveRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.deployStaticSiteArchiveV1(username, domain, hostingV1WebsitesDeployArchiveRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['HostingWebsitesApi.deployStaticSiteArchiveV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
+        /**
+         * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
          * @summary List websites
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -27017,7 +27762,19 @@ export const HostingWebsitesApiFactory = function (configuration?: Configuration
             return localVarFp.deleteWebsiteV1(domain, options).then((request) => request(axios, basePath));
         },
         /**
-         * Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
+         * Deploy a static application from an archive file.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website\'s directory.  This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use `Create NodeJS build from archive` instead, or `Start Node.js build` if the archive is already uploaded. For WordPress sites, use `Import WordPress website`.
+         * @summary Deploy static site archive
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {HostingV1WebsitesDeployArchiveRequest} hostingV1WebsitesDeployArchiveRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
+            return localVarFp.deployStaticSiteArchiveV1(username, domain, hostingV1WebsitesDeployArchiveRequest, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
          * @summary List websites
          * @param {number} [page] Page number
          * @param {number} [perPage] Number of items per page
@@ -27066,7 +27823,21 @@ export class HostingWebsitesApi extends BaseAPI {
     }
 
     /**
-     * Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
+     * Deploy a static application from an archive file.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website\'s directory.  This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use `Create NodeJS build from archive` instead, or `Start Node.js build` if the archive is already uploaded. For WordPress sites, use `Import WordPress website`.
+     * @summary Deploy static site archive
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {HostingV1WebsitesDeployArchiveRequest} hostingV1WebsitesDeployArchiveRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingWebsitesApi
+     */
+    public deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig) {
+        return HostingWebsitesApiFp(this.configuration).deployStaticSiteArchiveV1(username, domain, hostingV1WebsitesDeployArchiveRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+
+    /**
+     * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
      * @summary List websites
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -40675,6 +41446,54 @@ export const WordPressInstallationsApiAxiosParamCreator = function (configuratio
                 options: localVarRequestOptions,
             };
         },
+        /**
+         * Import WordPress website to the specified domain.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to import a WordPress website from archive and database files that have been uploaded to the website\'s directory.
+         * @summary Import WordPress website
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1InstallationsImportWordPressRequest} wordPressV1InstallationsImportWordPressRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        importWordPressWebsiteV1: async (username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('importWordPressWebsiteV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('importWordPressWebsiteV1', 'domain', domain)
+            // verify required parameter 'wordPressV1InstallationsImportWordPressRequest' is not null or undefined
+            assertParamExists('importWordPressWebsiteV1', 'wordPressV1InstallationsImportWordPressRequest', wordPressV1InstallationsImportWordPressRequest)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/import`
+                .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(wordPressV1InstallationsImportWordPressRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * 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.
          * @summary Install WordPress
@@ -40962,6 +41781,20 @@ export const WordPressInstallationsApiFp = function(configuration?: Configuratio
             const localVarOperationServerBasePath = operationServerMap['WordPressInstallationsApi.getInstallationJWTTokenV1']?.[0]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * Import WordPress website to the specified domain.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to import a WordPress website from archive and database files that have been uploaded to the website\'s directory.
+         * @summary Import WordPress website
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1InstallationsImportWordPressRequest} wordPressV1InstallationsImportWordPressRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.importWordPressWebsiteV1(username, domain, wordPressV1InstallationsImportWordPressRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['WordPressInstallationsApi.importWordPressWebsiteV1']?.[0]?.url;
+            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.
          * @summary Install WordPress
@@ -41083,6 +41916,18 @@ export const WordPressInstallationsApiFactory = function (configuration?: Config
         getInstallationJWTTokenV1(username: string, software: string, options?: RawAxiosRequestConfig): AxiosPromise<WordPressV1InstallationsJwtTokenResource> {
             return localVarFp.getInstallationJWTTokenV1(username, software, options).then((request) => request(axios, basePath));
         },
+        /**
+         * Import WordPress website to the specified domain.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to import a WordPress website from archive and database files that have been uploaded to the website\'s directory.
+         * @summary Import WordPress website
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1InstallationsImportWordPressRequest} wordPressV1InstallationsImportWordPressRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
+            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.
          * @summary Install WordPress
@@ -41202,6 +42047,20 @@ export class WordPressInstallationsApi extends BaseAPI {
         return WordPressInstallationsApiFp(this.configuration).getInstallationJWTTokenV1(username, software, options).then((request) => request(this.axios, this.basePath));
     }
 
+    /**
+     * Import WordPress website to the specified domain.  WARNING: this overwrites the website\'s existing contents and cannot be undone — verify this is intended before calling this endpoint.  This endpoint allows you to import a WordPress website from archive and database files that have been uploaded to the website\'s directory.
+     * @summary Import WordPress website
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {WordPressV1InstallationsImportWordPressRequest} wordPressV1InstallationsImportWordPressRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof WordPressInstallationsApi
+     */
+    public importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig) {
+        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.
      * @summary Install WordPress
@@ -42149,6 +43008,54 @@ export const WordPressPluginsApiAxiosParamCreator = function (configuration?: Co
                 options: localVarRequestOptions,
             };
         },
+        /**
+         * Deploy a WordPress plugin from an already uploaded directory.  This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website\'s directory. The plugin will be activated and made available in the WordPress admin panel.
+         * @summary Deploy WordPress plugin
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1PluginsDeployPluginRequest} wordPressV1PluginsDeployPluginRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployWordPressPluginV1: async (username: string, domain: string, wordPressV1PluginsDeployPluginRequest: WordPressV1PluginsDeployPluginRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('deployWordPressPluginV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('deployWordPressPluginV1', 'domain', domain)
+            // verify required parameter 'wordPressV1PluginsDeployPluginRequest' is not null or undefined
+            assertParamExists('deployWordPressPluginV1', 'wordPressV1PluginsDeployPluginRequest', wordPressV1PluginsDeployPluginRequest)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/plugins/deploy`
+                .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(wordPressV1PluginsDeployPluginRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * Install one or more plugins on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin slugs available for installation.  This operation is asynchronous: a successful response only means the install job has been queued, not that the plugins are ready.
          * @summary Install WordPress plugins
@@ -42560,6 +43467,20 @@ export const WordPressPluginsApiFp = function(configuration?: Configuration) {
             const localVarOperationServerBasePath = operationServerMap['WordPressPluginsApi.deactivateWordPressPluginV1']?.[0]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * Deploy a WordPress plugin from an already uploaded directory.  This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website\'s directory. The plugin will be activated and made available in the WordPress admin panel.
+         * @summary Deploy WordPress plugin
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1PluginsDeployPluginRequest} wordPressV1PluginsDeployPluginRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async deployWordPressPluginV1(username: string, domain: string, wordPressV1PluginsDeployPluginRequest: WordPressV1PluginsDeployPluginRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.deployWordPressPluginV1(username, domain, wordPressV1PluginsDeployPluginRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['WordPressPluginsApi.deployWordPressPluginV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * Install one or more plugins on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin slugs available for installation.  This operation is asynchronous: a successful response only means the install job has been queued, not that the plugins are ready.
          * @summary Install WordPress plugins
@@ -42711,6 +43632,18 @@ export const WordPressPluginsApiFactory = function (configuration?: Configuratio
         deactivateWordPressPluginV1(username: string, software: string, wordPressV1PluginsDeactivatePluginRequest: WordPressV1PluginsDeactivatePluginRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
             return localVarFp.deactivateWordPressPluginV1(username, software, wordPressV1PluginsDeactivatePluginRequest, options).then((request) => request(axios, basePath));
         },
+        /**
+         * Deploy a WordPress plugin from an already uploaded directory.  This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website\'s directory. The plugin will be activated and made available in the WordPress admin panel.
+         * @summary Deploy WordPress plugin
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1PluginsDeployPluginRequest} wordPressV1PluginsDeployPluginRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployWordPressPluginV1(username: string, domain: string, wordPressV1PluginsDeployPluginRequest: WordPressV1PluginsDeployPluginRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
+            return localVarFp.deployWordPressPluginV1(username, domain, wordPressV1PluginsDeployPluginRequest, options).then((request) => request(axios, basePath));
+        },
         /**
          * Install one or more plugins on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin slugs available for installation.  This operation is asynchronous: a successful response only means the install job has been queued, not that the plugins are ready.
          * @summary Install WordPress plugins
@@ -42852,6 +43785,20 @@ export class WordPressPluginsApi extends BaseAPI {
         return WordPressPluginsApiFp(this.configuration).deactivateWordPressPluginV1(username, software, wordPressV1PluginsDeactivatePluginRequest, options).then((request) => request(this.axios, this.basePath));
     }
 
+    /**
+     * Deploy a WordPress plugin from an already uploaded directory.  This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website\'s directory. The plugin will be activated and made available in the WordPress admin panel.
+     * @summary Deploy WordPress plugin
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {WordPressV1PluginsDeployPluginRequest} wordPressV1PluginsDeployPluginRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof WordPressPluginsApi
+     */
+    public deployWordPressPluginV1(username: string, domain: string, wordPressV1PluginsDeployPluginRequest: WordPressV1PluginsDeployPluginRequest, options?: RawAxiosRequestConfig) {
+        return WordPressPluginsApiFp(this.configuration).deployWordPressPluginV1(username, domain, wordPressV1PluginsDeployPluginRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * Install one or more plugins on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin slugs available for installation.  This operation is asynchronous: a successful response only means the install job has been queued, not that the plugins are ready.
      * @summary Install WordPress plugins
@@ -43023,6 +43970,54 @@ export const WordPressThemesApiAxiosParamCreator = function (configuration?: Con
                 options: localVarRequestOptions,
             };
         },
+        /**
+         * Deploy a WordPress theme from an already uploaded directory.  This endpoint allows you to deploy a WordPress theme that has been uploaded to the website\'s directory. The theme can be optionally activated after deployment.
+         * @summary Deploy WordPress theme
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1ThemesDeployThemeRequest} wordPressV1ThemesDeployThemeRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployWordPressThemeV1: async (username: string, domain: string, wordPressV1ThemesDeployThemeRequest: WordPressV1ThemesDeployThemeRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'username' is not null or undefined
+            assertParamExists('deployWordPressThemeV1', 'username', username)
+            // verify required parameter 'domain' is not null or undefined
+            assertParamExists('deployWordPressThemeV1', 'domain', domain)
+            // verify required parameter 'wordPressV1ThemesDeployThemeRequest' is not null or undefined
+            assertParamExists('deployWordPressThemeV1', 'wordPressV1ThemesDeployThemeRequest', wordPressV1ThemesDeployThemeRequest)
+            const localVarPath = `/api/hosting/v1/accounts/{username}/websites/{domain}/wordpress/themes/deploy`
+                .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(wordPressV1ThemesDeployThemeRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * Install a theme on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).  When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`, `layout`, and `font` fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored.  This operation is asynchronous: a successful response only means the install job has been queued, not that the theme is ready.
          * @summary Install WordPress theme
@@ -43277,6 +44272,20 @@ export const WordPressThemesApiFp = function(configuration?: Configuration) {
             const localVarOperationServerBasePath = operationServerMap['WordPressThemesApi.activateWordPressThemeV1']?.[0]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * Deploy a WordPress theme from an already uploaded directory.  This endpoint allows you to deploy a WordPress theme that has been uploaded to the website\'s directory. The theme can be optionally activated after deployment.
+         * @summary Deploy WordPress theme
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1ThemesDeployThemeRequest} wordPressV1ThemesDeployThemeRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async deployWordPressThemeV1(username: string, domain: string, wordPressV1ThemesDeployThemeRequest: WordPressV1ThemesDeployThemeRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.deployWordPressThemeV1(username, domain, wordPressV1ThemesDeployThemeRequest, options);
+            const localVarOperationServerBasePath = operationServerMap['WordPressThemesApi.deployWordPressThemeV1']?.[0]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * Install a theme on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).  When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`, `layout`, and `font` fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored.  This operation is asynchronous: a successful response only means the install job has been queued, not that the theme is ready.
          * @summary Install WordPress theme
@@ -43367,6 +44376,18 @@ export const WordPressThemesApiFactory = function (configuration?: Configuration
         activateWordPressThemeV1(username: string, software: string, wordPressV1ThemesActivateThemeRequest: WordPressV1ThemesActivateThemeRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
             return localVarFp.activateWordPressThemeV1(username, software, wordPressV1ThemesActivateThemeRequest, options).then((request) => request(axios, basePath));
         },
+        /**
+         * Deploy a WordPress theme from an already uploaded directory.  This endpoint allows you to deploy a WordPress theme that has been uploaded to the website\'s directory. The theme can be optionally activated after deployment.
+         * @summary Deploy WordPress theme
+         * @param {string} username 
+         * @param {string} domain Domain name
+         * @param {WordPressV1ThemesDeployThemeRequest} wordPressV1ThemesDeployThemeRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deployWordPressThemeV1(username: string, domain: string, wordPressV1ThemesDeployThemeRequest: WordPressV1ThemesDeployThemeRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource> {
+            return localVarFp.deployWordPressThemeV1(username, domain, wordPressV1ThemesDeployThemeRequest, options).then((request) => request(axios, basePath));
+        },
         /**
          * Install a theme on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).  When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`, `layout`, and `font` fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored.  This operation is asynchronous: a successful response only means the install job has been queued, not that the theme is ready.
          * @summary Install WordPress theme
@@ -43449,6 +44470,20 @@ export class WordPressThemesApi extends BaseAPI {
         return WordPressThemesApiFp(this.configuration).activateWordPressThemeV1(username, software, wordPressV1ThemesActivateThemeRequest, options).then((request) => request(this.axios, this.basePath));
     }
 
+    /**
+     * Deploy a WordPress theme from an already uploaded directory.  This endpoint allows you to deploy a WordPress theme that has been uploaded to the website\'s directory. The theme can be optionally activated after deployment.
+     * @summary Deploy WordPress theme
+     * @param {string} username 
+     * @param {string} domain Domain name
+     * @param {WordPressV1ThemesDeployThemeRequest} wordPressV1ThemesDeployThemeRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof WordPressThemesApi
+     */
+    public deployWordPressThemeV1(username: string, domain: string, wordPressV1ThemesDeployThemeRequest: WordPressV1ThemesDeployThemeRequest, options?: RawAxiosRequestConfig) {
+        return WordPressThemesApiFp(this.configuration).deployWordPressThemeV1(username, domain, wordPressV1ThemesDeployThemeRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * Install a theme on an existing WordPress installation.  Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).  When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`, `layout`, and `font` fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored.  This operation is asynchronous: a successful response only means the install job has been queued, not that the theme is ready.
      * @summary Install WordPress theme