hostinger-api-sdk 1.37.0 → 1.39.0

package/dist/esm/api.d.ts

@@ -1,7 +1,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
@@ -5198,6 +5198,50 @@ export declare const HostingV1FilesFilesResourceItemsInnerTypeEnum: {
     readonly Other: "other";
 };
 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
@@ -5354,6 +5398,89 @@ export declare const HostingV1NodeJsBuildResourceStateEnum: {
     readonly Failed: "failed";
 };
 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 declare const HostingV1NodeJsBuildSettingsResourceAppTypeEnum: {
+    readonly CreateReactApp: "create-react-app";
+    readonly Gatsby: "gatsby";
+    readonly Vite: "vite";
+    readonly Angular: "angular";
+    readonly React: "react";
+    readonly Vue: "vue";
+    readonly Parcel: "parcel";
+    readonly Next: "next";
+    readonly Nuxt: "nuxt";
+    readonly Nest: "nest";
+    readonly Express: "express";
+    readonly Fastify: "fastify";
+    readonly Astro: "astro";
+    readonly Svelte: "svelte";
+    readonly SvelteKit: "svelte-kit";
+    readonly Hono: "hono";
+    readonly ReactRouter: "react-router";
+    readonly Nitro: "nitro";
+    readonly Other: "other";
+};
+export type HostingV1NodeJsBuildSettingsResourceAppTypeEnum = typeof HostingV1NodeJsBuildSettingsResourceAppTypeEnum[keyof typeof HostingV1NodeJsBuildSettingsResourceAppTypeEnum];
+export declare const HostingV1NodeJsBuildSettingsResourcePackageManagerEnum: {
+    readonly Npm: "npm";
+    readonly Yarn: "yarn";
+    readonly Pnpm: "pnpm";
+};
+export type HostingV1NodeJsBuildSettingsResourcePackageManagerEnum = typeof HostingV1NodeJsBuildSettingsResourcePackageManagerEnum[keyof typeof HostingV1NodeJsBuildSettingsResourcePackageManagerEnum];
 /**
  *
  * @export
@@ -5444,6 +5571,19 @@ export declare const HostingV1NodeJsCreateFromArchiveRequestPackageManagerEnum:
     readonly Pnpm: "pnpm";
 };
 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
@@ -5501,6 +5641,119 @@ 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 declare const HostingV1NodeJsStartBuildRequestNodeVersionEnum: {
+    readonly NUMBER_18: 18;
+    readonly NUMBER_20: 20;
+    readonly NUMBER_22: 22;
+    readonly NUMBER_24: 24;
+};
+export type HostingV1NodeJsStartBuildRequestNodeVersionEnum = typeof HostingV1NodeJsStartBuildRequestNodeVersionEnum[keyof typeof HostingV1NodeJsStartBuildRequestNodeVersionEnum];
+export declare const HostingV1NodeJsStartBuildRequestAppTypeEnum: {
+    readonly CreateReactApp: "create-react-app";
+    readonly Gatsby: "gatsby";
+    readonly Vite: "vite";
+    readonly Angular: "angular";
+    readonly React: "react";
+    readonly Vue: "vue";
+    readonly Parcel: "parcel";
+    readonly Next: "next";
+    readonly Nuxt: "nuxt";
+    readonly Nest: "nest";
+    readonly Express: "express";
+    readonly Fastify: "fastify";
+    readonly Astro: "astro";
+    readonly Svelte: "svelte";
+    readonly SvelteKit: "svelte-kit";
+    readonly Hono: "hono";
+    readonly ReactRouter: "react-router";
+    readonly Nitro: "nitro";
+    readonly Other: "other";
+};
+export type HostingV1NodeJsStartBuildRequestAppTypeEnum = typeof HostingV1NodeJsStartBuildRequestAppTypeEnum[keyof typeof HostingV1NodeJsStartBuildRequestAppTypeEnum];
+export declare const HostingV1NodeJsStartBuildRequestPackageManagerEnum: {
+    readonly Npm: "npm";
+    readonly Yarn: "yarn";
+    readonly Pnpm: "pnpm";
+};
+export type HostingV1NodeJsStartBuildRequestPackageManagerEnum = typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum[keyof typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum];
+export declare const HostingV1NodeJsStartBuildRequestSourceTypeEnum: {
+    readonly Archive: "archive";
+};
+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
@@ -5910,6 +6163,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
@@ -5917,17 +6183,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}
@@ -5935,11 +6201,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}
@@ -5959,17 +6225,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 declare const HostingV1WebsitesWebsiteResourceVhostTypeEnum: {
     readonly Main: "main";
@@ -5978,6 +6256,14 @@ export declare const HostingV1WebsitesWebsiteResourceVhostTypeEnum: {
     readonly Subdomain: "subdomain";
 };
 export type HostingV1WebsitesWebsiteResourceVhostTypeEnum = typeof HostingV1WebsitesWebsiteResourceVhostTypeEnum[keyof typeof HostingV1WebsitesWebsiteResourceVhostTypeEnum];
+export declare const HostingV1WebsitesWebsiteResourceWebsiteTypeEnum: {
+    readonly Wordpress: "wordpress";
+    readonly Builder: "builder";
+    readonly Horizons: "horizons";
+    readonly Nodejs: "nodejs";
+    readonly Other: "other";
+};
+export type HostingV1WebsitesWebsiteResourceWebsiteTypeEnum = typeof HostingV1WebsitesWebsiteResourceWebsiteTypeEnum[keyof typeof HostingV1WebsitesWebsiteResourceWebsiteTypeEnum];
 /**
  *
  * @export
@@ -11952,6 +12238,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
@@ -12508,6 +12813,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
@@ -12794,6 +13118,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
@@ -13632,6 +13981,14 @@ export declare class AgencyHostingDomainsApi extends BaseAPI {
  * @export
  */
 export declare const AgencyHostingFilesApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * 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
