Billing: Orders

Create purchase order

Changed on

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.

post/api/billing/v1/orders

Request

  • Base URL: https://developers.hostinger.com
  • URL: https://developers.hostinger.com/api/billing/v1/orders
  • Auth: HTTP bearer

Request body

payment_method_idinteger

Payment method ID, default will be used if not provided

Example request

{
  "payment_method_id": 1327362,
  "items": [
    {
      "item_id": "hostingercom-vps-kvm2-usd-1m",
      "quantity": 1
    }
  ],
  "coupons": [
    [
      "Coupon 3"
    ]
  ]
}

Response

Success response

idinteger

Order ID

subscription_idstring

Subscription ID

status'completed' | 'pending' | 'processing' | 'failed' | 'refunded' | 'cancelled' | 'awaiting_payment' | 'payment_initiated' | 'fraud_refund'
currencystring

Currency code

subtotalinteger

Subtotal price (exc. VAT) in cents

totalinteger

Total price (inc. VAT) in cents

created_atstring date-time
updated_atstring date-time

Example response

{
  "id": 2957086,
  "subscription_id": "Azz353Uhl1xC54pR0",
  "status": "completed",
  "currency": "USD",
  "subtotal": 899,
  "total": 1088,
  "billing_address": {
    "first_name": "John",
    "last_name": "Doe",
    "country": "NL",
    "email": "john@doe.tld"
  },
  "created_at": "2025-02-27T11:54:22Z",
  "updated_at": "2025-03-27T11:54:22Z"
}

Changes