Tools & integrations

Every official way to drive the Hostinger API besides raw HTTP — the CLI, SDKs, MCP server, Ansible collection, Terraform provider, n8n node, WHMCS module, and the Postman collection.

The Hostinger API is the foundation for a set of official tools. Some are generated from the same OpenAPI specification and therefore cover every endpoint; others are hand-built for a specific platform and cover a focused slice of the API.

Pick by how you work: a terminal, an application, an infrastructure-as-code pipeline, a workflow builder, or an AI assistant.

Generated from the specification

These cover the whole API and pick up new endpoints automatically when the specification changes.

Tool	Install	Use it for
Hostinger CLI	brew install hostinger/tap/hostinger	Terminal work, shell scripts, CI
PHP SDK	composer require hostinger/api-php-sdk	PHP applications
Python SDK	pip install hostinger-api	Python applications
TypeScript SDK	npm install @hostinger/sdk	Node and browser applications
MCP server	npx @hostinger/mcp	AI assistants — see below

The Email SDKs are the equivalent set for the separate Mail API, which reads and sends mail from your mailboxes.

MCP server

The @hostinger/mcp package exposes the API as Model Context Protocol tools, so an AI assistant can manage your hosting, domains, DNS, VPS and billing directly.

Two ways to connect:

• Hosted — point your assistant at https://mcp.hostinger.com. Nothing to install; you sign in from the browser.

• Local — run npx @hostinger/mcp and authenticate with an API token or through the browser.

For a ready-made setup inside a code editor, use the Hostinger Connector, which wraps the same server with editor integration and guided sign-in.

Source: hostinger/api-mcp-server.

Infrastructure as code

Both tools below are focused on VPS provisioning rather than the whole API.

Terraform

The Hostinger Terraform provider manages VPS instances, SSH keys, post-install scripts and DNS zone records, with support for importing VPS instances you created elsewhere.

terraform {
  required_providers {
    hostinger = {
      source  = "hostinger/hostinger"
      version = "0.1.23"
    }
  }
}

Requires Terraform 1.3 or later and an API token. Provisioning new servers also needs a payment method on the account. Source: hostinger/terraform-provider-hostinger.

Ansible

The hostinger.vps collection provides modules for VPS power state, hostnames, firewalls, snapshots, SSH keys, post-install scripts, the malware scanner and metrics, plus a dynamic inventory plugin that discovers your VPS instances.

ansible-galaxy collection install hostinger.vps

Requires ansible-core 2.13 or later. Source: hostinger/ansible-collection-hostinger.

Workflow automation

n8n

The n8n-nodes-hostinger-api community node adds Hostinger as a step in n8n workflows — VPS management, domains, DNS, billing and Reach — so you can trigger Hostinger actions from any other service n8n connects to.

Install it through n8n's community nodes screen. Source: hostinger/api-n8n-node.

WHMCS

The Hostinger WHMCS module integrates VPS and Cloud services into a WHMCS billing system: automated provisioning, restarts and reinstalls, disk and bandwidth tracking, backups and snapshots, nameserver and PTR management, and a VPS control panel in the client area.

Requires WHMCS 8.0 or later, PHP 8.1 or later, and an API token.

Postman

The Hostinger public workspace hosts a Postman collection covering the API, useful for exploring endpoints interactively before you write any code.

You can also work straight from the endpoint pages in these docs — each one has a Test it panel that sends a real request from your browser.

The OpenAPI specification

Everything above starts from one document: https://developers.hostinger.com/openapi/openapi.json.

Fetch it directly if you want to generate a client for a language Hostinger doesn't publish, feed the API to a tool that consumes OpenAPI, or diff versions to see what changed.

---

Last updated: September 10, 2026