@@ -13647,6 +14004,14 @@ export declare const AgencyHostingFilesApiAxiosParamCreator: (configuration?: Co
  * @export
  */
 export declare const AgencyHostingFilesApiFp: (configuration?: Configuration) => {
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<AgencyHostingV1FilesUploadUrlResource>>;
     /**
      * 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
@@ -13662,6 +14027,14 @@ export declare const AgencyHostingFilesApiFp: (configuration?: Configuration) =>
  * @export
  */
 export declare const AgencyHostingFilesApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * 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>;
     /**
      * 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
@@ -13679,6 +14052,15 @@ export declare const AgencyHostingFilesApiFactory: (configuration?: Configuratio
  * @extends {BaseAPI}
  */
 export declare 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
+     */
+    generateUploadURLV1(websiteUid: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AgencyHostingV1FilesUploadUrlResource, any, {}, any>>;
     /**
      * 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
@@ -18632,6 +19014,14 @@ export declare class HostingDomainsApi extends BaseAPI {
  * @export
  */
 export declare const HostingFilesApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * 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
@@ -18664,6 +19054,14 @@ export declare const HostingFilesApiAxiosParamCreator: (configuration?: Configur
  * @export
  */
 export declare const HostingFilesApiFp: (configuration?: Configuration) => {
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1FilesUploadUrlResource>>;
     /**
      * 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
@@ -18696,6 +19094,14 @@ export declare const HostingFilesApiFp: (configuration?: Configuration) => {
  * @export
  */
 export declare const HostingFilesApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * 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>;
     /**
      * 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
@@ -18730,6 +19136,15 @@ export declare const HostingFilesApiFactory: (configuration?: Configuration, bas
  * @extends {BaseAPI}
  */
 export declare 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
+     */
+    generateUploadURLV1(hostingV1FilesGenerateUploadUrlRequest: HostingV1FilesGenerateUploadUrlRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1FilesUploadUrlResource, any, {}, any>>;
     /**
      * 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
@@ -18775,7 +19190,7 @@ export type ListWebsiteFilesAndDirectoriesV1FileTypesEnum = typeof ListWebsiteFi
  */
 export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * 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
@@ -18795,6 +19210,16 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
      * @throws {RequiredError}
      */
     getNodeJSBuildLogsV1: (username: string, domain: string, uuid: string, fromLine?: number | null, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * 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
@@ -18836,6 +19261,16 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
      * @throws {RequiredError}
      */
     restartNodeJsApplicationV1: (username: string, domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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) => Promise<RequestArgs>;
 };
 /**
  * HostingNodeJSApi - functional programming interface
@@ -18843,7 +19278,7 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
  */
 export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
     /**
-     * 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
@@ -18863,6 +19298,16 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getNodeJSBuildLogsV1(username: string, domain: string, uuid: string, fromLine?: number | null, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildLogsResource>>;
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildSettingsResource>>;
     /**
      * 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
@@ -18904,6 +19349,16 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     restartNodeJsApplicationV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1NodeJsBuildResource>>;
 };
 /**
  * HostingNodeJSApi - factory interface
@@ -18911,7 +19366,7 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingNodeJSApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Upload a project archive, auto-detect build settings, and immediately start a Node.js build.  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
@@ -18931,6 +19386,16 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
      * @throws {RequiredError}
      */
     getNodeJSBuildLogsV1(username: string, domain: string, uuid: string, fromLine?: number | null, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1NodeJsBuildLogsResource>;
+    /**
+     * 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>;
     /**
      * 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
@@ -18972,6 +19437,16 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
      * @throws {RequiredError}
      */
     restartNodeJsApplicationV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
+    /**
+     * 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>;
 };
 /**
  * HostingNodeJSApi - object-oriented interface
@@ -18981,7 +19456,7 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
  */
 export declare 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
@@ -19003,6 +19478,17 @@ export declare class HostingNodeJSApi extends BaseAPI {
      * @memberof HostingNodeJSApi
      */
     getNodeJSBuildLogsV1(username: string, domain: string, uuid: string, fromLine?: number | null, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1NodeJsBuildLogsResource, any, {}, any>>;
+    /**
+     * 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
+     */
+    getNodeJsBuildSettingsFromArchiveV1(username: string, domain: string, archivePath: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1NodeJsBuildSettingsResource, any, {}, any>>;
     /**
      * 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
@@ -19048,6 +19534,17 @@ export declare class HostingNodeJSApi extends BaseAPI {
      * @memberof HostingNodeJSApi
      */
     restartNodeJsApplicationV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * 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
+     */
+    startNodeJsBuildV1(username: string, domain: string, hostingV1NodeJsStartBuildRequest: HostingV1NodeJsStartBuildRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1NodeJsBuildResource, any, {}, any>>;
 }
 /**
  * @export
@@ -19586,7 +20083,17 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
      */
     deleteWebsiteV1: (domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * 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) => Promise<RequestArgs>;
+    /**
+     * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use 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
@@ -19621,7 +20128,17 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
      */
     deleteWebsiteV1(domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
-     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * 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
@@ -19656,7 +20173,17 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
      */
     deleteWebsiteV1(domain: string, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
     /**
-     * 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>;
+    /**
+     * 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
@@ -19695,7 +20222,18 @@ export declare class HostingWebsitesApi extends BaseAPI {
      */
     deleteWebsiteV1(domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
-     * 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
+     */
+    deployStaticSiteArchiveV1(username: string, domain: string, hostingV1WebsitesDeployArchiveRequest: HostingV1WebsitesDeployArchiveRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * Retrieve a paginated list of websites (CloudLinux, Builder, and Horizons) accessible to the authenticated client.  This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.  Each website includes a `website_type` field describing the type of website detected on the underlying platform (`wordpress`, `builder`, `horizons`, `nodejs`, or `other`). Some fields, such as `vhost_type`, `username`, and `root_directory`, only apply to CloudLinux websites and are null for other platforms.  Use 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
@@ -26290,6 +26828,16 @@ export declare const WordPressInstallationsApiAxiosParamCreator: (configuration?
      * @throws {RequiredError}
      */
     getInstallationJWTTokenV1: (username: string, software: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * Install WordPress on an existing website.  The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears.  Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and `overwrite` is false (the default), the async job will fail.  This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready.
      * @summary Install WordPress
@@ -26379,6 +26927,16 @@ export declare const WordPressInstallationsApiFp: (configuration?: Configuration
      * @throws {RequiredError}
      */
     getInstallationJWTTokenV1(username: string, software: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<WordPressV1InstallationsJwtTokenResource>>;
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
      * Install WordPress on an existing website.  The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears.  Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and `overwrite` is false (the default), the async job will fail.  This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready.
      * @summary Install WordPress
@@ -26468,6 +27026,16 @@ export declare const WordPressInstallationsApiFactory: (configuration?: Configur
      * @throws {RequiredError}
      */
     getInstallationJWTTokenV1(username: string, software: string, options?: RawAxiosRequestConfig): AxiosPromise<WordPressV1InstallationsJwtTokenResource>;
+    /**
+     * 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>;
     /**
      * 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
@@ -26563,6 +27131,17 @@ export declare class WordPressInstallationsApi extends BaseAPI {
      * @memberof WordPressInstallationsApi
      */
     getInstallationJWTTokenV1(username: string, software: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<WordPressV1InstallationsJwtTokenResource, any, {}, any>>;
+    /**
+     * 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
+     */
+    importWordPressWebsiteV1(username: string, domain: string, wordPressV1InstallationsImportWordPressRequest: WordPressV1InstallationsImportWordPressRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
      * Install WordPress on an existing website.  The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears.  Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and `overwrite` is false (the default), the async job will fail.  This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready.
      * @summary Install WordPress
@@ -27029,6 +27608,16 @@ export declare const WordPressPluginsApiAxiosParamCreator: (configuration?: Conf
      * @throws {RequiredError}
      */
     deactivateWordPressPluginV1: (username: string, software: string, wordPressV1PluginsDeactivatePluginRequest: WordPressV1PluginsDeactivatePluginRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * 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
@@ -27138,6 +27727,16 @@ export declare const WordPressPluginsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     deactivateWordPressPluginV1(username: string, software: string, wordPressV1PluginsDeactivatePluginRequest: WordPressV1PluginsDeactivatePluginRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
      * 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
@@ -27247,6 +27846,16 @@ export declare const WordPressPluginsApiFactory: (configuration?: Configuration,
      * @throws {RequiredError}
      */
     deactivateWordPressPluginV1(username: string, software: string, wordPressV1PluginsDeactivatePluginRequest: WordPressV1PluginsDeactivatePluginRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
+    /**
+     * 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>;
     /**
      * 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
@@ -27361,6 +27970,17 @@ export declare class WordPressPluginsApi extends BaseAPI {
      * @memberof WordPressPluginsApi
      */
     deactivateWordPressPluginV1(username: string, software: string, wordPressV1PluginsDeactivatePluginRequest: WordPressV1PluginsDeactivatePluginRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * 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
+     */
+    deployWordPressPluginV1(username: string, domain: string, wordPressV1PluginsDeployPluginRequest: WordPressV1PluginsDeployPluginRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
      * 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
@@ -27467,6 +28087,16 @@ export declare const WordPressThemesApiAxiosParamCreator: (configuration?: Confi
      * @throws {RequiredError}
      */
     activateWordPressThemeV1: (username: string, software: string, wordPressV1ThemesActivateThemeRequest: WordPressV1ThemesActivateThemeRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * 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) => Promise<RequestArgs>;
     /**
      * 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
@@ -27531,6 +28161,16 @@ export declare const WordPressThemesApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     activateWordPressThemeV1(username: string, software: string, wordPressV1ThemesActivateThemeRequest: WordPressV1ThemesActivateThemeRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * 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): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
     /**
      * 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
@@ -27595,6 +28235,16 @@ export declare const WordPressThemesApiFactory: (configuration?: Configuration,
      * @throws {RequiredError}
      */
     activateWordPressThemeV1(username: string, software: string, wordPressV1ThemesActivateThemeRequest: WordPressV1ThemesActivateThemeRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
+    /**
+     * 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>;
     /**
      * 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
@@ -27662,6 +28312,17 @@ export declare class WordPressThemesApi extends BaseAPI {
      * @memberof WordPressThemesApi
      */
     activateWordPressThemeV1(username: string, software: string, wordPressV1ThemesActivateThemeRequest: WordPressV1ThemesActivateThemeRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * 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
+     */
+    deployWordPressThemeV1(username: string, domain: string, wordPressV1ThemesDeployThemeRequest: WordPressV1ThemesDeployThemeRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
     /**
      * 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