@hostinger/sdk 1.52.1 → 1.52.2

package/base.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.52.1
+ * API Version: 1.52.2
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/common.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.52.1
+ * API Version: 1.52.2
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api

package/configuration.ts

@@ -3,7 +3,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.52.1
+ * API Version: 1.52.2
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api
@@ -48,7 +48,7 @@ export class Configuration {
         this.baseOptions = {
             ...param.baseOptions,
             headers: {
-                'User-Agent': "hostinger-typescript-sdk/1.52.1",
+                'User-Agent': "hostinger-typescript-sdk/1.52.2",
                 ...param.baseOptions?.headers,
             },
         };

package/dist/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.52.1
+ * API Version: 1.52.2
  *
  * NOTE: This file is auto-generated, DO NOT EDIT THIS FILE MANUALLY!
  * If you want to contribute or request a new feature, please create an issue or pull request on https://github.com/hostinger/api
@@ -7209,6 +7209,93 @@ export interface HostingV1FilesUploadUrlResource {
      */
     'rest_auth_key': string;
 }
+/**
+ * Every field is null when the website has no Git auto-deployment configured.
+ * @export
+ * @interface HostingV1GitGitAutoDeploymentSettingsResource
+ */
+export interface HostingV1GitGitAutoDeploymentSettingsResource {
+    /**
+     * Git installation the repository is accessed through
+     * @type {string}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'installation_uuid': string | null;
+    /**
+     * Whether pushes to the branch deploy automatically
+     * @type {boolean}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'is_enabled': boolean | null;
+    /**
+     * Repository owner login
+     * @type {string}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'owner': string | null;
+    /**
+     * Repository name
+     * @type {string}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'repository': string | null;
+    /**
+     * Branch that is deployed
+     * @type {string}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'branch': string | null;
+    /**
+     * Subdirectory under the website document root the repository deploys into. Empty means the document root.
+     * @type {string}
+     * @memberof HostingV1GitGitAutoDeploymentSettingsResource
+     */
+    'directory': string | null;
+}
+/**
+ *
+ * @export
+ * @interface HostingV1GitGitCommitAuthorResource
+ */
+export interface HostingV1GitGitCommitAuthorResource {
+    /**
+     * Author name as recorded in the commit
+     * @type {string}
+     * @memberof HostingV1GitGitCommitAuthorResource
+     */
+    'name': string;
+    /**
+     * Avatar URL of the author on the Git provider
+     * @type {string}
+     * @memberof HostingV1GitGitCommitAuthorResource
+     */
+    'avatar_url': string | null;
+}
+/**
+ *
+ * @export
+ * @interface HostingV1GitGitCommitResource
+ */
+export interface HostingV1GitGitCommitResource {
+    /**
+     * Full commit SHA
+     * @type {string}
+     * @memberof HostingV1GitGitCommitResource
+     */
+    'hash': string;
+    /**
+     * Commit message
+     * @type {string}
+     * @memberof HostingV1GitGitCommitResource
+     */
+    'message': string;
+    /**
+     *
+     * @type {HostingV1GitGitCommitAuthorResource}
+     * @memberof HostingV1GitGitCommitResource
+     */
+    'author': HostingV1GitGitCommitAuthorResource;
+}
 /**
  *
  * @export
@@ -7342,6 +7429,49 @@ export interface HostingV1GitGitRepositoryResource {
      */
     'default_branch': string;
 }
