@hostinger/sdk 1.58.0 → 1.58.2

package/dist/esm/api.d.ts

@@ -1,7 +1,7 @@
 /**
  * Hostinger API
  *
- * API Version: 1.58.0
+ * API Version: 1.58.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
@@ -7342,6 +7342,31 @@ export interface HostingV1FilesUploadUrlResource {
      */
     'rest_auth_key': string;
 }
+/**
+ *
+ * @export
+ * @interface HostingV1GitDeployWebsiteGitRepositoryRequest
+ */
+export interface HostingV1GitDeployWebsiteGitRepositoryRequest {
+    /**
+     * Clone URL of the repository on any Git host, SSH or HTTPS. Private repositories need an SSH URL and the account\'s Git SSH key added to the repository as a deploy key. An HTTP or HTTPS URL with a username or token, or any URL with a password, is rejected.
+     * @type {string}
+     * @memberof HostingV1GitDeployWebsiteGitRepositoryRequest
+     */
+    'repository_url': string;
+    /**
+     * Branch to clone and pull
+     * @type {string}
+     * @memberof HostingV1GitDeployWebsiteGitRepositoryRequest
+     */
+    'branch': string;
+    /**
+     * Directory under the website document root, exactly as `List website Git repositories` returns it for an existing repository. Empty, null or omitted means the document root.
+     * @type {string}
+     * @memberof HostingV1GitDeployWebsiteGitRepositoryRequest
+     */
+    'directory': string | null;
+}
 /**
  * Every field is null when the website has no Git auto-deployment configured.
  * @export
@@ -7429,6 +7454,25 @@ export interface HostingV1GitGitCommitResource {
      */
     'author': HostingV1GitGitCommitAuthorResource;
 }
+/**
+ * Result of cloning or pulling a Git repository into the website
+ * @export
+ * @interface HostingV1GitGitDeployOutputResource
+ */
+export interface HostingV1GitGitDeployOutputResource {
+    /**
+     * Whether the clone or pull, and composer install when it ran, finished without errors
+     * @type {boolean}
+     * @memberof HostingV1GitGitDeployOutputResource
+     */
+    'is_success': boolean;
+    /**
+     * Log of the deployment steps, and the Git or composer error when `is_success` is false
+     * @type {string}
+     * @memberof HostingV1GitGitDeployOutputResource
+     */
+    'output': string;
+}
 /**
  *
  * @export
@@ -7562,6 +7606,19 @@ export interface HostingV1GitGitRepositoryResource {
      */
     'default_branch': string;
 }
+/**
+ * Public SSH key the hosting account uses to clone and pull Git repositories
+ * @export
+ * @interface HostingV1GitGitSshKeyResource
+ */
+export interface HostingV1GitGitSshKeyResource {
+    /**
+     * Public key to add as a deploy key on the Git host. Null when the account has no key yet.
+     * @type {string}
+     * @memberof HostingV1GitGitSshKeyResource
+     */
+    'public_key': string | null;
+}
 /**
  *
  * @export
@@ -7605,6 +7662,68 @@ export interface HostingV1GitUpdateGitAutoDeploymentSettingsRequest {
      */
     'is_enabled': boolean;
 }
