[FEATURE] Expose Docker Manager Catalog endpoints in the public API

[marcelocecin]

Feature Request: Expose Docker Manager Catalog endpoints in the public API

Feature Description

Please expose the Docker Manager Catalog endpoints in the public Hostinger API. Currently, when navigating through the hPanel, the frontend fetches catalog application data from an internal URL like https://hpanel.hostinger.com/vps/{vps_id}/docker-manager/catalog, but there are no corresponding endpoints documented or available in the official Hostinger API Reference under the VPS section. [1, 2]

Problem Statement

I am trying to programmatically automate, audit, or script the deployment of pre-configured applications available in Hostinger's Docker Catalog. Since these endpoints are missing from the public API, I am forced to manually check the hPanel interface to see what templates and configurations are available, or reverse-engineer internal dashboard requests, which is unreliable and prone to breaking changes. [1, 3]

Proposed Solution

Add new endpoints under the VPS/Docker Manager section of the public API, such as: [2]

• GET /api/vps/v1/virtual-machines/{id}/docker-manager/catalog — To list all available applications, categories, and pre-configured templates in the Docker Catalog.
• GET /api/vps/v1/virtual-machines/{id}/docker-manager/catalog/{app_id} — To fetch specific docker-compose.yml base templates or variable schemes for a particular catalog app. [1, 3, 4]

Use Cases

1. Automated Provisioning: Allowing developers to build custom CLI tooling or scripts that query the active catalog to list and instantly deploy stacks (like n8n, WordPress, or OpenClaw) without opening hPanel. [1]
2. Infrastructure as Code (IaC): Integrating Hostinger's pre-built production configurations directly into custom deployment pipelines or management dashboards.

Additional Context

The official Hostinger documentation heavily promotes the "One-Click Deploy" Docker Catalog and the experimental Docker Manager features via API. However, while we can submit raw YAML files programmatically, we cannot leverage or fetch the platform's native curated ecosystem templates. [1, 2, 3]

Are you willing to contribute?

• No, but I'm available for testing

1 2 3 4