+/**
+ *
+ * @export
+ * @interface HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+ */
+export interface HostingV1GitUpdateGitAutoDeploymentSettingsRequest {
+    /**
+     * Active Git installation from `List Git installations`
+     * @type {string}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'installation_uuid': string;
+    /**
+     * Repository owner login, as returned by `List Git installation repositories`. GitLab group paths use slashes.
+     * @type {string}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'owner': string;
+    /**
+     * Repository name without the .git suffix
+     * @type {string}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'repository': string;
+    /**
+     * Branch to deploy
+     * @type {string}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'branch': string;
+    /**
+     * Subdirectory under the website document root to deploy into. Empty, null or omitted means the document root.
+     * @type {string}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'directory': string | null;
+    /**
+     * Whether pushes to the branch deploy automatically
+     * @type {boolean}
+     * @memberof HostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     */
+    'is_enabled': boolean;
+}
 /**
  *
  * @export
@@ -7471,6 +7601,7 @@ export declare const HostingV1NodeJsBuildOptionsResourcePackageManagerEnum: {
 export type HostingV1NodeJsBuildOptionsResourcePackageManagerEnum = typeof HostingV1NodeJsBuildOptionsResourcePackageManagerEnum[keyof typeof HostingV1NodeJsBuildOptionsResourcePackageManagerEnum];
 export declare const HostingV1NodeJsBuildOptionsResourceSourceTypeEnum: {
     readonly Archive: "archive";
+    readonly Git: "git";
 };
 export type HostingV1NodeJsBuildOptionsResourceSourceTypeEnum = typeof HostingV1NodeJsBuildOptionsResourceSourceTypeEnum[keyof typeof HostingV1NodeJsBuildOptionsResourceSourceTypeEnum];
 /**
@@ -7855,7 +7986,7 @@ export interface HostingV1NodeJsSetBuildEnvVarsRequestEnvVarsInner {
     'value': string;
 }
 /**
- *
+ * Which keys carry values depends on the parent source_type; the others are null.
  * @export
  * @interface HostingV1NodeJsSourceOptionsResource
  */
@@ -7866,6 +7997,36 @@ export interface HostingV1NodeJsSourceOptionsResource {
      * @memberof HostingV1NodeJsSourceOptionsResource
      */
     'archive_path': string | null;
+    /**
+     * Repository owner login (present if source_type is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsSourceOptionsResource
+     */
+    'owner': string | null;
+    /**
+     * Repository name without the .git suffix (present if source_type is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsSourceOptionsResource
+     */
+    'repository': string | null;
+    /**
+     * Branch that was built (present if source_type is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsSourceOptionsResource
+     */
+    'branch': string | null;
+    /**
+     * Git installation used to access the repository (present if source_type is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsSourceOptionsResource
+     */
+    'installation_uuid': string | null;
+    /**
+     *
+     * @type {HostingV1GitGitCommitResource}
+     * @memberof HostingV1NodeJsSourceOptionsResource
+     */
+    'commit': HostingV1GitGitCommitResource | null;
 }
 /**
  *
@@ -7916,7 +8077,7 @@ export interface HostingV1NodeJsStartBuildRequest {
      */
     'package_manager': HostingV1NodeJsStartBuildRequestPackageManagerEnum | null;
     /**
-     * The source type of the files
+     * Where the files come from: `archive` (an uploaded archive on the website) or `git` (a branch of a repository reachable through a Git installation).
      * @type {string}
      * @memberof HostingV1NodeJsStartBuildRequest
      */