+/**
+ * Git repository linked to a directory of the website. A repository whose clone failed stays listed; deploying it again retries the clone.
+ * @export
+ * @interface HostingV1GitWebsiteGitRepositoryResource
+ */
+export interface HostingV1GitWebsiteGitRepositoryResource {
+    /**
+     * Clone URL of the repository. A username, password or token in an HTTP(S) URL, or a password in any URL, is shown as `***`.
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryResource
+     */
+    'repository_url': string;
+    /**
+     * Branch that is cloned and pulled
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryResource
+     */
+    'branch': string;
+    /**
+     * Directory under the website document root. Empty means the document root.
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryResource
+     */
+    'directory': string;
+    /**
+     *
+     * @type {HostingV1GitWebsiteGitRepositoryWebhookResource}
+     * @memberof HostingV1GitWebsiteGitRepositoryResource
+     */
+    'webhook': HostingV1GitWebsiteGitRepositoryWebhookResource;
+}
+/**
+ * Auto-deployment webhook of the repository, the same one the Git section of hPanel shows
+ * @export
+ * @interface HostingV1GitWebsiteGitRepositoryWebhookResource
+ */
+export interface HostingV1GitWebsiteGitRepositoryWebhookResource {
+    /**
+     * Webhook URL to add on the Git host for automatic deployment
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryWebhookResource
+     */
+    'url': string;
+    /**
+     * Git host detected from the repository URL. Null when it is not GitHub, GitLab or Bitbucket.
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryWebhookResource
+     */
+    'provider': string | null;
+    /**
+     * Page on the Git host where the webhook is added. Null when the host is not detected.
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryWebhookResource
+     */
+    'setup_url': string | null;
+    /**
+     * Git host guide for adding a webhook. Null when the host is not detected.
+     * @type {string}
+     * @memberof HostingV1GitWebsiteGitRepositoryWebhookResource
+     */
+    'tutorial_url': string | null;
+}
 /**
  *
  * @export
@@ -23928,6 +24047,24 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
      * @throws {RequiredError}
      */
     deleteGitAutoDeploymentSettingsV1: (username: string, domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Clones a Git repository into a directory of the website, or pulls it again. An empty or missing directory gets a clone of the branch. A directory that already holds this repository and branch is reset to its last commit and pulled: changes made on the server to files the repository tracks are discarded, files it does not track stay. A directory that holds other files, including another repository or another branch of this one, is rejected. `composer install` runs after the clone or pull when the repository has a `composer.json`.  The call waits for the deployment and returns its log. `is_success` false means Git or composer failed and the log says why. A second call for the same directory is rejected while the first is still waiting for the server. If the request times out, the deployment may still finish on the server; calling again later with the same repository and branch pulls.  Private repositories need an SSH URL and the account\'s Git SSH key from `Generate Git SSH key`, added to the repository as a deploy key.
+     * @summary Deploy website Git repository
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitDeployWebsiteGitRepositoryRequest} hostingV1GitDeployWebsiteGitRepositoryRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deployWebsiteGitRepositoryV1: (username: string, domain: string, hostingV1GitDeployWebsiteGitRepositoryRequest: HostingV1GitDeployWebsiteGitRepositoryRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Creates the SSH key pair of the hosting account and returns the public key. When the account already has a key, returns that key unchanged. One key serves every website of the account; add the public key to a private repository as a deploy key before deploying it.
+     * @summary Generate Git SSH key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateGitSSHKeyV1: (username: 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
@@ -23937,6 +24074,14 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
      * @throws {RequiredError}
      */
     getGitAutoDeploymentSettingsV1: (username: string, domain: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the public SSH key of the hosting account. `Deploy website Git repository` uses this key to clone and pull over SSH, so a private repository works once the key is added to it as a deploy key on the Git host. `public_key` is null when the account has no key yet.
+     * @summary Get Git SSH public key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitSSHPublicKeyV1: (username: 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
@@ -23954,6 +24099,15 @@ export declare const HostingGitApiAxiosParamCreator: (configuration?: Configurat
      * @throws {RequiredError}
      */
     listGitInstallationsV1: (provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Lists the Git repositories linked to directories of the website, with `Deploy website Git repository` or in the Git section of hPanel: clone URL, branch and directory of each one. A repository whose clone failed stays listed; deploying it again retries the clone. GitHub and GitLab auto-deployments are not listed here; see `Get Git auto-deployment settings`.
+     * @summary List website Git repositories
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listWebsiteGitRepositoriesV1: (username: string, domain: string, 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
@@ -23979,6 +24133,24 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CommonSuccessEmptyResource>>;
+    /**
+     * Clones a Git repository into a directory of the website, or pulls it again. An empty or missing directory gets a clone of the branch. A directory that already holds this repository and branch is reset to its last commit and pulled: changes made on the server to files the repository tracks are discarded, files it does not track stay. A directory that holds other files, including another repository or another branch of this one, is rejected. `composer install` runs after the clone or pull when the repository has a `composer.json`.  The call waits for the deployment and returns its log. `is_success` false means Git or composer failed and the log says why. A second call for the same directory is rejected while the first is still waiting for the server. If the request times out, the deployment may still finish on the server; calling again later with the same repository and branch pulls.  Private repositories need an SSH URL and the account\'s Git SSH key from `Generate Git SSH key`, added to the repository as a deploy key.
+     * @summary Deploy website Git repository
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitDeployWebsiteGitRepositoryRequest} hostingV1GitDeployWebsiteGitRepositoryRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deployWebsiteGitRepositoryV1(username: string, domain: string, hostingV1GitDeployWebsiteGitRepositoryRequest: HostingV1GitDeployWebsiteGitRepositoryRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1GitGitDeployOutputResource>>;
+    /**
+     * Creates the SSH key pair of the hosting account and returns the public key. When the account already has a key, returns that key unchanged. One key serves every website of the account; add the public key to a private repository as a deploy key before deploying it.
+     * @summary Generate Git SSH key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateGitSSHKeyV1(username: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1GitGitSshKeyResource>>;
     /**
      * 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
@@ -23988,6 +24160,14 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1GitGitAutoDeploymentSettingsResource>>;
+    /**
+     * Returns the public SSH key of the hosting account. `Deploy website Git repository` uses this key to clone and pull over SSH, so a private repository works once the key is added to it as a deploy key on the Git host. `public_key` is null when the account has no key yet.
+     * @summary Get Git SSH public key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitSSHPublicKeyV1(username: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<HostingV1GitGitSshKeyResource>>;
     /**
      * 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
@@ -24005,6 +24185,15 @@ export declare const HostingGitApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1GitGitInstallationResource>>>;
+    /**
+     * Lists the Git repositories linked to directories of the website, with `Deploy website Git repository` or in the Git section of hPanel: clone URL, branch and directory of each one. A repository whose clone failed stays listed; deploying it again retries the clone. GitHub and GitLab auto-deployments are not listed here; see `Get Git auto-deployment settings`.
+     * @summary List website Git repositories
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listWebsiteGitRepositoriesV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<HostingV1GitWebsiteGitRepositoryResource>>>;
     /**
      * 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
@@ -24030,6 +24219,24 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
      * @throws {RequiredError}
      */
     deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<CommonSuccessEmptyResource>;
+    /**
+     * Clones a Git repository into a directory of the website, or pulls it again. An empty or missing directory gets a clone of the branch. A directory that already holds this repository and branch is reset to its last commit and pulled: changes made on the server to files the repository tracks are discarded, files it does not track stay. A directory that holds other files, including another repository or another branch of this one, is rejected. `composer install` runs after the clone or pull when the repository has a `composer.json`.  The call waits for the deployment and returns its log. `is_success` false means Git or composer failed and the log says why. A second call for the same directory is rejected while the first is still waiting for the server. If the request times out, the deployment may still finish on the server; calling again later with the same repository and branch pulls.  Private repositories need an SSH URL and the account\'s Git SSH key from `Generate Git SSH key`, added to the repository as a deploy key.
+     * @summary Deploy website Git repository
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitDeployWebsiteGitRepositoryRequest} hostingV1GitDeployWebsiteGitRepositoryRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    deployWebsiteGitRepositoryV1(username: string, domain: string, hostingV1GitDeployWebsiteGitRepositoryRequest: HostingV1GitDeployWebsiteGitRepositoryRequest, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1GitGitDeployOutputResource>;
+    /**
+     * Creates the SSH key pair of the hosting account and returns the public key. When the account already has a key, returns that key unchanged. One key serves every website of the account; add the public key to a private repository as a deploy key before deploying it.
+     * @summary Generate Git SSH key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateGitSSHKeyV1(username: string, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1GitGitSshKeyResource>;
     /**
      * 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
@@ -24039,6 +24246,14 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
      * @throws {RequiredError}
      */
     getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1GitGitAutoDeploymentSettingsResource>;
+    /**
+     * Returns the public SSH key of the hosting account. `Deploy website Git repository` uses this key to clone and pull over SSH, so a private repository works once the key is added to it as a deploy key on the Git host. `public_key` is null when the account has no key yet.
+     * @summary Get Git SSH public key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getGitSSHPublicKeyV1(username: string, options?: RawAxiosRequestConfig): AxiosPromise<HostingV1GitGitSshKeyResource>;
     /**
      * 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
@@ -24056,6 +24271,15 @@ export declare const HostingGitApiFactory: (configuration?: Configuration, baseP
      * @throws {RequiredError}
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1GitGitInstallationResource>>;
+    /**
+     * Lists the Git repositories linked to directories of the website, with `Deploy website Git repository` or in the Git section of hPanel: clone URL, branch and directory of each one. A repository whose clone failed stays listed; deploying it again retries the clone. GitHub and GitLab auto-deployments are not listed here; see `Get Git auto-deployment settings`.
+     * @summary List website Git repositories
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listWebsiteGitRepositoriesV1(username: string, domain: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<HostingV1GitWebsiteGitRepositoryResource>>;
     /**
      * 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
@@ -24084,6 +24308,26 @@ export declare class HostingGitApi extends BaseAPI {
      * @memberof HostingGitApi
      */
     deleteGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<CommonSuccessEmptyResource, any, {}, any>>;
+    /**
+     * Clones a Git repository into a directory of the website, or pulls it again. An empty or missing directory gets a clone of the branch. A directory that already holds this repository and branch is reset to its last commit and pulled: changes made on the server to files the repository tracks are discarded, files it does not track stay. A directory that holds other files, including another repository or another branch of this one, is rejected. `composer install` runs after the clone or pull when the repository has a `composer.json`.  The call waits for the deployment and returns its log. `is_success` false means Git or composer failed and the log says why. A second call for the same directory is rejected while the first is still waiting for the server. If the request times out, the deployment may still finish on the server; calling again later with the same repository and branch pulls.  Private repositories need an SSH URL and the account\'s Git SSH key from `Generate Git SSH key`, added to the repository as a deploy key.
+     * @summary Deploy website Git repository
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {HostingV1GitDeployWebsiteGitRepositoryRequest} hostingV1GitDeployWebsiteGitRepositoryRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    deployWebsiteGitRepositoryV1(username: string, domain: string, hostingV1GitDeployWebsiteGitRepositoryRequest: HostingV1GitDeployWebsiteGitRepositoryRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitDeployOutputResource, any, {}, any>>;
+    /**
+     * Creates the SSH key pair of the hosting account and returns the public key. When the account already has a key, returns that key unchanged. One key serves every website of the account; add the public key to a private repository as a deploy key before deploying it.
+     * @summary Generate Git SSH key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    generateGitSSHKeyV1(username: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitSshKeyResource, 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
@@ -24094,6 +24338,15 @@ export declare class HostingGitApi extends BaseAPI {
      * @memberof HostingGitApi
      */
     getGitAutoDeploymentSettingsV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitAutoDeploymentSettingsResource, any, {}, any>>;
+    /**
+     * Returns the public SSH key of the hosting account. `Deploy website Git repository` uses this key to clone and pull over SSH, so a private repository works once the key is added to it as a deploy key on the Git host. `public_key` is null when the account has no key yet.
+     * @summary Get Git SSH public key
+     * @param {string} username
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    getGitSSHPublicKeyV1(username: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitSshKeyResource, 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
@@ -24113,6 +24366,16 @@ export declare class HostingGitApi extends BaseAPI {
      * @memberof HostingGitApi
      */
     listGitInstallationsV1(provider?: ListGitInstallationsV1ProviderEnum, status?: ListGitInstallationsV1StatusEnum, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitGitInstallationResource[], any, {}, any>>;
+    /**
+     * Lists the Git repositories linked to directories of the website, with `Deploy website Git repository` or in the Git section of hPanel: clone URL, branch and directory of each one. A repository whose clone failed stays listed; deploying it again retries the clone. GitHub and GitLab auto-deployments are not listed here; see `Get Git auto-deployment settings`.
+     * @summary List website Git repositories
+     * @param {string} username
+     * @param {string} domain Domain name
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof HostingGitApi
+     */
+    listWebsiteGitRepositoriesV1(username: string, domain: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<HostingV1GitWebsiteGitRepositoryResource[], 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
@@ -24841,7 +25104,7 @@ export type ListNodeJsVulnerabilitiesV1SeveritiesEnum = typeof ListNodeJsVulnera
  */
 export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -24858,7 +25121,7 @@ export declare const HostingOrdersApiAxiosParamCreator: (configuration?: Configu
  */
 export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -24875,7 +25138,7 @@ export declare const HostingOrdersApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingOrdersApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -24894,7 +25157,7 @@ export declare const HostingOrdersApiFactory: (configuration?: Configuration, ba
  */
 export declare class HostingOrdersApi extends BaseAPI {
     /**
-     * Retrieve a paginated list of orders accessible to the authenticated client.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
+     * Retrieve a paginated list of orders accessible to the authenticated client.  Only Web and Cloud hosting orders are listed. Agency Plan orders are listed by `GET /api/agency-hosting/v1/orders`.  This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.  Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.
      * @summary List orders
      * @param {number} [page] Page number
      * @param {number} [perPage] Number of items per page
@@ -25513,7 +25776,7 @@ export declare class HostingSSLApi extends BaseAPI {
  */
 export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25567,7 +25830,7 @@ export declare const HostingWebsitesApiAxiosParamCreator: (configuration?: Confi
  */
 export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25621,7 +25884,7 @@ export declare const HostingWebsitesApiFp: (configuration?: Configuration) => {
  */
 export declare const HostingWebsitesApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.
@@ -25677,7 +25940,7 @@ export declare const HostingWebsitesApiFactory: (configuration?: Configuration,
  */
 export declare class HostingWebsitesApi extends BaseAPI {
     /**
-     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
+     * Create a new website for the authenticated client.  You must choose which hosting order to create this website on. Pass that order as `order_id` together with the domain name. List orders to see available IDs; the website is provisioned on that order\'s hosting plan.  Only Web and Cloud hosting orders are accepted. To create a website on an Agency Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.  The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.  Subsequent websites will be hosted on the same datacenter automatically.  Website creation is asynchronous and takes up to a few minutes. Poll the list website setups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status: completed` before uploading files, deploying or creating databases. While the setup is `running`, endpoints that operate on the website may respond with `404` or `409`. `is_enabled` on the websites list reflects suspension, not readiness.
      * @summary Create website
      * @param {HostingV1WebsitesCreateWebsiteRequest} hostingV1WebsitesCreateWebsiteRequest
      * @param {*} [options] Override http request option.