hostinger-api-mcp
Model Context Protocol (MCP) server for Hostinger API.
Quick start: Hosted remote server
If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server:
https://mcp.hostinger.com
Claude Code
claude mcp add --transport http hostinger https://mcp.hostinger.com
This opens a browser window to authorize via OAuth. Once approved, the operations below are reachable through execute in your session.
Codex
codex mcp add hostinger --url https://mcp.hostinger.com
codex mcp login hostinger
login opens the same OAuth flow in your browser.
Other MCP-compatible clients
Add https://mcp.hostinger.com as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears. Refer to your client's docs for how it exposes "add remote MCP server" / "custom connector" settings.
Prerequisites
- Node.js version 24 or higher
If you don't have Node.js installed, you can download it from the official website.
Alternatively, you can use a package manager like Homebrew (for macOS) or Chocolatey (for Windows) to install Node.js.
We recommend using NVM (Node Version Manager) to install and manage installed Node.js versions.
After installing NVM, you can install Node.js with the following command:
nvm install v24
nvm use v24
Installation
To install the MCP server, run one of the following command, depending on your package manager:
npm install -g @hostinger/mcp
yarn global add @hostinger/mcp
pnpm add -g @hostinger/mcp
Update
To update the MCP server to the latest version, use one of the following commands, depending on your package manager:
npm update -g @hostinger/mcp
yarn global upgrade @hostinger/mcp
pnpm update -g @hostinger/mcp
Binaries
This package installs the following MCP server commands:
hostinger-api-mcp โ unified server over every operation (424 total)
hostinger-agency-hosting-mcp โ 43 operations for agency-hosting
hostinger-agent-readiness-mcp โ 4 operations for agent-readiness
hostinger-billing-mcp โ 10 operations for billing
hostinger-dns-mcp โ 9 operations for dns
hostinger-domains-mcp โ 43 operations for domains
hostinger-ecommerce-mcp โ 30 operations for ecommerce
hostinger-gpu-mcp โ 13 operations for gpu
hostinger-horizons-mcp โ 7 operations for horizons
hostinger-hosting-mcp โ 59 operations for hosting
hostinger-mail-mcp โ 39 operations for mail
hostinger-reach-mcp โ 73 operations for reach
hostinger-vps-mcp โ 68 operations for vps
hostinger-wordpress-mcp โ 41 operations for wordpress
Every binary exposes the same three tools; a scoped binary only searches and executes its own group's operations. hostinger-api-mcp remains the backwards-compatible default.
Configuration
The following environment variables can be configured when running the server:
DEBUG: Enable debug logging (true/false) (default: false)
HOSTINGER_API_TOKEN: Your API token, which will be sent in the Authorization header. When set, OAuth is bypassed entirely.
API_TOKEN: Deprecated alias for HOSTINGER_API_TOKEN. Will be removed in a future version โ prefer HOSTINGER_API_TOKEN.
OAUTH_ISSUER: OAuth server base URL (default: https://auth.hostinger.com). Only used when HOSTINGER_API_TOKEN is not set.
Authentication
The server supports two authentication methods:
API Token (recommended for CI/scripts)
Set HOSTINGER_API_TOKEN in the environment (the MCP client's env block). When present it always takes precedence โ no OAuth code runs.
OAuth 2.0 with PKCE (interactive sign-in)
When HOSTINGER_API_TOKEN is not set and the server runs in stdio mode, OAuth 2.0 with PKCE is used automatically on the first authenticated tool call:
- A dynamic OAuth client is registered with the issuer (RFC 7591) โ once per machine.
- A browser window opens to the authorization page.
- After sign-in, the server captures the redirect on a local ephemeral port, exchanges the code for tokens, and stores them.
- Subsequent calls reuse the stored access token; expired tokens are refreshed automatically. If a refresh token is revoked, the browser flow is re-launched.
Credentials are stored at:
- macOS / Linux:
~/.config/hostinger-mcp/credentials.json (mode 0600)
- Windows:
%APPDATA%\hostinger-mcp\credentials.json
Credentials are shared across all Hostinger MCP binaries (hostinger-api-mcp, hostinger-vps-mcp, etc.).
Manual commands:
hostinger-api-mcp --login
hostinger-api-mcp --logout
HTTP transport note: OAuth sign-in is not supported in --http mode. Set HOSTINGER_API_TOKEN before using --http.
Usage
JSON configuration for Claude, Cursor, etc.
Register Node and the server script by absolute path, never npx or a bare node/hostinger-api-mcp: tools start the server in your project, where npx puts the project's node_modules/.bin first on PATH, a version manager (asdf, mise) runs whatever Node the project's .tool-versions names, and Windows looks a bare name up in the project folder first. Any of these lets a cloned repository run its own code with your Hostinger credentials. After the global install, node -p process.execPath prints the Node path and npm root -g the folder that holds @hostinger/mcp. Run both from your home folder.
{
"mcpServers": {
"hostinger-api": {
"command": "/absolute/path/to/node",
"args": ["/absolute/path/to/global/node_modules/@hostinger/mcp/src/servers/all.js"],
"env": {
"DEBUG": "false",
"HOSTINGER_API_TOKEN": "YOUR API TOKEN"
}
}
}
}
Transport Options
The MCP server supports two transport modes:
Standard I/O Transport
The server can use standard input / output (stdio) transport (default). This provides local streaming:
Streamable HTTP Transport
The server can use HTTP streaming transport. This provides bidirectional streaming over HTTP:
hostinger-api-mcp --http
hostinger-api-mcp --http --host 0.0.0.0 --port 8150
Command Line Options
Options:
--http Use HTTP streaming transport (requires HOSTINGER_API_TOKEN env var)
--stdio Use Server-Sent Events transport (default)
--host {host} Hostname or IP address to listen on (default: 127.0.0.1)
--port {port} Port to bind to (default: 8100)
--login Run OAuth sign-in flow and exit
--logout Revoke stored OAuth credentials and exit
--help Show help message
This server implements the Model Context Protocol (MCP) and can be used with any MCP-compatible consumer.
Example of connecting to this server using HTTP streaming transport:
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const transport = new StreamableHTTPClientTransport({
url: "http://localhost:8100/",
headers: {
"Authorization": `Bearer ${process.env.HOSTINGER_API_TOKEN}`
}
});
const client = new Client({
name: "my-client",
version: "1.0.0"
}, {
capabilities: {}
});
await client.connect(transport);
const { tools } = await client.listTools();
console.log("Available tools:", tools);
const result = await client.callTool({
name: "execute",
arguments: { operation: "billing_catalog_list", params: { category: "DOMAIN" } }
});
console.log("Tool result:", result);
Every server exposes three tools:
search โ find operations by keyword; returns each match with its inputSchema.
execute โ run one operation: { "operation": "<name>", "params": { ... } }.
multi-execute โ run up to 20 operations in order, stopping at the first failure. A params value that is exactly "$steps.<i>.<path>" is replaced by that value from an earlier step's result.
Operations
The operations search offers, by binary:
Operations that newer tools replace are hidden from search, and not documented, in every binary that also offers the replacing tool. Some keep working through execute until they are removed. Others only run inside the tool that replaced them: execute refuses them and names that tool.
hostinger-agency-hosting-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
agency-hosting_deploy-node-static-website
Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone โ always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully โ there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally โ do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For plain PHP applications that should be extracted as-is, use agency-hosting_deploy-php-application instead. The website UID is automatically resolved from the domain.
- Method:
custom
- Path:
custom
agency-hosting_deploy-php-application
Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone โ always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully โ there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally โ do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For node-static websites that require a build step, use agency-hosting_deploy-node-static-website instead. The website UID is automatically resolved from the domain.
- Method:
custom
- Path:
custom
agency-hosting_datacenters_list
Lists the datacenters available for provisioning a new website on the given Agency Plan
hosting order.
Each datacenter includes a pinger_url you can ping from the client to measure round-trip
latency; comparing the results across datacenters lets you pick the nearest one (lowest
ping) before choosing its code as the datacenter_code when creating a website setup.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders/{order_id}/datacenters
agency-hosting_domains_change-website
Changes the primary domain for an Agency Plan website.
Provide the current domain in the path and the new domain in the request body.
Set domain to null to revert to the temporary domain.
- Method:
PUT
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{from_domain}
agency-hosting_domains_link-to-website
Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains
agency-hosting_domains_list
Returns a paginated list of domains associated with Agency Plan websites accessible to the authenticated client.
Use the website_uuids filter to narrow results to specific websites.
- Method:
GET
- Path:
/api/agency-hosting/v1/domains
agency-hosting_domains_unlink-from-website
Unlinks a domain from the specified Agency Plan website.
The website stops serving traffic on this domain immediately.
Website files and database are preserved, and any other linked domains remain accessible.
If this is the only domain on the website, unlinking leaves the website without an accessible domain.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}
agency-hosting_files_generate-upload-url
Generate a file browser upload URL with authentication credentials for uploading files
to an Agency Plan website's file storage.
Returns url, auth_key and rest_auth_key. Use these to upload a file to the
website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send
X-Auth: {auth_key} and X-Auth-Rest: {rest_auth_key} headers on every request below.
- Create the upload:
POST to {url}/{relative_file_path}?override=true with headers
upload-length: {file size in bytes} and upload-offset: 0. Expect 201 Created.
- Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or
PATCH requests with an upload-offset header tracking progress) until complete.
relative_file_path is the destination path inside the website's file storage, e.g.
app.zip.
Instead of a TUS client, plain curl also works:
FILE=app.zip
SIZE=$(stat -f%z "$FILE") # stat -c%s on Linux
curl -i -X POST "{url}/${FILE}?override=true" \
-H "X-Auth: {auth_key}" \
-H "X-Auth-Rest: {rest_auth_key}" \
-H "Tus-Resumable: 1.0.0" \
-H "Upload-Length: ${SIZE}" \
-H "Upload-Offset: 0"
# -> 201 Created
curl -i -X PATCH "{url}/${FILE}?override=true" \
-H "X-Auth: {auth_key}" \
-H "X-Auth-Rest: {rest_auth_key}" \
-H "Tus-Resumable: 1.0.0" \
-H "Content-Type: application/offset+octet-stream" \
-H "Upload-Offset: 0" \
--data-binary "@${FILE}"
# -> 204 No Content, Upload-Offset response header equals SIZE when done
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/files/upload-urls
agency-hosting_files_import-website-from-archive
Imports an Agency Plan website from an already-uploaded archive.
Upload the archive to the website's root directory via file browser first, then provide its
filename in this request. Website contents are overwritten by the archive contents. Supported
archive types: .zip, .tar, .tar.gz, .tgz.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/files/import-archive
agency-hosting_metrics_list-plan-order-disk-usage
Returns aggregated disk and inode usage for the Agency Plan order over the
selected time frame, plus the plan quotas. Figures cover the whole order
account. Values may be up to one hour stale. CPU, memory, and process usage
are on the resource-usage-metrics endpoint.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders/{order_id}/disk-usage-metrics
agency-hosting_orders_list
Returns a paginated list of Agency Plan orders accessible to the authenticated client.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders
agency-hosting_metrics_list-order-resource-usage
Returns aggregated CPU, memory, and process usage for the Agency Plan order
over the selected time frame, plus the plan quotas and a per-website
breakdown. Each website is identified by uid. Suspended and deleted websites
are excluded from both the order totals and the per-website breakdown.
Values may be up to one hour stale. Disk and inode usage are on the
disk-usage-metrics endpoint.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders/{order_id}/resource-usage-metrics
agency-hosting_php_list-extensions-for-website
Lists every PHP extension available to an Agency Plan website and whether it is currently enabled.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions
agency-hosting_php_replace-website-extensions
Replaces the set of PHP extensions enabled on an Agency Plan website with the ones provided. Any toggleable extension not in the request is disabled, so call the extensions endpoint first and send the full desired set. Extensions compiled into PHP, reported with the "built-in" state, are always active and are unaffected.
- Method:
PUT
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions
agency-hosting_php_list-options-for-website
Lists the php.ini directives that can be configured for an Agency Plan website, each with its default, the value currently in effect, and the values it accepts.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/options
agency-hosting_php_replace-website-options
Replaces the custom php.ini values on an Agency Plan website with the ones provided. Any option not in the request is reset to its default, so call the options endpoint first and send the full desired set. Sending an empty array resets every option to its default.
- Method:
PUT
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/options
agency-hosting_php_list-versions-for-order
Lists the PHP versions available to websites created under an Agency Plan order, determined by the server the order is hosted on. Use this before creating a website; for a website that already exists, call the website-scoped versions endpoint instead.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders/{order_id}/websites/php-settings/versions
agency-hosting_php_list-versions-for-website
Lists the PHP versions an Agency Plan website can be switched to. The version the website is currently running is returned as settings.php.version by the website details endpoint.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/versions
agency-hosting_php_update-website-version
Switches an Agency Plan website to a different PHP version. Call the available versions endpoint first to see which versions can be selected. The website restarts on the new version, so requests served during the switch may fail and code that is incompatible with the target version will break.
- Method:
PATCH
- Path:
/api/agency-hosting/v1/websites/{website_uid}/php-settings/version
agency-hosting_website-setups_create
Provisions a new website on one of your Agency Plan hosting orders.
Choose the datacenter, stack (flavor), and PHP version for the site. Optionally attach
your own domain โ omit it, set it to null, or leave it unavailable and a free
*.hostingersite.com subdomain is generated instead โ and/or install WordPress by
supplying the wordpress details (admin account, site title, and language).
Common setups:
- Plain PHP site:
flavor set to php-fpm, with settings.php.version; omit
wordpress and type.
- WordPress site:
flavor set to the desired WordPress version (e.g. wp-7.0), plus
the wordpress block (admin account, title, language).
- Static/Node.js frontend app:
flavor set to php-fpm and type set to
node-static.
Provisioning runs in the background, so the response returns immediately with a setup UUID
that identifies the job. The new website becomes reachable once provisioning finishes.
- Method:
POST
- Path:
/api/agency-hosting/v1/orders/{order_id}/websites/setups
agency-hosting_website-setups_status
Returns the current status of an Agency Plan website setup started via the setups
endpoint.
Poll this endpoint using the setup_uuid returned from the provisioning request until
status becomes completed, at which point website_uid identifies the new website.
- Method:
GET
- Path:
/api/agency-hosting/v1/orders/{order_id}/websites/setups/{setup_uuid}
agency-hosting_ssl_reinstall-website
Replaces the Let's Encrypt certificate of the domain: the current platform certificate, when
one is recorded, is revoked and removed, then a new setup starts in the background. Returns at
once; Get website SSL status reports installing while it runs, then active or failed.
Returns 422 for free subdomains, when a certificate process is recorded for the domain (a
failed setup counts until it is cleaned up), or when the domain hit its limit of three setups
per seven days. Returns 429 when the same domain was requested less than a minute ago, and 403
when the website is suspended or locked, and 404 when the website or the domain does not exist.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/reinstall
agency-hosting_ssl_install-website
Starts a Let's Encrypt certificate setup for the domain and returns at once; the setup runs in
the background. Get website SSL status reports installing while it runs, then active or
failed; the ssl_setup entry of List website processes shows the same progress.
Returns 422 when the domain already has a platform certificate that is not expired, when a
certificate process is recorded for the domain (a failed setup counts until it is cleaned up),
or when the domain hit its limit of three setups per seven days. Returns 429 when the same
domain was requested less than a minute ago, 403 when the website is suspended or locked, and
404 when the website or the domain does not exist.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/setup
agency-hosting_ssl_website-status
Returns the SSL state of one domain of an Agency Plan website: the certificate status,
whether the certificate was uploaded by the customer, and when it stops being valid.
installing means a certificate setup is running or retrying; the ssl_setup entry of
List website processes shows the same progress. active means a valid certificate is in
place: uploaded by the customer, issued by the platform, or a lifetime certificate bought for
the domain. failed means the last setup gave up and no valid certificate is in place.
expired means the certificate has run out. not_installed means the domain has no
certificate and no setup process. Returns 404 when the website or the domain does not exist.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/status
agency-hosting_ssl_uninstall-website
Removes the platform-issued Let's Encrypt certificate of the domain: the certificate is revoked
and deleted before the response, so the domain is no longer served with a platform certificate
until a new setup completes. Also succeeds when the domain has no platform certificate to
remove. Uploaded (custom) certificates are not affected.
Returns 422 when a certificate process is recorded for the domain (a failed setup counts until
it is cleaned up), 429 when the same domain was requested less than a minute ago, and 403 when
the website is suspended or locked, and 404 when the website or the domain does not exist.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl
agency-hosting_websites_build-nodejs-assets
Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive.
Upload the archive to file browser first, then provide its relative path from document root in this request.
Website contents are overwritten by the build result, which is deployed to public_html.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/build-assets
agency-hosting_cache_clear-website
Clears cache for all domains associated with an Agency Plan website, including its preview domain.
This operation clears all cache types for the website.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/cache
agency-hosting_cron-jobs_list-website
Returns a paginated list of cron jobs configured for an Agency Plan website.
Each entry includes the schedule expression and the command executed on that schedule.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/cron-jobs
agency-hosting_cron-jobs_create-website
Creates a cron job for an Agency Plan website from a schedule expression and a command.
Returns the created cron job, including its uuid, which is required to delete the cron job.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/cron-jobs
agency-hosting_cron-jobs_delete-website
Permanently deletes the cron job identified by its uuid from an Agency Plan website.
The operation is idempotent: deleting a cron job that does not exist succeeds without error.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/cron-jobs/{uuid}
agency-hosting_databases_list-website
Returns a paginated list of MySQL databases created for an Agency Plan website.
Each entry includes the database's non-system users.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/databases
agency-hosting_databases_create-website
Creates a MySQL database with a dedicated user for an Agency Plan website.
The database name, username, and password must all be provided by the caller.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/databases
agency-hosting_databases_delete-website
Permanently deletes a MySQL database and all its data from an Agency Plan website, including its users.
The operation is idempotent: deleting a database that does not exist succeeds without error.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}
agency-hosting_databases_create-website-user
Creates a user for an existing database on an Agency Plan website.
Each database supports a single non-system user; creating a user for a database that already has one fails.
- Method:
POST
- Path:
/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users
agency-hosting_databases_delete-website-user
Permanently deletes a database user from an Agency Plan website database, revoking all access it had.
The operation is idempotent: deleting a user that does not exist succeeds without error.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users/{database_user_name}
agency-hosting_websites_get
Retrieves detailed information about a specific Agency Plan website, including configuration,
status, metadata, hosting plan details, and resource quotas.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}
agency-hosting_websites_delete
Permanently deletes an Agency Plan website. Deletion is processed asynchronously: the
website is immediately transitioned to a deleting state and the underlying server
resources are removed in the background.
- Method:
DELETE
- Path:
/api/agency-hosting/v1/websites/{website_uid}
agency-hosting_websites_list-plan
Retrieve a paginated list of Agency Plan websites (H5G, Builder, and Horizons) 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.
The response shape differs per platform โ see the platform field on each item.
Use website_types to list only websites of a given detected type, e.g. only
WordPress websites (website_types=wordpress) or only Node.js websites
(website_types=nodejs). Combine with order_ids, states, or domain for more
targeted results.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites
agency-hosting_websites_list-processes
Lists active and recently completed asynchronous processes for an Agency Plan website.
Each process has a unique ID (for tracking), a type, and a status (running, completed, failed).
Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/processes
agency-hosting_wordpress_change-version
Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation.
- Method:
PATCH
- Path:
/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/version
agency-hosting_wordpress_settings
Returns the current WordPress settings for an Agency Plan website: installed core version,
LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings
agency-hosting_wordpress_list-versions
Lists the WordPress core versions available for installation on an Agency Plan website.
- Method:
GET
- Path:
/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/versions
hostinger-agent-readiness-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
agent-readiness_checks_list
List every check an agent readiness scan runs, with its name, category and weight.\n
Use it to show the human-readable name of each check_id in a scan's results.
- Method:
GET
- Path:
/api/agent-readiness/v1/checks
agent-readiness_scans_run
Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually pending
with no results yet. To get the results, poll the Get agent readiness scan operation with the same
domain every few seconds until its status is completed or failed. The scan itself is limited to 60 seconds,
plus any time it waits in the queue. A failed scan is not retried; run this operation again.\n
Starting a scan for a domain that already has a pending scan from the last 5 minutes
returns that scan instead of starting a new one.
- Method:
POST
- Path:
/api/agent-readiness/v1/scans
agent-readiness_scans_get
Get the latest agent readiness scan of a website.\n
Scans started with the Run agent readiness scan operation are asynchronous. While the status is
pending, the result fields are null; wait a few seconds and call this operation again until the status is
completed or failed. A failed scan is not retried; run the scan again.\n
A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
check with the evidence found and how to fix it. Check names are listed by the List checks operation.\n
Returns 404 when the domain has never been scanned; use the Run agent readiness scan operation first.
- Method:
GET
- Path:
/api/agent-readiness/v1/scans/{domain}
hostinger-billing-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
billing_catalog_list
Retrieve catalog items available for order.
Prices in catalog items is displayed as cents (without floating point),
e.g: float 17.99 is displayed as integer 1799.
Use this endpoint to view available services and pricing before placing orders.
- Method:
GET
- Path:
/api/billing/v1/catalog
billing_orders_create-purchase
Create a purchase order for any Hostinger product.
This unified endpoint places an order for one or more catalog items and
works across all Hostinger products, leveraging the existing billing
infrastructure. Use the catalog endpoint to look
up the item_id values available for purchase.
If no payment method is provided, your default payment method will be used automatically.
If the response is 202 Accepted, the payment is still being processed and the order will
complete asynchronously once the payment is confirmed.
This endpoint only places the order. Product-specific provisioning
(e.g. VPS setup or domain registration) is not performed here โ once the
order completes, use the relevant product endpoints or
hPanel to finalize setup.
Use this endpoint to purchase any product available in the catalog.
- Method:
POST
- Path:
/api/billing/v1/orders
billing_payment-methods_set-default
Set the default payment method for your account.
Use this endpoint to configure the primary payment method for future orders.
- Method:
POST
- Path:
/api/billing/v1/payment-methods/{paymentMethodId}
billing_payment-methods_delete
Delete a payment method from your account.
Use this endpoint to remove unused payment methods from user accounts.
- Method:
DELETE
- Path:
/api/billing/v1/payment-methods/{paymentMethodId}
billing_payment-methods_list
Retrieve available payment methods that can be used for placing new orders.
If you want to add new payment method,
please use hPanel.
Use this endpoint to view available payment options before creating orders.
- Method:
GET
- Path:
/api/billing/v1/payment-methods
billing_subscriptions_list
Retrieve a list of all subscriptions associated with your account.
Use this endpoint to monitor active services and billing status.
- Method:
GET
- Path:
/api/billing/v1/subscriptions
billing_subscriptions_disable-auto-renewal
Disable auto-renewal for a subscription.
Use this endpoint when disable auto-renewal for a subscription.
- Method:
DELETE
- Path:
/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/disable
billing_subscriptions_enable-auto-renewal
Enable auto-renewal for a subscription.
Use this endpoint when enable auto-renewal for a subscription.
- Method:
PATCH
- Path:
/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable
billing_subscriptions_renew
Create a renewal order for an existing Hostinger subscription.
This endpoint places a renewal order for a single subscription, leveraging
the existing billing infrastructure. Use the
subscriptions endpoint to look up the
subscriptionId values available for renewal.
If no payment method is provided, your default payment method will be used automatically.
If the response is 202 Accepted, the payment is still being processed and the renewal will
complete asynchronously once the payment is confirmed.
Use this endpoint to renew any subscription available in your account.
- Method:
POST
- Path:
/api/billing/v1/subscriptions/{subscriptionId}/renew
hostinger-dns-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
dns_snapshots_get
Retrieve particular DNS snapshot with contents of DNS zone records.
Use this endpoint to view historical DNS configurations for domains.
- Method:
GET
- Path:
/api/dns/v1/snapshots/{domain}/{snapshotId}
dns_snapshots_list
Retrieve DNS snapshots for a domain.
Use this endpoint to view available DNS backup points for restoration.
- Method:
GET
- Path:
/api/dns/v1/snapshots/{domain}
dns_snapshots_restore
Restore DNS zone to the selected snapshot.
Use this endpoint to revert domain DNS to a previous configuration.
- Method:
POST
- Path:
/api/dns/v1/snapshots/{domain}/{snapshotId}/restore
dns_records_list
Retrieve DNS zone records for a specific domain.
Use this endpoint to view current DNS configuration for domain management.
- Method:
GET
- Path:
/api/dns/v1/zones/{domain}
dns_records_update
Update DNS records for the selected domain.
Using overwrite = true will replace existing records with the provided ones.
Otherwise existing records will be updated and new records will be added.
Use this endpoint to modify domain DNS configuration.
- Method:
PUT
- Path:
/api/dns/v1/zones/{domain}
dns_records_delete
Delete DNS records for the selected domain.
To filter which records to delete, add the name of the record and type to the filter.
Multiple filters can be provided with single request.
If you have multiple records with the same name and type, and you want to delete only part of them,
refer to the Update zone records endpoint.
Use this endpoint to remove specific DNS records from domains.
- Method:
DELETE
- Path:
/api/dns/v1/zones/{domain}
dns_records_reset
Reset DNS zone to the default records.
Use this endpoint to restore domain DNS to original configuration.
- Method:
POST
- Path:
/api/dns/v1/zones/{domain}/reset
dns_records_validate
Validate DNS records prior to update for the selected domain.
If the validation is successful, the response will contain 200 Success code.
If there is validation error, the response will fail with 422 Validation error code.
Use this endpoint to verify DNS record validity before applying changes.
- Method:
POST
- Path:
/api/dns/v1/zones/{domain}/validate
hostinger-domains-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
domains_verifications_direct
Retrieve a list of pending and completed domain verifications.
- Method:
GET
- Path:
/api/v2/direct/verifications/active
domains_availability_suggest-names-from-description
Suggest available domain names based on a free-text description of your project.
Suggestions are generated by an AI model, so they differ between calls.
Endpoint has rate limit of 90 requests per minute.
Use this endpoint to find a domain name when you only know what the website is about.
- Method:
POST
- Path:
/api/domains/v1/availability/alternatives-from-description
domains_availability_suggest-names-from
Suggest available domain names based on a domain name you already have in mind.
Suggestions are generated by an AI model, so they differ between calls.
Endpoint has rate limit of 90 requests per minute.
Use this endpoint when the domain you wanted is taken and you need close alternatives.
- Method:
POST
- Path:
/api/domains/v1/availability/alternatives-from-domain
domains_availability_check
Check availability of domain names across multiple TLDs.
Multiple TLDs can be checked at once.
If you want alternative domains with response, provide only one TLD and set with_alternatives to true.
TLDs should be provided without leading dot (e.g. com, net, org).
Premium domains are included: an available premium domain has is_available and is_premium set to true.
Endpoint has rate limit of 90 requests per minute.
Use this endpoint to verify domain availability before purchase.
- Method:
POST
- Path:
/api/domains/v1/availability
domains_forwarding_get
Retrieve domain forwarding data.
Returns 404 when the domain has no forwarding.
Use this endpoint to view current redirect configuration for domains.
- Method:
GET
- Path:
/api/domains/v1/forwarding/{domain}
domains_forwarding_update
Update domain forwarding configuration.
Updating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
current nameservers are returned by the domain details endpoint; confirm with the
user before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
propagate.
Use this endpoint to modify existing redirect configuration for domains.
- Method:
PUT
- Path:
/api/domains/v1/forwarding/{domain}
domains_forwarding_delete
Delete domain forwarding data.
Use this endpoint to remove redirect configuration from domains.
- Method:
DELETE
- Path:
/api/domains/v1/forwarding/{domain}
domains_forwarding_create
Create domain forwarding configuration.
Creating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
current nameservers are returned by the domain details endpoint; confirm with the
user before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
propagate.
Use this endpoint to set up domain redirects to other URLs.
- Method:
POST
- Path:
/api/domains/v1/forwarding
domains_whois_pending-irtp-verification
Retrieve a pending IRTP verification for a domain.
Both the old and new registrant must confirm it before the WHOIS change takes effect.
Returns 404 when the domain has no pending IRTP verification.
Use this endpoint to check the status of a WHOIS change awaiting registrant confirmation.
- Method:
GET
- Path:
/api/domains/v1/irtp/{domain}
domains_whois_cancel-pending-irtp-verification
Cancel a pending IRTP verification.
Use this endpoint to back out of a WHOIS change that is stuck waiting on registrant confirmation,
for example when the confirmation email cannot be received, without waiting out the 5-day expiry.
- Method:
DELETE
- Path:
/api/domains/v1/irtp/{domain}
domains_move_incoming
Retrieve the incoming move for a specified domain.
Returns 404 when no account is moving this domain to you.
Use this endpoint to check whether a domain addressed to you is still waiting to be accepted.
- Method:
GET
- Path:
/api/domains/v1/move/incoming/{domain}
domains_move_accept-incoming
Accept an incoming move for a specified domain.
The provided WHOIS profiles become the contacts of the domain, so they must belong
to your account and satisfy the requirements of the TLD. Only the contact types the
domain actually uses are applied, but all four profile IDs have to be provided.
The move has to still be waiting for your decision, already accepted moves
cannot be accepted again.
Accepting does not complete the move. A confirmation email is sent to the email address of
the new owner contact, and the domain changes hands only after the change is confirmed from it.
Until then the move stays in the activating status, which can be followed with the
incoming move endpoint.
Use this endpoint to take ownership of a domain offered to you.
- Method:
PUT
- Path:
/api/domains/v1/move/incoming/{domain}
domains_move_reject-incoming
Reject an incoming move for a specified domain.
The domain stays in the account which initiated the move.
Moves you have already accepted cannot be rejected anymore.
Use this endpoint to decline a domain you do not want to take over.
- Method:
DELETE
- Path:
/api/domains/v1/move/incoming/{domain}
domains_move_incoming-list
Retrieve all domains other Hostinger accounts are moving to your account.
Moves of every status are returned, including the ones which already completed.
Use this endpoint to find domains waiting for you to accept them.
- Method:
GET
- Path:
/api/domains/v1/move/incoming
domains_move_outgoing
Retrieve the outgoing move for a specified domain.
Returns 404 when the domain has no move in progress.
Use this endpoint to track the status of a move you have initiated for a single domain.
- Method:
GET
- Path:
/api/domains/v1/move/outgoing/{domain}
domains_move_start-outgoing
Initiate a move of a specified domain to another Hostinger account.
The receiving account has to already exist and accept the move before the domain changes hands.
The domain must be active. The subscription it belongs to is resolved automatically,
and the request is rejected with a 404 status code when the domain has no domain
subscription of its own.
The move is also refused unless the domain:
- was registered at least 4 days ago
- does not expire within the next 10 days
- has an extension that supports moves
- has no move already in progress
- was not moved in the last 10 days
- is not a premium domain
- is not still processing a recent renewal
A move refused for one of these rules is rejected with a 404 status code and error code 2048,
with a message naming the rule. The receiving account is checked first, and when it cannot
be used the message stays generic.
Domains protected by premium protection require an additional verification step,
such requests are rejected with a 428 status code.
Use this endpoint to hand a domain over to another Hostinger user.
- Method:
POST
- Path:
/api/domains/v1/move/outgoing/{domain}
domains_move_cancel-outgoing
Cancel an outgoing move for a specified domain.
The move can only be cancelled while the receiving account has not accepted it yet.
The domain stays in your account.
Use this endpoint to withdraw a move you no longer want to complete.
- Method:
DELETE
- Path:
/api/domains/v1/move/outgoing/{domain}
domains_move_outgoing-list
Retrieve all domains you are moving to other Hostinger accounts.
Only moves which have not completed yet are returned.
Use this endpoint to track moves you have initiated and the accounts they are addressed to.
- Method:
GET
- Path:
/api/domains/v1/move/outgoing
domains_portfolio_authorization-code
Retrieve the authorization (EPP) code for a specified domain so it can be transferred
away from Hostinger to another registrar.
Requesting a new code invalidates any code retrieved previously.
Use this endpoint to obtain the code required to transfer a domain to another registrar.
- Method:
GET
- Path:
/api/domains/v1/portfolio/{domain}/auth-code
domains_portfolio_claim-free
Claim a free domain available on your account and register it.
Unlike purchasing a domain, this consumes a free domain you already have,
so no payment method is required.
A free domain and a free domain transfer from the same plan are alternatives:
claiming the free domain removes the plan's free domain transfer
(type: free_domain_transfer). Before making request, confirm with the user which
of the two they want. Right after a claim, the removed free domain transfer may
still appear in the domain list endpoint for a short
time; do not claim it.
A successful response means the domain is registered. If registration fails, login to
hPanel and check domain registration status.
If no WHOIS information is provided, default contact information for that TLD will be used.
Before making request, ensure WHOIS information for desired TLD exists in your account.
Some TLDs require additional_details to be provided and these will be validated before claiming.
Requests which cannot be fulfilled are rejected with an error code in the response body,
for example 2037 when no free domain is available.
Use this endpoint to register a domain using a free domain from your account.
- Method:
POST
- Path:
/api/domains/v1/portfolio/claim
domains_portfolio_enable-lock
Enable domain lock for the domain.
When domain lock is enabled,
the domain cannot be transferred to another registrar without first disabling the lock.
Use this endpoint to secure domains against unauthorized transfers.
- Method:
PUT
- Path:
/api/domains/v1/portfolio/{domain}/domain-lock
domains_portfolio_disable-lock
Disable domain lock for the domain.
Domain lock needs to be disabled before transferring the domain to another registrar.
Use this endpoint to prepare domains for transfer to other registrars.
- Method:
DELETE
- Path:
/api/domains/v1/portfolio/{domain}/domain-lock
domains_portfolio_get
Retrieve detailed information for specified domain.
A domain is found here only once it is registered. Until then, Get domain list shows it, and
its verification field says what registration waits for when the domain is held for
verification.
After registration, the registry may require the owner contact to be verified by email, phone
number or contact name before a deadline, after which the domain is suspended. The
contact_verification field shows what needs verifying, its state and the deadline.
Use this endpoint to view comprehensive domain configuration and status.
- Method:
GET
- Path:
/api/domains/v1/portfolio/{domain}
domains_portfolio_list
Retrieve all domains associated with your account.
A plan can include both a free domain (type: free_domain) and a free domain
transfer (type: free_domain_transfer). They are alternatives: claiming one
removes the other, which may still be listed for a short time after the claim.
A domain held for verification before it is registered has status: pending_verification,
and its verification field says what registration waits for: a manual review, an SMS code,
or owner contact verification.
Use this endpoint to view user's domain portfolio.
- Method:
GET
- Path:
/api/domains/v1/portfolio
domains_portfolio_purchase
Purchase and register a new domain name.
If registration fails, login to hPanel and check domain registration status.
If no payment method is provided, your default payment method will be used automatically.
If the response is 202 Accepted, the payment is still being processed and the domain was
not registered. Once the order completes, register the domain from
hPanel.
If no WHOIS information is provided, default contact information for that TLD will be used.
Before making request, ensure WHOIS information for desired TLD exists in your account.
Some TLDs require additional_details to be provided and these will be validated before completing purchase.
Use this endpoint to register new domains for users.
- Method:
POST
- Path:
/api/domains/v1/portfolio
domains_portfolio_enable-privacy-protection
Enable privacy protection for the domain.
When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database.
Use this endpoint to protect domain owner's personal information from public view.
- Method:
PUT
- Path:
/api/domains/v1/portfolio/{domain}/privacy-protection
domains_portfolio_disable-privacy-protection
Disable privacy protection for the domain.
When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database.
Use this endpoint to make domain owner's information publicly visible.
- Method:
DELETE
- Path:
/api/domains/v1/portfolio/{domain}/privacy-protection
domains_portfolio_renewal-information
Retrieve renewal information for a specified domain, including its status, current
expiration date, whether it can be renewed, whether it is in its grace or redemption period,
and when each of those periods ends.
Use this endpoint to build renewal automation and expiry monitoring for a single domain.
- Method:
GET
- Path:
/api/domains/v1/portfolio/{domain}/renewal
domains_portfolio_complete-setup
Register a domain you have already paid for but which has not been set up yet.
Use this endpoint when an order completed without registering the domain, for example when
Purchase new domain returned 202 Accepted and the domain was added to your account without
being registered, or when an earlier setup attempt failed. No new order is placed and no payment
is taken: the subscription you already own is used, for the period you already paid for.
A domain is left awaiting setup when the details needed to register it were missing or invalid
as the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.
Complete the missing information, then call this endpoint. If the order itself has not completed
yet, the domain is not on your account, wait until it appears in Get domain list.
If domain_contacts is omitted, the default WHOIS profile of that TLD is used for all four
roles. The profile must exist and be complete for the TLD, an incomplete profile is the most
common reason a domain is left awaiting setup. Create one with Create WHOIS profile.
Some TLDs require additional_details. These are validated before setup, so a missing or
invalid value is rejected without any registration being attempted.
The domain is set up with the default nameservers and with privacy protection. Use
Update domain nameservers and Disable privacy protection afterwards to change either.
A successful response means the setup request was accepted, not that the domain is already
registered. Poll Get domain list for the outcome, the domain appears in Get domain details
only once it is registered. When the domain is held for verification, its verification field
in Get domain list says what registration waits for.
Use this endpoint to finish registering a domain that is awaiting setup on your account.
- Method:
POST
- Path:
/api/domains/v1/portfolio/{domain}/setup
domains_portfolio_update-nameservers
Set nameservers for a specified domain.
Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.
Use this endpoint to configure custom DNS hosting for domains.
- Method:
PUT
- Path:
/api/domains/v1/portfolio/{domain}/nameservers
domains_transfer_claim-free
Claim a free domain transfer available on your account and start the transfer.
Unlike purchasing a transfer, this consumes a free domain transfer you already have,
so no payment method is required.
A free domain and a free domain transfer from the same plan are alternatives:
claiming the free domain transfer removes the plan's free domain
(type: free_domain). Before making request, confirm with the user which of the
two they want. Right after a claim, the removed free domain may still appear in
the domain list endpoint for a short time; do not claim it.
Before making request, unlock the domain at the current registrar and, if its TLD uses one,
get its authorization code. The transfer is validated first, so domains which cannot be
transferred, or are missing a required authorization code, are rejected before the free
domain transfer is consumed.
A successful response means the transfer has been started. Completion depends on the current
registrar and can be followed with the transfer list endpoint.
If no WHOIS information is provided, default contact information for that TLD will be used.
Before making request, ensure WHOIS information for desired TLD exists in your account.
Requests which cannot be fulfilled are rejected with an error code in the response body.
Use this endpoint to transfer a domain using a free domain transfer from your account.
- Method:
POST
- Path:
/api/domains/v1/transfers/claim
domains_transfer_get
Retrieve the transfer for a specified domain.
Use this endpoint to track an incoming or outgoing registrar transfer and its status.
- Method:
GET
- Path:
/api/domains/v1/transfers/{domain}
domains_transfer_list
Retrieve all domain transfers in your portfolio.
Use this endpoint to monitor incoming and outgoing registrar transfers across your domains.
- Method:
GET
- Path:
/api/domains/v1/transfers
domains_transfer_start
Transfer a domain from another registrar to your account.
The transfer runs on a domain transfer service you have already purchased.
Before making request, unlock the domain at the current registrar and, if its TLD uses one,
get its authorization code.
A successful response means the transfer has been started. Completion depends on the current
registrar and can be followed with the transfer list endpoint.
If no WHOIS information is provided, default contact information for that TLD will be used.
Before making request, ensure WHOIS information for desired TLD exists in your account.
Use this endpoint to bring domains registered elsewhere into your account.
- Method:
POST
- Path:
/api/domains/v1/transfers
domains_whois_change-for
Change WHOIS contact profile for a domain.
Repoints the given contact roles to a new WHOIS profile and submits the change to the registry.
The profile currently assigned to those roles is resolved automatically;
the request fails if the given roles are not all on the same profile today.
Changing transfer sensitive fields on the owner contact starts an IRTP verification.
The change is processed asynchronously.
Use this endpoint to move a registered domain onto different contact information.
- Method:
PUT
- Path:
/api/domains/v1/whois/change
domains_whois_set-as-default
Set WHOIS contact profile as default.
The default profile is pre-selected for the TLD it belongs to when registering new domains.
Use this endpoint to avoid picking contact information for every registration.
- Method:
PUT
- Path:
/api/domains/v1/whois/default/{whoisId}
domains_whois_unset-default
Unset WHOIS contact profile as default.
The profile itself is kept, it is only no longer pre-selected for its TLD.
Use this endpoint to stop reusing contact information for new registrations.
- Method:
DELETE
- Path:
/api/domains/v1/whois/default/{whoisId}
domains_whois_get
Retrieve a WHOIS contact profile.
Use this endpoint to view domain registration contact information.
- Method:
GET
- Path:
/api/domains/v1/whois/{whoisId}
domains_whois_delete
Delete WHOIS contact profile.
Use this endpoint to remove unused contact profiles from account.
- Method:
DELETE
- Path:
/api/domains/v1/whois/{whoisId}
domains_whois_list
Retrieve WHOIS contact profiles.
Use this endpoint to view available contact profiles for domain registration.
- Method:
GET
- Path:
/api/domains/v1/whois
domains_whois_create
Create WHOIS contact profile.
Use this endpoint to add new contact information for domain registration.
The keys required in whois_details and tld_details depend on the TLD, country and entity type, and can be
country-specific: for Lithuania, for example, state_lt and zip_lt are required instead of state and
zip. A 422 response lists every required key that is missing or has an invalid value under
errors.whois_details, and under errors.tld_details when tld_details is sent. Each error states the
key's constraint and, where the key takes a fixed set of values, the allowed values, so all of them can be
corrected in one retry.
- Method:
POST
- Path:
/api/domains/v1/whois
domains_whois_usage
Retrieve domain list where provided WHOIS contact profile is used.
Use this endpoint to view which domains use specific contact profiles.
- Method:
GET
- Path:
/api/domains/v1/whois/{whoisId}/usage
hostinger-ecommerce-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
ecommerce_discounts_list
List a store's discounts. Filter by free text over code and name, or by disabled state.
Amounts for fixed discounts are integers in the smallest currency unit; percentage
discounts carry a whole-number value between 1 and 100.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/discounts
ecommerce_discounts_create
Create a discount for a store. Fixed discounts take an amount in the smallest currency
unit (e.g. $10 is 1000); percentage discounts take a whole-number value between 1 and 100.
Free-shipping discounts ignore value. Returns the created discount.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/discounts
ecommerce_miscellaneous_custom-storefront-setup-instructions
Retrieve step-by-step setup instructions, formatted as Markdown, for connecting a custom sales
channel to your store and keeping your catalog, orders, shipping and payments in sync through
the Ecommerce API.
- Method:
GET
- Path:
/api/ecommerce/v1/miscellaneous/custom-storefront-instructions
ecommerce_orders_cancel
Cancel the order and optionally email the customer. Returns the updated order summary.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/cancel
ecommerce_orders_fulfil
Create a fulfilment for the order and attach tracking in one call. Omit items to fulfil
every remaining unfulfilled item. Returns the updated order summary.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/fulfill
ecommerce_orders_list-store
List a store's orders newest first as summaries. Filter by status, payment or fulfilment
status, customer email, order number or a free-text query. Amounts are in the smallest
currency unit. Retrieve a single order for its line items, addresses and fulfilments.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/orders
ecommerce_orders_retrieve
Retrieve one order in full: line items (each with the id the fulfil endpoint needs),
addresses, the totals breakdown and fulfilments with tracking. Amounts are in the
smallest currency unit.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/orders/{order_id}
ecommerce_payments_enable-manual-method
Enable a manual payment method so the store can accept orders without an online payment provider.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/payment-methods/manual
ecommerce_payments_create-provider-connect-link
Create an onboarding link for connecting a payment gateway to the store. Returns the gateway
onboarding URL for the merchant to open and a deep-link into the store admin.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/payment-providers/{provider_id}/connect-link
ecommerce_payments_list-store-providers
List a store's payment providers, split into providers already connected to the store and
gateways available to install. Never exposes gateway credentials, secrets, or configuration.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/payment-providers
ecommerce_products_create-image-upload-url
Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the
attach-image endpoint with the returned object_name to scan and attach it to the product.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images/upload-url
ecommerce_products_delete
Delete a product and its variants from the store. A subscription product with active
subscribers is archived instead of deleted so its data stays available.
- Method:
DELETE
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}
ecommerce_products_update
Update a product's name, description, status, SEO settings or collections. Set status to
published to make it buyable, draft to hide it, or archived to retire it. SEO settings (title,
description, slug) left out keep their values. collection_changes adds or removes collections
without touching the others. Variants, prices and inventory are managed through the variant
endpoints, not here. Returns the updated product summary.
- Method:
PATCH
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}
ecommerce_products_create-digital
Create a published digital product with a single variant and an optional external download link.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/products/digital
ecommerce_products_list
List a store's products newest first as lean summaries (name, status, thumbnail, variant
count and price range). Prices are integers in the smallest currency unit and live on
variants. Filter by status, free text or a set of product ids. Use include=variants to
embed each product's variants with prices and inventory, and include=media to embed its media.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/products
ecommerce_products_create-physical
Create a published physical product with a single variant priced in the store currency.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/products/physical
ecommerce_products_upload-and-attach-image
Fetch a raster image (JPEG, PNG, GIF or WebP, max 15MB) from a URL and attach it to a product in a
single call. Image downloads require HTTPS on port 443 without embedded credentials. At most one redirect
is allowed, and its destination must meet the same requirements. Private or reserved network
destinations, unsupported URLs and longer redirect chains are rejected. The image is virus-scanned
and validated by content, then stored on the CDN. Set is_thumbnail to make it the product's primary image.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images
ecommerce_sales-channels_list
List a store's active sales channels with their full metadata.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/sales-channels
ecommerce_sales-channels_create
Create a sales channel for a store. A "custom" channel is headless: build your own frontend and keep
your catalog, orders, shipping and payments in sync through the Ecommerce API. A "quick-link" channel
is a hosted one-page store whose handle is auto-generated.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/sales-channels
ecommerce_sales-channels_update
Update a custom sales channel. The merchant-facing name and the public url
(returned as the channel domain) can be changed. Pass null to clear a value.
- Method:
PATCH
- Path:
/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}
ecommerce_shipping_set-store
Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/shipping
ecommerce_stores_delete
Soft-delete a store owned by your account.
The underlying store data is preserved; only the store is marked as deleted.
- Method:
DELETE
- Path:
/api/ecommerce/v1/stores/{store_id}
ecommerce_stores_list
Retrieve the stores associated with your account.
- Method:
GET
- Path:
/api/ecommerce/v1/stores
ecommerce_stores_create
Create a new store for your account.
A primary sales channel is created alongside the store.
- Method:
POST
- Path:
/api/ecommerce/v1/stores
Get a store's readiness metadata: whether payment methods and shipping are configured,
plus its default currency. Useful to verify prerequisites before building a storefront.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/metadata
ecommerce_product-variants_update-in-batch
Update up to 100 existing variants in place by id โ title, SKU, inventory, stock tracking
and prices. Variants omitted from the request are left untouched. Prices replace the variant's
existing prices in full. Returns the updated variants.
- Method:
PATCH
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/batch
ecommerce_product-variants_delete
Delete a single variant from the product.
- Method:
DELETE
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/{variant_id}
ecommerce_product-variants_list
List a product's variants, ordered by rank, with their options, prices and inventory.
Prices are integers in the smallest currency unit and live on variants.
- Method:
GET
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants
ecommerce_product-variants_create
Add a variant to a product along one or more option dimensions (e.g. Size, Color). Options
missing from the product are created automatically; provide a value for every option the
product already has. Prices are integers in the smallest currency unit and default to the
store currency. Returns the created variant.
- Method:
POST
- Path:
/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants
hostinger-gpu-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
gpu_instances_get
Retrieve detailed information about a specified GPU instance, including its SSH keys.
Use this endpoint to follow the instance status after creating or deleting it.
- Method:
GET
- Path:
/api/gpu/v1/instances/{instanceId}
gpu_instances_delete
Delete a specified GPU instance.
The instance is destroyed asynchronously: a successful request returns immediately and the instance
status moves to destroying. Deleting fails while the instance is in created, destroying,
destroyed or abuse status, or while another action is in progress on it.
Use this endpoint to stop billing for a GPU instance you no longer need.
- Method:
DELETE
- Path:
/api/gpu/v1/instances/{instanceId}
gpu_exposed-services_delete
Delete a specified exposed service of a GPU instance.
The service is removed asynchronously: a successful request returns immediately and the service
stops being reachable from the internet shortly after.
Use this endpoint to close public access to a service on your GPU instance.
- Method:
DELETE
- Path:
/api/gpu/v1/instances/{instanceId}/exposed-services/{exposedServiceId}
gpu_exposed-services_list
Retrieve the services exposed on a specified GPU instance.
A newly created service is listed once it gets its public hostname and external port.
Use this endpoint to find the public address of services running on your GPU instance.
- Method:
GET
- Path:
/api/gpu/v1/instances/{instanceId}/exposed-services
gpu_exposed-services_create
Expose a service running on a specified GPU instance to the internet.
The service is exposed asynchronously: a successful request returns immediately, and the service
appears in the exposed services list once it gets its public hostname and external port.
Fails when the instance already has the maximum of 4 exposed services.
Use this endpoint to make an application on your GPU instance publicly reachable.
- Method:
POST
- Path:
/api/gpu/v1/instances/{instanceId}/exposed-services
gpu_instances_list
Retrieve all GPU instances of your account.
Use this endpoint to view your GPU instances with their status, pool, instance type and OS template.
- Method:
GET
- Path:
/api/gpu/v1/instances
gpu_instances_create
Create a new GPU instance.
Pick pool_instance_id from the pool instance types list and os_template_id from the OS templates
available for that instance type. Your account must have enough credits to run the instance for its
first hour.
The instance is created asynchronously: a successful request returns immediately, and the instance
appears in the instance list while its status moves from created through creating to running.
Use this endpoint to provision GPU compute.
- Method:
POST
- Path:
/api/gpu/v1/instances
gpu_instances_metrics
Retrieve utilisation metrics of a specified GPU instance for the last hour.
Each data point contains CPU, memory and GPU utilisation, used GPU memory and GPU throughput.
The list is empty until the instance is provisioned.
Use this endpoint to monitor GPU instance load.
- Method:
GET
- Path:
/api/gpu/v1/instances/{instanceId}/metrics
gpu_catalog_pool-groups
Retrieve GPU pool groups, ordered by name.
Each group bundles the pools of one GPU model and lists its currently available pools,
whether any of them is available and the lowest hourly price, in credits, among its instance types.
The price is returned even when the group is out of stock.
Use this endpoint to show which GPU models can be ordered and from what price.
- Method:
GET
- Path:
/api/gpu/v1/pools/groups
gpu_catalog_pool-instance-types
Retrieve the instance types offered by a specified GPU pool, ordered by CPU core count.
Each instance type describes its CPU, memory and storage, and its hourly price.
Only instance types that can currently be ordered are returned.
Use this endpoint to choose the pool_instance_id for a new GPU instance.
- Method:
GET
- Path:
/api/gpu/v1/pools/{poolId}/instances
gpu_catalog_pool-os-templates
Retrieve the OS templates that can be installed on a specified GPU pool instance type.
Use this endpoint to choose the os_template_id for a new GPU instance.
- Method:
GET
- Path:
/api/gpu/v1/pools/{poolId}/instances/{poolInstanceId}/os-templates
gpu_catalog_pool
Retrieve all available GPU pools, ordered by name.
A pool serves GPU accelerators of one model from a single region.
Use this endpoint to choose a pool before listing its instance types.
- Method:
GET
- Path:
/api/gpu/v1/pools
hostinger-horizons-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
horizons_websites_clone
Clone a Hostinger Horizons website into a new website.\n
Use this tool when the user wants a copy of an existing website, for example to try out
changes without touching the original.\n
This tool returns the ID and URL of the newly created copy.
The original website is left untouched.\n
To edit the copy, use the Edit website tool with the returned website ID, or the user can
open the provided website URL in Hostinger Horizons interface.
- Method:
POST
- Path:
/api/horizons/v1/websites/{websiteId}/clone
horizons_websites_list
List the Hostinger Horizons websites the user owns.\n
Use this tool when the user asks which websites they have, or when you need a website ID
before editing, publishing or cloning a website.\n
Each website is returned with its ID, status, domain and the URL to open it
in Hostinger Horizons interface.\n
The complete list of websites is returned in a single response - it is not paginated.
- Method:
GET
- Path:
/api/horizons/v1/websites
horizons_websites_create
Create new Hostinger Horizons website from the given message.\n
Use this tool when user asks you to create a website, landing page, blog
or any other type of application.\n
This tool initiates the website creation process and returns a website URL and ID.
The generation happens asynchronously.\n
After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing
that Hostinger Horizons is now creating their website and it will be ready in a few minutes
and you should provide the website URL to the user immediately
Do not write code.\n\nTo edit afterwards, use the Edit website tool with the returned
website ID, or the user can go to Hostinger Horizons interface in the provided website URL.
If the tool call fails with an error, you should provide a clear explanation of the error
and do not generate code yourself in the chat.
\n
TECHNOLOGY STACK CONSTRAINTS (STRICTLY ENFORCED):\n
The environment is limited to the following technologies.
You MUST NOT use, suggest, or implement any technology outside this list:\n
\n
-
Language: JavaScript ONLY.
-
Languages like TypeScript, Rust, Python, Java, PHP, etc., are STRICTLY PROHIBITED.\n
-
Framework: React.\n
-
Navigation: React Router.\n
-
Styling: TailwindCSS.\n
-
Components: shadcn/ui (built with @radix-ui primitives).\n
-
Icons: Lucide React.\n
-
Animations: Framer Motion.\n
\n
BACKEND & DATA STORAGE:\n
-
Horizons integrated backend is the EXCLUSIVE solution for persistent data storage,
authentication, and database needs.\n
-
Local databases (SQLite, MySQL, etc.) are STRICTLY PROHIBITED.\n
-
Third-party services (Firebase, AWS Amplify) are allowed ONLY if explicitly requested by the user.\n
\n
MAPS:\n
-
OpenStreetMap is the default provider.\n
-
Alternative providers (Google Maps, Mapbox) are allowed ONLY if explicitly requested by the user.\n
-
Method: POST
-
Path: /api/horizons/v1/websites
horizons_websites_edit
Edit an existing Hostinger Horizons website with a follow-up message.\n
Use this tool when the user wants to change, extend or fix a website that already exists.\n
This tool queues the requested changes and returns the website URL and ID.
The changes are applied asynchronously.\n
After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing
that Hostinger Horizons is now applying the requested changes and they will be ready
in a few minutes, and you should provide the website URL to the user immediately.
Do not write code.\n
If the tool call fails with an error, you should provide a clear explanation of the error
and do not generate code yourself in the chat.
- Method:
POST
- Path:
/api/horizons/v1/websites/{websiteId}/messages
horizons_websites_publish
Publish a Hostinger Horizons website so its latest changes go live.\n
Use this tool when the user asks to publish, deploy or make their website live.\n
This tool starts the publish process and returns the URL the website will be live on.
Publishing happens asynchronously and takes a few minutes.\n
Set is_template only when the user explicitly asks to share the website as a template:
true adds a "Use template" banner to its published pages that copies the website into the
visitor's own account, and false removes it. Leave it out to keep the current setting.\n
After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing
that the website is being published and you should provide the published URL to the user immediately.
- Method:
POST
- Path:
/api/horizons/v1/websites/{websiteId}/publish
horizons_websites_get
Get the link for the user to open their website in Hostinger Horizons interface.\n
Use this tool when the user wants the link to an existing website, or when you need its
website URL before or after editing it.\n
is_in_progress is true while changes are being generated or the website is being published;
wait until it is false before publishing. is_generating is true while changes are being generated,
and actions_in_progress has website_publish while the website is being published.
published_at is when the website was last published,
is_template is whether its published pages show the "Use template" banner, and
has_ecommerce_store is whether it has an online store.\n
Websites can be edited with the Edit website tool, or by the user in Hostinger Horizons
interface in the provided website URL.
- Method:
GET
- Path:
/api/horizons/v1/websites/{websiteId}
hostinger-hosting-mcp
changelog_list-entries
What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
- Method:
custom
- Path:
custom
hosting_deploy
Deploy, publish or upload a website to Hostinger web hosting (Shared, Cloud): static HTML, PHP, a nodejs (Node.js) app, a whole WordPress site, or a WordPress plugin or theme, from a local directory, an archive or a GitHub or GitLab repository. It detects what the project is and does the upload, build and Git setup itself: do not call upload or build operations, and do not archive the directory yourself. WARNING: it overwrites the website's contents and cannot be undone; confirm the domain with the user before deploying to a site that already has content. A Node.js build runs on the server: this returns a buildUuid at once, then call hosting_get-deployment until the build state is completed or failed. A plugin or theme goes into the site's WordPress installation, also when WordPress is in a folder of the document root (headless). Static, PHP, plugin and theme deploys are done when this returns; a WordPress site import only starts, and its files are extracted a few minutes later. From Git, pass type (static or nodejs) unless the site already runs a Node.js app or you pass Node.js settings; a static or PHP site deploys the branch now and again on every push; a Node.js site builds the branch now and on every later push, with the settings stored for the site (when none are stored, they are detected from the branch's package.json; pass appType, nodeVersion, outputDirectory, buildScript or entryFile to override them). Git needs GitHub or GitLab connected once in hPanel.
- Method:
custom
- Path:
custom
hosting_get-deployment
Check deployment status, build status, build logs and why a build failed (failure analysis) for a website's nodejs (Node.js) deployment: the state of its latest build (or of buildUuid), the end of the build log, the failure analysis when the build failed, and the build settings and Git auto-deployment settings stored for the site. Use it after hosting_deploy starts a Node.js build, and to find out why a deployment failed. Poll until the build state is completed or failed, with growing pauses. The log comes back in full; pass fromLine (the lines count from the previous call) to read only new output. A website without Node.js builds returns build: null with an explanation, because static, PHP, plugin and theme deploys are complete when hosting_deploy returns, and a WordPress site import is ready a few minutes after it starts.
- Method:
custom
- Path:
custom
hosting_websites_get-settings
Read a website's SSL certificate, HTTPS redirect, CDN and server cache settings in one call. ssl is the SSL status as hosting_ssl_status returns it: the certificate status (active, installing, waiting_for_retry, failed, expired or not_installed) and provider, whether it is a lifetime certificate, whether HTTP is redirected to HTTPS, when it expires and the last installation error. cdn.is_enabled says whether the Hostinger CDN serves the website. cache.is_enabled says whether server-side caching is on, and cache.is_cacheless_mode_enabled whether development (cacheless) mode bypasses it. Use it before hosting_websites_update-settings, and to follow an SSL installation started by hosting_ssl_install: poll until ssl.status is active or failed, with growing pauses. A section that cannot be read comes back as { error } and the others are still returned; cache is null with a cacheNote when cache status is not available. To install or remove a certificate use hosting_ssl_install or hosting_ssl_uninstall. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_websites_update-settings
Change a website's HTTPS redirect, CDN and server cache settings in one call. Pass only the settings to change, at least one. Settings are applied in the order cache, cachelessMode, cdn, httpsRedirect, and the call stops at the first failure. applied lists the settings that were changed. When a setting fails, the call returns an error whose text is the same JSON: failed names the setting and why, and skipped lists the ones not attempted; a multi-execute batch stops there too. Turning httpsRedirect on needs an active SSL certificate: the call checks it first and changes nothing when there is none. Install one with hosting_ssl_install and wait until hosting_websites_get-settings shows ssl.status active. cachelessMode is applied in the background and takes effect within a few minutes; enabling the CDN changes DNS records, so visitors are served through it after a few minutes of propagation. Certificates are not installed or removed here: use hosting_ssl_install and hosting_ssl_uninstall. Read the current values with hosting_websites_get-settings. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_cache_clear
Clear a website's server cache (the hosting server's page cache) and Hostinger CDN cache, so updated content shows at once. By default (scope: all) it clears the server cache and, when the CDN is on, purges the CDN too. scope: cdn purges only the CDN edge cache and leaves the server cache alone; that fails with 422 when the CDN is off. For a WordPress site installed in a subdirectory, pass directory to clear that installation's cache (only with scope all). This does not purge the WordPress LiteSpeed Cache plugin: that is a separate WordPress operation (wordpress_litespeed-cache_purge-lite-speed). To turn caching or the CDN on or off use hosting_websites_update-settings. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_php_update
Change a website's PHP version, extensions and php.ini options in one call. Pass only what to change, at least one of version, resetExtensions, extensions and options. Steps run in the order version, resetExtensions, extensions, options, and the call stops at the first failure. applied lists the steps that ran. When a step fails, the call returns an error whose text is the same JSON: failed names the step and why, and skipped lists the ones not attempted; a multi-execute batch stops there too. WARNING: changing the version resets the website's extensions (PHP 8.0 and later) and its options to their defaults, so pass the extensions and options to keep in the same call; they are applied after the version. Option values above the plan limit are capped silently: read the applied values back with hosting_php_get, which also lists the available versions, extensions and options. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_websites_list-domains
List the extra domains of a website: its parked (alias) domains, which show the same site under another domain name, and its subdomains (e.g. blog.example.com), with each one's root directory. parked items have domain (a domain name or an IP address) and type (domain or ip); subdomains items have domain (the full name), subdomain (the prefix) and root_directory. A list that cannot be read comes back as { error } and the other is still returned. To add or remove one use hosting_websites_add-domain or hosting_websites_remove-domain. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_websites_add-domain
Add a domain to an existing website: type parked adds a parked (alias) domain, a second domain name (or an IP address) that shows the same site; type subdomain creates a subdomain such as blog.example.com with its own directory. For a parked domain the domain must be owned by the account or already point to the website: check a domain from outside the account with hosting_domains_verify-ownership first. www belongs to the main domain: do not add it as a subdomain. To create a new website use hosting_websites_create instead. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_websites_remove-domain
Remove a parked (alias) domain or a subdomain from a website. Pass its name as hosting_websites_list-domains shows it: a parked domain, or a subdomain's full name or prefix; the tool finds which one it is. To delete a whole website use hosting_websites_delete. Works for Shared and Cloud hosting websites.
- Method:
custom
- Path:
custom
hosting_websites_trigger-event
Tell Hostinger that something happened on this website, so Hostinger services such as hPanel can react to it. event.name picks the event and decides which event.params it takes. The call changes nothing on the website.
- Method:
custom
- Path:
custom
hosting_cron-jobs_list
Returns the list of cron jobs configured for the specified account, including their schedule and command.
- Method:
GET
- Path:
/api/hosting/v1/accounts/{username}/cron-jobs
hosting_cron-jobs_create
Creates a cron job for the specified account from a schedule expression and a command.
Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output.
- Method:
POST
- Path:
/api/hosting/v1/accounts/{username}/cron-jobs
hosting_cron-jobs_delete
Permanently deletes the cron job identified by its uid.
The uid is returned by the list cron jobs endpoint.
- Method:
DELETE
- Path:
/api/hosting/v1/accounts/{username}/cron-jobs/{uid}
hosting_cron-jobs_output
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.
- Method:
GET
- Path:
/api/hosting/v1/accounts/{username}/cron-jobs/{uid}/output
hosting_databases_change-password
Changes the password for the specified database user.
The database name must be the full name returned by the list databases endpoint.
The password must also be updated in any website configuration that uses this database.
- Method:
PATCH
- Path:
/api/hosting/v1/accounts/{username}/databases/{name}/change-password
hosting_databases_list
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.
- Method:
GET
- Path:
/api/hosting/v1/accounts/{username}/databases
hosting_databases_create
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.
- Method:
POST
- Path:
/api/hosting/v1/accounts/{username}/databases
hosting_databases_delete
Permanently deletes a database and its remote connections.
The database name must be the full name returned by the list databases endpoint.
- Method:
DELETE
- Path:
/api/hosting/v1/accounts/{username}/databases/{name}
hosting_databases_create-remote-connection
Allows a remote host to connect to the specified database.
Provide an IPv4/IPv6 address, or "%" to allow any host. The database name must be
the full name returned by the list databases endpoint. Database creation is synchronous,
so a 404 here means no database with that name exists under the username, not that it
is still being created.
- Method:
POST
- Path:
/api/hosting/v1/accounts/{username}/databases/{name}/remote-connections
hosting_databases_delete-remote-connection
Permanently removes a remote-access rule, revoking the given host's remote access to the database.
Identify the rule with the required ip query parameter (the IPv4/IPv6 address, or "%",
exactly as returned by the list remote connections endpoint). The database name must be
the full name returned by the list databases endpoint.
- Method:
DELETE
- Path:
/api/hosting/v1/accounts/{username}/databases/{name}/remote-connections
hosting_databases_list-remote-connections
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.
- Method:
GET
- Path:
/api/hosting/v1/accounts/{username}/databases/remote-connections
hosting_databases_repair
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.
- Method:
PATCH
- Path:
/api/hosting/v1/accounts/{username}/databases/{name}/repair
hosting_databases_setup-website
Creates a new MySQL database for the website and writes its connection details into the
website's environment variables, then restarts the application. The platform generates the
password (and the database name and user, unless supplied). The password is never returned;
the application reads it from the environment.
Written variables: DB_HOST, DB_PORT, DB_NAME, DB_USER, DB_PASSWORD and
DATABASE_URL (mysql://user:password@host:port/name, user and password percent-encoded).
Existing variables are kept. If the website already has any variable with one of these
names the call fails with 422 and nothing is created; the Replace Node.js environment variables endpoint removes them.
After this call the variables are ordinary environment variables: the
Replace Node.js environment variables endpoint changes or removes them like any other.
A restart is enough for apps that read environment variables at process start, such as
Express or NestJS. Frameworks that bake variables into the build output (Next.js,
NEXT_PUBLIC_*) see the new values only after a fresh build (Start Node.js build endpoint).
A password in the request is ignored; the platform always generates it. The optional name
and user are identifiers, not secrets.