@@ -7965,10 +8126,11 @@ export declare const HostingV1NodeJsStartBuildRequestPackageManagerEnum: {
 export type HostingV1NodeJsStartBuildRequestPackageManagerEnum = typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum[keyof typeof HostingV1NodeJsStartBuildRequestPackageManagerEnum];
 export declare const HostingV1NodeJsStartBuildRequestSourceTypeEnum: {
     readonly Archive: "archive";
+    readonly Git: "git";
 };
 export type HostingV1NodeJsStartBuildRequestSourceTypeEnum = typeof HostingV1NodeJsStartBuildRequestSourceTypeEnum[keyof typeof HostingV1NodeJsStartBuildRequestSourceTypeEnum];
 /**
- * Source-specific options
+ * Source-specific options. For `archive` send `archive_path`. For `git` send `owner`, `repository`, `branch` and `installation_uuid`, taken from `List Git installations` and `List Git installation repositories`.
  * @export
  * @interface HostingV1NodeJsStartBuildRequestSourceOptions
  */
@@ -7979,6 +8141,30 @@ export interface HostingV1NodeJsStartBuildRequestSourceOptions {
      * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
      */
     'archive_path': string;
+    /**
+     * Repository owner login (required if source is \"git\"). GitLab group paths use slashes.
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
+     */
+    'owner': string;
+    /**
+     * Repository name without the .git suffix (required if source is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
+     */
+    'repository': string;
+    /**
+     * Branch to build (required if source is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
+     */
+    'branch': string;
+    /**
+     * Git installation used to access the repository (required if source is \"git\")
+     * @type {string}
+     * @memberof HostingV1NodeJsStartBuildRequestSourceOptions
+     */
+    'installation_uuid': string;
 }
 /**
  *
@@ -23204,7 +23390,25 @@ export type ListWebsiteFilesAndDirectoriesV1FileTypesEnum = typeof ListWebsiteFi
  */
 export declare const HostingGitApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and `default_branch` identify a repository and a branch to deploy. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
+     * Removes the Git auto-deployment settings of the website. Files already deployed stay on the website; pushes stop deploying until settings are saved again. Succeeds also when nothing is configured.
+     * @summary Delete Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deleteGitAutoDeploymentSettingsV1: (username: string, domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the Git auto-deployment settings of the website: which repository and branch deploy into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the repository link but ignores pushes.  When the website has no auto-deployment configured every field is null. Save settings with `Update Git auto-deployment settings`.
+     * @summary Get Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitAutoDeploymentSettingsV1: (username: string, domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of `Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
      * @summary List Git installation repositories
      * @param {string} uuid Git installation UUID from the List Git installations endpoint
      * @param {*} [options] Override http request option.
@@ -23212,7 +23416,7 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
      */
     listGitInstallationRepositoriesV1: (uuid: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, GitHub has to be connected once in hPanel (Websites, Manage, Advanced, Git, Connect GitHub; or Add Website, Node.js Web App, Import Git Repository, Continue with GitHub); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`.
+     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App, Import Git Repository); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`, and as `installation_uuid` in `Start Node.js build` with `source_type` `git` and in `Update Git auto-deployment settings`.
      * @summary List Git installations
      * @param {ListGitInstallationsV1ProviderEnum} [provider] Filter by Git provider
      * @param {ListGitInstallationsV1StatusEnum} [status] Filter by installation status
@@ -23220,6 +23424,16 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
      * @throws {RequiredError}
      */
     listGitInstallationsV1: (provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Creates or replaces the Git auto-deployment settings of the website: repository, branch, the directory under the document root to deploy into, and `is_enabled`. Send the full set; `is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must be an installation from `List Git installations` that belongs to the same customer as the website.  For PHP and static websites, saving with `is_enabled` true deploys the branch right away and every later push to that branch deploys again. For Node.js and Website Builder websites saving does not clone anything. On a Node.js website start the first deploy with `Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build settings stored for the website.
+     * @summary Update Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitUpdateGitAutoDeploymentSettingsRequest} hostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    updateGitAutoDeploymentSettingsV1: (username: string, domain: string, hostingV1GitUpdateGitAutoDeploymentSettingsRequest: HostingV1GitUpdateGitAutoDeploymentSettingsRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
 };
 /**
  * HostingGitApi - functional programming interface
@@ -23227,7 +23441,25 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
  */
 export declare const HostingGitApiFp: (configuration?: Configuration) => {
     /**
-     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and `default_branch` identify a repository and a branch to deploy. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
+     * Removes the Git auto-deployment settings of the website. Files already deployed stay on the website; pushes stop deploying until settings are saved again. Succeeds also when nothing is configured.
+     * @summary Delete Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * Returns the Git auto-deployment settings of the website: which repository and branch deploy into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the repository link but ignores pushes.  When the website has no auto-deployment configured every field is null. Save settings with `Update Git auto-deployment settings`.
+     * @summary Get Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1GitGitAutoDeploymentSettingsResource>>;
+    /**
+     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of `Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
      * @summary List Git installation repositories
      * @param {string} uuid Git installation UUID from the List Git installations endpoint
      * @param {*} [options] Override http request option.
@@ -23235,7 +23467,7 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
      */
     listGitInstallationRepositoriesV1(uuid: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1GitGitRepositoryResource>>>;
     /**
-     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, GitHub has to be connected once in hPanel (Websites, Manage, Advanced, Git, Connect GitHub; or Add Website, Node.js Web App, Import Git Repository, Continue with GitHub); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`.
+     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App, Import Git Repository); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`, and as `installation_uuid` in `Start Node.js build` with `source_type` `git` and in `Update Git auto-deployment settings`.
      * @summary List Git installations
      * @param {ListGitInstallationsV1ProviderEnum} [provider] Filter by Git provider
      * @param {ListGitInstallationsV1StatusEnum} [status] Filter by installation status
@@ -23243,6 +23475,16 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1GitGitInstallationResource>>>;
+    /**
+     * Creates or replaces the Git auto-deployment settings of the website: repository, branch, the directory under the document root to deploy into, and `is_enabled`. Send the full set; `is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must be an installation from `List Git installations` that belongs to the same customer as the website.  For PHP and static websites, saving with `is_enabled` true deploys the branch right away and every later push to that branch deploys again. For Node.js and Website Builder websites saving does not clone anything. On a Node.js website start the first deploy with `Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build settings stored for the website.
+     * @summary Update Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitUpdateGitAutoDeploymentSettingsRequest} hostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    updateGitAutoDeploymentSettingsV1(username: string, domain: string, hostingV1GitUpdateGitAutoDeploymentSettingsRequest: HostingV1GitUpdateGitAutoDeploymentSettingsRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
 };
 /**
  * HostingGitApi - factory interface
@@ -23250,7 +23492,25 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingGitApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and `default_branch` identify a repository and a branch to deploy. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
+     * Removes the Git auto-deployment settings of the website. Files already deployed stay on the website; pushes stop deploying until settings are saved again. Succeeds also when nothing is configured.
+     * @summary Delete Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
+    /**
+     * Returns the Git auto-deployment settings of the website: which repository and branch deploy into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the repository link but ignores pushes.  When the website has no auto-deployment configured every field is null. Save settings with `Update Git auto-deployment settings`.
+     * @summary Get Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1GitGitAutoDeploymentSettingsResource>;
+    /**
+     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of `Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
      * @summary List Git installation repositories
      * @param {string} uuid Git installation UUID from the List Git installations endpoint
      * @param {*} [options] Override http request option.
@@ -23258,7 +23518,7 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
      */
     listGitInstallationRepositoriesV1(uuid: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1GitGitRepositoryResource>>;
     /**
-     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, GitHub has to be connected once in hPanel (Websites, Manage, Advanced, Git, Connect GitHub; or Add Website, Node.js Web App, Import Git Repository, Continue with GitHub); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`.
+     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App, Import Git Repository); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`, and as `installation_uuid` in `Start Node.js build` with `source_type` `git` and in `Update Git auto-deployment settings`.
      * @summary List Git installations
      * @param {ListGitInstallationsV1ProviderEnum} [provider] Filter by Git provider
      * @param {ListGitInstallationsV1StatusEnum} [status] Filter by installation status
@@ -23266,6 +23526,16 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
      * @throws {RequiredError}
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1GitGitInstallationResource>>;
+    /**
+     * Creates or replaces the Git auto-deployment settings of the website: repository, branch, the directory under the document root to deploy into, and `is_enabled`. Send the full set; `is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must be an installation from `List Git installations` that belongs to the same customer as the website.  For PHP and static websites, saving with `is_enabled` true deploys the branch right away and every later push to that branch deploys again. For Node.js and Website Builder websites saving does not clone anything. On a Node.js website start the first deploy with `Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build settings stored for the website.
+     * @summary Update Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitUpdateGitAutoDeploymentSettingsRequest} hostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    updateGitAutoDeploymentSettingsV1(username: string, domain: string, hostingV1GitUpdateGitAutoDeploymentSettingsRequest: HostingV1GitUpdateGitAutoDeploymentSettingsRequest, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
 };
 /**
  * HostingGitApi - object-oriented interface
@@ -23275,7 +23545,27 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
  */
 export declare class HostingGitApi extends BaseAPI {
     /**
-     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and `default_branch` identify a repository and a branch to deploy. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
+     * Removes the Git auto-deployment settings of the website. Files already deployed stay on the website; pushes stop deploying until settings are saved again. Succeeds also when nothing is configured.
+     * @summary Delete Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * Returns the Git auto-deployment settings of the website: which repository and branch deploy into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the repository link but ignores pushes.  When the website has no auto-deployment configured every field is null. Save settings with `Update Git auto-deployment settings`.
+     * @summary Get Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitAutoDeploymentSettingsResource, any, {}, any>>;
+    /**
+     * Lists the repositories the Git installation can access, read live from the provider. Works for github and gitlab installations. Use an active installation: a suspended or pending one is still queried and the call fails with whatever the provider answers. The list is cut at the first 500 repositories in the order the provider returns them; when the account has more, name the repository directly instead of searching this list.  `owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of `Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the installation does not belong to the customer. Limited to 10 calls per minute per API client (429 above that).
      * @summary List Git installation repositories
      * @param {string} uuid Git installation UUID from the List Git installations endpoint
      * @param {*} [options] Override http request option.
@@ -23284,7 +23574,7 @@ export declare class HostingGitApi extends BaseAPI {
      */
     listGitInstallationRepositoriesV1(uuid: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitRepositoryResource[], any, {}, any>>;
     /**
-     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, GitHub has to be connected once in hPanel (Websites, Manage, Advanced, Git, Connect GitHub; or Add Website, Node.js Web App, Import Git Repository, Continue with GitHub); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`.
+     * Lists the Git provider accounts the customer has connected. Only installations with status `active` are returned unless the `status` filter says otherwise.  An empty list means the customer has no active installation. Check `status=suspended` and `status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App, Import Git Repository); this endpoint then lists the new installation.  Use `uuid` as the path parameter of `List Git installation repositories`, and as `installation_uuid` in `Start Node.js build` with `source_type` `git` and in `Update Git auto-deployment settings`.
      * @summary List Git installations
      * @param {ListGitInstallationsV1ProviderEnum} [provider] Filter by Git provider
      * @param {ListGitInstallationsV1StatusEnum} [status] Filter by installation status
@@ -23293,6 +23583,17 @@ export declare class HostingGitApi extends BaseAPI {
      * @memberof HostingGitApi
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitInstallationResource[], any, {}, any>>;
+    /**
+     * Creates or replaces the Git auto-deployment settings of the website: repository, branch, the directory under the document root to deploy into, and `is_enabled`. Send the full set; `is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must be an installation from `List Git installations` that belongs to the same customer as the website.  For PHP and static websites, saving with `is_enabled` true deploys the branch right away and every later push to that branch deploys again. For Node.js and Website Builder websites saving does not clone anything. On a Node.js website start the first deploy with `Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build settings stored for the website.
+     * @summary Update Git auto-deployment settings
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitUpdateGitAutoDeploymentSettingsRequest} hostingV1GitUpdateGitAutoDeploymentSettingsRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    updateGitAutoDeploymentSettingsV1(username: string, domain: string, hostingV1GitUpdateGitAutoDeploymentSettingsRequest: HostingV1GitUpdateGitAutoDeploymentSettingsRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
 }
 /**
  * @export
@@ -23450,7 +23751,7 @@ export declare const HostingNodeJSApiAxiosParamCreator: (configuration?: Configu
      */
     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.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+     * 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.  With `source_type` `archive`, `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.  With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and `installation_uuid`. Take the installation from `List Git installations` and the owner and repository from `List Git installation repositories`; the branch is cloned at its current head. The installation must belong to the same customer as the website.  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
@@ -23608,7 +23909,7 @@ export declare const HostingNodeJSApiFp: (configuration?: Configuration) => {
      */
     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.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+     * 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.  With `source_type` `archive`, `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.  With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and `installation_uuid`. Take the installation from `List Git installations` and the owner and repository from `List Git installation repositories`; the branch is cloned at its current head. The installation must belong to the same customer as the website.  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
@@ -23766,7 +24067,7 @@ export declare const HostingNodeJSApiFactory: (configuration?: Configuration, ba
      */
     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.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+     * 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.  With `source_type` `archive`, `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.  With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and `installation_uuid`. Take the installation from `List Git installations` and the owner and repository from `List Git installation repositories`; the branch is cloned at its current head. The installation must belong to the same customer as the website.  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
@@ -23939,7 +24240,7 @@ export declare class HostingNodeJSApi extends BaseAPI {
      */
     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.  The returned build `uuid` can be used to poll progress and retrieve logs via the `Get Node.js Build Logs` endpoint.
+     * 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.  With `source_type` `archive`, `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.  With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and `installation_uuid`. Take the installation from `List Git installations` and the owner and repository from `List Git installation repositories`; the branch is cloned at its current head. The installation must belong to the same customer as the website.  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