io.github.hostinger/hostinger-api-mcp
NPM · HOSTINGER-API-MCP · SCANNED AUG 3
MCP server for Hostinger API
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (130 of 131), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (130 of 131), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hostinger/api-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · hostinger-api-mcp
claude mcp add hostinger-hostinger-api-mcp -- npx -y hostinger-api-mcp
codex mcp add hostinger-hostinger-api-mcp -- npx -y hostinger-api-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hostinger-hostinger-api-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"hostinger-api-mcp"
],
"enabled": true
}
}
} openclaw mcp add hostinger-hostinger-api-mcp --command npx --arg -y --arg hostinger-api-mcp
mcp_servers:
hostinger-hostinger-api-mcp:
command: "npx"
args: ["-y", "hostinger-api-mcp"] {
"mcpServers": {
"hostinger-hostinger-api-mcp": {
"command": "npx",
"args": [
"-y",
"hostinger-api-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 −30
- Stability: fail → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 1.26.0 → 1.27.0 functional
- 2 Aug 26 +55
- Stability: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: hostinger/api-mcp-server security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Package version: 1.25.0 → 1.26.0 functional
- 28 Jul 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 1.23.0 → 1.25.0 functional
- 27 Jul 26 6
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- hostinger/api-mcp-server
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/hostinger/api-mcp-server/.github/workflows/build-release.yaml@refs/heads/main
- Rekor log index:
- 2334886922
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:2b5d7cc090533a4eae671a13600534a331a295d7ddb47f14838f4472f69a4607c124e868414c2453c43023e8c7c4e71d4d639301722a399c2f1671a10
- Discovery method:
- attestation_endpoint
Dependencies 130 packages
130 packages in the resolved dependency tree · 115 deprecated · 52 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
hosting_deleteWebsiteParkedDomainV1 ~68
Delete an existing parked or alias domain from the selected website. Use this endpoint to remove parked domains that are no longer needed.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| parkedDomain | string | yes | parkedDomain parameter |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_deleteWebsiteSubdomainV1 ~65
Delete an existing subdomain from the selected website. Use this endpoint to remove subdomains that are no longer needed.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| subdomain | string | yes | subdomain parameter |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_deleteWebsiteV1 ~191
Permanently deletes a website and all of its data. This action is destructive and cannot be undone. Always ask the user for explicit confirmation before calling this endpoint. All website files, databases and related configuration will be removed. The hosting plan itself is kept, so a new website can be created on it afterwards. The confirm field must be boolean true, otherwise the request is rejected. Supported websites: main and addon domain websites on web hosting plans, and Website Builder websites. Parked domains and subdomains cannot be deleted with this endpoint. The domain must be the exact website domain, not a preview domain or an alias. Returns 404 when the domain does not exist or does not belong to the authenticated client. Website removal is processed asynchronously and can take a few minutes to complete. The response returns before the removal finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
No output schema declared.
No examples provided.
hosting_deleteWordPressInstallationV1 ~108
Delete the specified WordPress installation, with optional file and database removal. This removes all associated components including plugins, themes, staging websites and any other related data. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_deployJsApplication ~210
Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
| Name | Type | Req | Description |
|---|---|---|---|
| archivePath | string | yes | Absolute or relative path to the application archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding. IMPORTANT… |
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| removeArchive | boolean | — | Whether to remove the archive file after successful deployment (default: false) |
No output schema declared.
No examples provided.
hosting_deployStaticWebsite ~234
Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The archive will be extracted and deployed directly without any build steps. The username will be automatically resolved from the domain.
| Name | Type | Req | Description |
|---|---|---|---|
| archivePath | string | yes | Absolute or relative path to the static website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding using E… |
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| removeArchive | boolean | — | Whether to remove the archive file after successful deployment (default: false) |
No output schema declared.
No examples provided.
hosting_deployWordpressPlugin ~93
Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| pluginPath | string | yes | Absolute or relative path to the plugin directory containing all plugin files |
| slug | string | yes | WordPress plugin slug (e.g., omnisend) |
No output schema declared.
No examples provided.
hosting_deployWordpressTheme ~125
Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| activate | boolean | — | Whether to activate the theme after deployment (default: false) |
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| slug | string | yes | WordPress theme slug (e.g., twentytwentyfive) |
| themePath | string | yes | Absolute or relative path to the theme directory containing all theme files |
No output schema declared.
No examples provided.
hosting_detectWordPressInstallationsV1 ~77
Trigger a background scan to detect WordPress installations for the account. This operation is asynchronous: a successful response only means the scan has been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the detected installations once the scan completes.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_generateAFreeSubdomainV1 ~57
Generate a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately and you can always connect a custom domain to your site later.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hosting_getCronJobOutputV1 ~71
Returns the output captured from the last execution of the cron job identified by its uid. The uid is returned by the list cron jobs endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Unique identifier of the cron job as returned by the list cron jobs endpoint. |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_getInstallationJWTTokenV1 ~99
Return a JWT token used to authenticate requests against the specified WordPress installation, including its MCP (Model Context Protocol) endpoint. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_getNodeJSBuildLogsV1 ~124
Retrieve logs from a specific Node.js build process. To stream live output while a build is running, poll this endpoint repeatedly while the build state is `running`, passing the previously returned `lines` count as `from_line` to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| from_line | integer | — | Line from which to start retrieving logs |
| username | string | yes | username parameter |
| uuid | string | yes | Build UUID |
No output schema declared.
No examples provided.
hosting_getPHPDetailsV1 ~94
Returns the full PHP configuration for the website: current version, available versions (supported and unsupported), enabled/disabled extensions, options with their current value, default, type and the plan limit (`max`), and conflicting extension groups. Use it to check the current PHP setup before updating the version, extensions or options.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_getPHPInfoV1 ~59
Returns the full phpinfo page (HTML) for the website. Use it to debug PHP issues or inspect the complete PHP environment of the website.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_getPhpMyAdminLinkV1 ~91
Returns a direct sign-on link to phpMyAdmin for the specified database. Use this when a visual database interface is needed for SQL queries, imports, exports, or table management. The database name must be the full name returned by the list databases endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full database name as returned by the list databases endpoint. |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_importWordpressWebsite ~230
Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain.
| Name | Type | Req | Description |
|---|---|---|---|
| archivePath | string | yes | Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding using EXACTLY… |
| databaseDump | string | yes | Absolute or relative path to a database dump file (.sql) |
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
No output schema declared.
No examples provided.
hosting_installWordPressPluginsV1 ~161
Install one or more plugins on an existing WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). Use GET /api/hosting/v1/wordpress/plugins to discover the plugin slugs available for installation. This operation is asynchronous: a successful response only means the install job has been queued, not that the plugins are ready.
| Name | Type | Req | Description |
|---|---|---|---|
| plugins | array | yes | Plugin slugs to install. Use GET /api/hosting/v1/wordpress/plugins to discover available slugs. |
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_installWordPressThemeV1 ~316
Install a theme on an existing WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field). When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional `palette`, `layout`, and `font` fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored. This operation is asynchronous: a successful response only means the install job has been queued, not that the theme is ready.
| Name | Type | Req | Description |
|---|---|---|---|
| font | string | — | Font identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted. |
| layout | string | — | Layout identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted. |
| palette | string | — | Palette identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted. |
| software | string | yes | WordPress installation (software) identifier |
| theme | string | yes | Slug of the theme to install. Hostinger theme slugs (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme) trigger the custom installer and forward the optional palette/layout/font fields; a… |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_installWordPressV1 ~403
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.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_updates | string | — | WordPress core auto-update policy |
| credentials | object | yes | WordPress admin credentials |
| database | 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. |
| directory | string | — | Relative directory to install WordPress into. Defaults to the website root when omitted. |
| domain | string | yes | Domain of the existing website where WordPress will be installed |
| language | string | — | WordPress locale. Defaults to en_US when omitted. |
| overwrite | boolean | — | 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. |
| site_title | string | yes | Title of the WordPress site |
| username | string | yes | username parameter |
| version | string | — | WordPress core version to install. If omitted, the latest core version compatible with the account vhost PHP version is selected. |
No output schema declared.
No examples provided.
hosting_listAccountCronJobsV1 ~40
Returns the list of cron jobs configured for the specified account, including their schedule and command.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listAccountDatabasesV1 ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Filter by domain name (exact match) |
| is_assigned | boolean | — | When used with domain, return only databases assigned to that domain. |
| page | integer | — | Page number |
| per_page | integer | — | Number of items per page |
| search | string | — | Search databases by name, user, or creation date. |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listAvailableDatacentersV1 ~68
Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID |
No output schema declared.
No examples provided.
hosting_listAvailableWordPressCoreUpdatesV1 ~86
List available WordPress core updates for the specified installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listAvailableWordPressPluginsV1 ~91
List plugins recommended for installation on a WordPress installation that are not yet installed. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listDatabaseRemoteConnectionsV1 ~104
Returns the remote-access rules for the specified account: the remote hosts (IPv4/IPv6 addresses, or "%" for any host) allowed to connect to the account databases. Use the domain filter to only return rules for databases assigned to a specific domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Filter remote connections by the domain the database is assigned to. Rules for databases not assigned to any domain are always included. |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listInstalledWordPressPluginsV1 ~105
List plugins installed on a WordPress installation, including their status, available updates and known vulnerabilities. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter installed plugins by category. |
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listInstalledWordPressThemesV1 ~93
List themes installed on a WordPress installation, including their status, available updates and known vulnerabilities. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listJsDeployments ~127
List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| page | integer | — | Page number for pagination (optional) |
| perPage | integer | — | Number of items per page (optional) |
| states | array | — | Filter by deployment states (optional). Valid values: pending, completed, running, failed |
No output schema declared.
No examples provided.
hosting_listNode_jsVulnerabilitiesV1 ~275
Lists known npm package vulnerabilities detected on a Node.js website, enriched with advisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from the most severe to the least severe, then by publish date (newest first). Use the `severities` query parameter to filter. Vulnerabilities with `is_patchable` set to `true` can be auto-fixed via the `Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with updated package versions. Auto-fix is only available for websites deployed from a connected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to `true` are already included in an open patch pull request; while any patch pull request is open, new patch requests for this website are rejected until it is merged or closed. Data comes from periodic dependency scans, so it may lag behind the latest deployment. An empty list means the most recent scan found no vulnerabilities; it does not guarantee the current deployment is vulnerability-free. Available on Business and Cloud Hosting plans.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| severities | array | — | Severities to filter by |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listNodeJSBuildsV1 ~139
Retrieve a paginated list of Node.js build processes for a specific website. Each build represents a single run of the Node.js build pipeline. Use the `states` query parameter to filter results by build state (pending, running, completed, failed). Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| page | integer | — | Page number |
| per_page | integer | — | Number of items per page |
| states | array | — | Build states to filter by |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listOrdersV1 ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_ids | array | — | Filter by specific order IDs |
| page | integer | — | Page number |
| per_page | integer | — | Number of items per page |
| statuses | array | — | Filter by order statuses |
No output schema declared.
No examples provided.
hosting_listSuggestedWordPressPluginsV1 ~66
List curated plugin suggestions grouped by website type. Use the returned `slug` values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | — | Optionally scope suggestions to a specific order. |
No output schema declared.
No examples provided.
hosting_listWebsiteParkedDomainsV1 ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listWebsiteSubdomainsV1 ~67
Retrieve all subdomains created under the selected website. Use this endpoint to inspect subdomain configuration for a specific website, including the parent domain and root directory assigned to each subdomain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_listWebsitesV1 ~152
Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you. Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Filter by domain name (exact match) |
| is_enabled | boolean | — | Filter by enabled status |
| order_id | integer | — | Order ID |
| page | integer | — | Page number |
| per_page | integer | — | Number of items per page |
| username | string | — | Filter by specific username |
No output schema declared.
No examples provided.
hosting_listWordPressInstallationsV1 ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Filter by domain name (exact match) |
| ownership | string | — | Filter by ownership type. Defaults to "owned". Use "all" to include both owned and managed installations. |
| username | string | — | Filter by specific username |
No output schema declared.
No examples provided.
hosting_listWordPressThemesV1 ~78
List WordPress themes available to install. Use the returned `slug` values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/themes/install.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | — | Optionally scope themes to a specific order. |
| search | string | — | Search term to match against theme names. |
No output schema declared.
No examples provided.
hosting_patchNode_jsVulnerabilitiesV1 ~258
Patches the selected Node.js vulnerabilities by updating the affected package versions in `package.json` and opening a GitHub pull request in the connected repository. The customer reviews and merges the pull request; merging triggers the automatic deployment. Auto-fix is only available for websites deployed from a connected GitHub repository. Websites deployed from an archive have no auto-fix path and return a 404. The Hostinger GitHub App needs write access to the repository; without it the request fails with a 403 explaining the missing permission. Only vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable IDs in the selection are skipped; the pull request covers the patchable subset, listed in `patched_vulnerability_ids`. Selections without any patchable vulnerability are rejected with a 422. Only one patch pull request can be open at a time per website; close or merge it before patching again. Available on Business and Cloud Hosting plans.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
| vulnerability_ids | array | yes | List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint. |
No output schema declared.
No examples provided.
hosting_purgeLiteSpeedCacheV1 ~87
Purge the LiteSpeed Cache for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_repairDatabaseV1 ~71
Repairs corrupted database tables asynchronously. Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full database name as returned by the list databases endpoint. |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_resetPHPExtensionsV1 ~58
Resets all PHP extensions of the website to their default state. Use it to recover from extension conflicts or restore the original configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_restartNode_jsApplicationV1 ~126
Restarts the Node.js server process for the website. Does not rebuild or redeploy the application. Use it to apply environment or configuration changes, or to recover a hung application. Only applicable to server-side applications (Express, Next.js, NestJS, etc.). Static front-end apps (React, Vue, Vite) have no persistent server process, so restarting them has no effect. Returns success even when the website has no server process to restart.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_searchWordPressPluginsV1 ~72
Search the WordPress.org plugin directory for plugins available to install. Use the returned `slug` values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | yes | Search term to match against plugin names. Minimum 3 characters. |
No output schema declared.
No examples provided.
hosting_setAIOptionStatusV1 ~122
Enable or disable an AI option for the Hostinger Tools plugin on the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| enable | boolean | yes | Enable (true) or disable (false) the AI option. |
| option | string | yes | AI option name |
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_showAIOptionStatusV1 ~128
Show the current AI option status for the Hostinger Tools plugin on the specified WordPress installation. Filter by `option` to return a single option, or omit it to return all options. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| option | string | — | Filter the status by a single AI option. |
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_showJsDeploymentLogs ~83
Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
| Name | Type | Req | Description |
|---|---|---|---|
| buildUuid | string | yes | UUID of the JavaScript deployment build |
| domain | string | yes | Domain name associated with the hosting account (e.g., example.com) |
| fromLine | integer | — | Line from which to retrieve logs (optional, default 0) |
No output schema declared.
No examples provided.
hosting_showLiteSpeedCacheStatusV1 ~87
Show the LiteSpeed Cache status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_showMaintenanceStatusV1 ~84
Show the maintenance mode status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.
hosting_showMemcachedObjectCacheStatusV1 ~90
Show the Memcached object cache status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the `id` field).
| Name | Type | Req | Description |
|---|---|---|---|
| software | string | yes | WordPress installation (software) identifier |
| username | string | yes | username parameter |
No output schema declared.
No examples provided.