hostinger-api-mcp 0.2.3 → 0.2.5

package/types.d.ts

@@ -796,6 +796,91 @@ Use this endpoint to view which domains use specific contact profiles.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Returns a paginated list of databases for the specified account.
+
+Use the domain and is_assigned filters to find databases assigned to a specific domain.
+   */
+  "hosting_listAccountDatabasesV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+      /**
+       * Filter by domain name (exact match)
+       */
+      domain?: string;
+      /**
+       * When used with domain, return only databases assigned to that domain.
+       */
+      is_assigned?: boolean;
+      /**
+       * Search databases by name, user, or creation date.
+       */
+      search?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Creates a database with a database user and password for the specified account.
+
+The database name and user are automatically prefixed with the account username when needed.
+   */
+  "hosting_createAccountDatabaseV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Database name. If the account username prefix is omitted, it is added automatically.
+       */
+      name: string;
+      /**
+       * Database user. If the account username prefix is omitted, it is added automatically.
+       */
+      user: string;
+      /**
+       * Database user password.
+       */
+      password: string;
+      /**
+       * Website domain assigned to the database.
+       */
+      website_domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Permanently deletes a database and its remote connections.
+
+The database name must be the full name returned by the list databases endpoint.
+   */
+  "hosting_deleteAccountDatabaseV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Full database name as returned by the list databases endpoint.
+       */
+      name: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a list of datacenters available for setting up hosting plans
 based on available datacenter capacity and hosting plan of your order.
@@ -824,6 +909,73 @@ and you can always connect a custom domain to your site later.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve all parked or alias domains created under the selected website.
+
+Use this endpoint to inspect parked domain configuration for a specific website,
+including the parent domain and root directory assigned to each parked domain.
+   */
+  "hosting_listWebsiteParkedDomainsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Create a parked or alias domain for the selected website.
+
+Provide a domain name or IP address to park on the website so it serves the same content
+as the parent domain.
+   */
+  "hosting_createWebsiteParkedDomainV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Domain name or IP address to park on the selected website
+       */
+      parked_domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Delete an existing parked or alias domain from the selected website.
+
+Use this endpoint to remove parked domains that are no longer needed.
+   */
+  "hosting_deleteWebsiteParkedDomainV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * parkedDomain parameter
+       */
+      parkedDomain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve all subdomains created under the selected website.
 
@@ -1021,6 +1173,99 @@ websites list endpoint to see when your new website becomes available.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Install WordPress on an existing website.
+
+The website must already exist before calling this endpoint. To create a new
+website first, use POST /api/hosting/v1/websites and poll
+GET /api/hosting/v1/websites until it appears.
+
+Call GET /api/hosting/v1/wordpress/installations filtered by username and
+domain before proceeding to check whether WordPress is already installed on
+the target domain/path. If WordPress already exists and `overwrite` is false
+(the default), the async job will fail.
+
+This operation is asynchronous: a successful response only means the install
+job has been queued, not that WordPress is ready. Installation typically
+takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered
+by username and domain to track progress. When the installation appears in
+that list, WordPress is ready.
+   */
+  "hosting_installWordPressV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain of the existing website where WordPress will be installed
+       */
+      domain: string;
+      /**
+       * Title of the WordPress site
+       */
+      site_title: string;
+      /**
+       * WordPress locale. Defaults to en_US when omitted.
+       */
+      language?: string;
+      /**
+       * Relative directory to install WordPress into. Defaults to the website root when omitted.
+       */
+      directory?: string;
+      /**
+       * When false (default), does not replace an existing installation. If WordPress is already installed on the domain/path, the async install job fails unless true.
+       */
+      overwrite?: boolean;
+      /**
+       * WordPress core auto-update policy
+       */
+      auto_updates?: string;
+      /**
+       * WordPress core version to install. If omitted, the latest core version compatible with the account vhost PHP version is selected.
+       */
+      version?: string;
+      /**
+       * WordPress admin credentials
+       */
+      credentials: object;
+      /**
+       * Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random credentials.
+       */
+      database?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * List WordPress installations accessible to the authenticated client.
+
+Use this endpoint to discover existing WordPress installations and to poll
+for installation status after calling the install endpoint. When a newly
+requested installation appears in this list, WordPress is ready. Filter by
+username and domain to narrow results to a specific website.
+
+Each installation includes a `valid` flag and, when invalid, a
+`validationError` describing why.
+   */
+  "hosting_listWordPressInstallationsV1": {
+    params: {
+      /**
+       * Filter by specific username
+       */
+      username?: string;
+      /**
+       * Filter by domain name (exact match)
+       */
+      domain?: string;
+      /**
+       * Filter by ownership type. Defaults to "owned". Use "all" to include both owned and managed installations.
+       */
+      ownership?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Delete a contact with the specified UUID.