• Core Concepts
• Common Patterns
• API Reference
• Best Practices
• Troubleshooting
• References

Note: This endpoint lives under a different base path —

/api/v2/direct/verifications/active

— not

/api/domains/v1/

.

curl -X POST "https://developers.hostinger.com/api/domains/v1/availability" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "myawesomesite",
    "tlds": ["com", "net", "org"],
    "with_alternatives": true
  }'

from hostinger_api import Hostinger

client = Hostinger(api_token="YOUR_API_TOKEN")
result = client.domains.availability.check(
    domain="myawesomesite",
    tlds=["com", "net", "org"],
    with_alternatives=True
)

import { Hostinger } from "hostinger-api-sdk";

const client = new Hostinger({ apiToken: "YOUR_API_TOKEN" });

const result = await client.domains.availability.check({
  domain: "myawesomesite",
  tlds: ["com", "net", "org"],
  withAlternatives: true,
});

use Hostinger\Api\HostingerApi;

$client = new HostingerApi('YOUR_API_TOKEN');

$result = $client->domains->availability->check([
    'domain' => 'myawesomesite',
    'tlds' => ['com', 'net', 'org'],
    'with_alternatives' => true,
]);

Note: Rate limited to 10 requests per minute. TLDs should be without leading dot (e.g.,

com

not

.com

). For alternatives, provide only one TLD.

curl -X POST "https://developers.hostinger.com/api/domains/v1/portfolio" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "my-new-domain.com",
    "item_id": "hostingercom-domain-com-usd-1y",
    "payment_method_id": 1327362,
    "domain_contacts": {
      "owner_id": 741288,
      "admin_id": 741288,
      "billing_id": 741288,
      "tech_id": 741288
    }
  }'

Get

item_id

from the billing catalog. If no payment method is provided, your default is used. If no WHOIS info is provided, default contact information for that TLD is used.

• Always check availability before attempting to purchase
• Ensure WHOIS profile exists for the target TLD before registering
• Some TLDs require

  additional_details

  — check requirements per TLD
• Keep domain lock enabled to prevent unauthorized transfers

• Enable privacy protection to hide personal information from public WHOIS
• Enable domain lock on all production domains
• Only disable domain lock immediately before an intended transfer

• Improper nameserver configuration makes the domain unresolvable
• Always have at least 2 nameservers configured
• Verify nameservers are responding before switching

• Use

  301

  (permanent) for SEO-preserving redirects
• Use

  302

  (temporary) for short-term redirects
• Remove forwarding before pointing the domain to hosting

• Nameserver changes can take up to 48 hours to propagate
• Verify new nameservers are configured correctly:

  dig NS example.com

• Check that DNS records exist on the new nameserver

• Check registration status in hPanel
• Verify WHOIS profile is complete for the target TLD
• Ensure payment method has sufficient funds

• Some TLDs have registrar-imposed lock periods after registration
• Contact support if the lock state doesn't change

• Profile may be in use by active domains
• Check usage with the

  /whois/{whoisId}/usage

  endpoint first

• transfer-guide.md

  — Domain purchase workflow, nameserver configuration, transfer procedures, WHOIS management, and bulk operations (TypeScript/PHP examples)

• Hostinger API Documentation
• Hostinger API Changelog
• Python SDK
• TypeScript SDK
• PHP SDK
• CLI Tool