Orders API Integration

Introduction

The ILS Orders API lets you push orders into your ILS Panel programmatically. Use it to connect a custom storefront, sync from an ERP, automate test orders, or bridge any platform we do not natively integrate with.

All endpoints are stateless and accept JSON. Every response — success or failure — is JSON with the same envelope. Your client never needs to parse HTML.

Base URL & Format

• HTTP method: All endpoints accept POST only. Any other verb returns 405 Method Not Allowed.
• Content-Type: application/json on every request.
• Auth header: auth-key: <your-api-key> on every request.
• Identifier: The reference_id returned by Create Order is passed in the JSON body of Detail, Update, and Delete — not in the URL.

Authentication

Every request must carry your panel-generated API key in the auth-key HTTP header. The key encodes your user id and a per-account unique code — treat it like a password.

Your key is already provisioned and visible inside the panel under Channel » Public API. See Where to find your API key for step-by-step screenshots of the path.

// Example header
auth-key: AbCd1234EfGhIjKlMnOpQrStUvWxYz0987654321

Where to find your API key & channel id

Every ILS Panel account has a unique API key and one unique_id per active channel — both are visible in the panel, no manual generation required.

1. Sign in to your ILS Panel.
2. Open Channel from the left navigation.
3. On the Channel integrations grid, find the Public API card and click View.
4. The API Auth Key field shows your token, masked by default. Click the eye icon to reveal, then the copy icon to copy it into your auth-key header.
5. Below the auth key you will see your active channels with their channel unique id (an alphanumeric string, up to 50 chars). Copy that value and pass it as channel_id in the order body to scope the order to that channel. Omit channel_id and the order is recorded as a manual entry under your account.

The keys are derived from your account's unique code and identity, so they stay valid for the lifetime of your account. If you suspect compromise, contact [email protected] to rotate the underlying unique code — this invalidates all derived tokens immediately.

Response envelope

Every response — success or error — follows the same shape:

{
  "status": 200,
  "message": "Human-readable summary",
  "data": { /* present on success; optional on failures */ }
}

Status codes

HTTP status codes and the status field inside the JSON body always agree.

Create Order

Creates a new order in your panel. The order is written immediately into order_detail and order_items — no queue, no delay. A generated reference_id is returned which you must use to read, update, or delete the order later.

Headers

Body parameters

Address fields (shipping_address & billing_address) — Indian standards

Product fields (products[])

Example request

POST /api/order/create HTTP/1.1
Host: ilsportal.io
Content-Type: application/json
auth-key: AbCd1234EfGhIjKlMnOp...

{
  "order_id": 202610010001,
  "order_name": "#1001",
  "order_date": "01-06-2026",
  "reference_no": 1001,
  "channel_id": "<channel unique_id from panel>",
  "payment_type": "PREPAID",
  "tax_include": true,
  "order_notes": "Please ship promptly",
  "tags": ["WEB", "PRIORITY"],
  "weight_unit": "KG",
  "invoice_number": "INV/2026/00045",
  "package_details": { "length": 30, "width": 20, "height": 10 },
  "shipping_gstin": "24AAACI1681G1ZE",
  "billing_gstin": "24AAACI1681G1ZE",
  "shipping_address": {
    "first_name": "Chetna",
    "last_name": "Patel",
    "address1": "123 Varachha",
    "address2": "Near Mota Varachha",
    "city": "Surat",
    "province": "Gujarat",
    "province_code": "GJ",
    "zip": "395008",
    "country": "India",
    "country_code": "IN",
    "phone": "+919033104668",
    "email": "[email protected]"
  },
  "products": [
    {
      "product_name": "T-Shirt Cotton",
      "product_sku": "TSHRT-001",
      "product_price": 299.00,
      "product_quantity": 2,
      "product_weight": 0.250,
      "product_weight_unit": "KG",
      "product_tax": 5,
      "product_discount": 10,
      "product_hsn": "61091000",
      "product_variant_title": "Red / Large"
    }
  ],
  "shipping_detail": {
    "shipping_title": "Standard",
    "shipping_charge": 40.00
  }
}

Example response — 200 OK

{
  "status": 200,
  "message": "The order has been created successfully.",
  "data": { /* full normalized order JSON, including reference_id */ }
}

Get Order Details

Returns the full order JSON for a previously created order. Pass the reference_id in the JSON body. The response includes the complete fulfillments[] array (each entry has tracking_company, tracking_number, tracking_url, and the line_items[] covered by that fulfilment), as well as top-level fulfillment_status (fulfilled, partially_fulfilled, or unfulfilled) and per-item fulfillment_status / fulfillable_quantity.

Body parameters

Example request

POST /api/order/detail HTTP/1.1
Host: ilsportal.io
Content-Type: application/json
auth-key: AbCd1234EfGhIjKlMnOp...

{
  "reference_id": "482A1B7C9E3F"
}

Example response — 200 OK

{
  "status": 200,
  "message": "The order details have been fetched successfully.",
  "data": {
    "id": "ORD-2026-1001",
    "name": "#1001",
    "order_number": 1001,
    "created_at": "2026-06-01T00:00:00.000Z",
    "financial_status": "paid",
    "fulfillment_status": "unfulfilled",
    "total_price": 628.0,
    "total_tax": 28.0,
    "line_items": [ /* ... */ ],
    "shipping_address": { /* ... */ },
    "customer":        { /* ... */ },
    "reference_id": "482A1B7C9E3F"
  }
}

Update Order

Patches an existing order. Only a fixed set of fields can be modified, and only while the order is still pending. The reference_id is sent in the body alongside the fields to change.

Body fields

Tracking & item-wise fulfilment

The tracking_details object carries the carrier-issued tracking. It now accepts an optional items[] array for item-wise fulfilment:

Example request

POST /api/order/update HTTP/1.1
Host: ilsportal.io
Content-Type: application/json
auth-key: AbCd1234EfGhIjKlMnOp...

{
  "reference_id": "482A1B7C9E3F",
  "tags": ["VIP", "GIFT"],
  "order_notes": "Leave at front desk",
  "tracking_details": {
    "tracking_number": "TR123456",
    "tracking_company": "DTDC",
    "tracking_url": "https://trackdtdc.in/TR123456",
    // Optional: list specific SKUs and quantities to fulfil.
    // Omit the items array to fulfil the entire order with this tracking.
    "items": [
      { "sku": "TSHRT-001", "quantity": 2 }
    ]
  }
}

Example response — 200 OK

{
  "status": 200,
  "message": "The order has been updated successfully.",
  "data": { /* full normalized order JSON */ }
}

Delete Order

Removes the order from order_detail and order_items and deletes its on-disk JSON. Only orders in pending status can be deleted — the same definition used by Update Order: status = '2' AND cancel_status = '0' AND fulfill_status = '0'. The reference_id is sent in the body.

Body parameters

Example request

POST /api/order/delete HTTP/1.1
Host: ilsportal.io
Content-Type: application/json
auth-key: AbCd1234EfGhIjKlMnOp...

{
  "reference_id": "482A1B7C9E3F"
}

Example response — 200 OK

{
  "status": 200,
  "message": "The order has been deleted successfully."
}

Error Handling

All errors return JSON with the same envelope and an HTTP status code that mirrors the status field. The API never returns HTML — even on internal server errors, you receive valid JSON your client can parse safely.

Postman Collection

Download a ready-to-import Postman collection with every endpoint, pre-filled headers and example bodies. Set your auth_key, base_url, and channel_id in the environment and start sending requests.

Import steps

1. Open Postman » Import » choose the downloaded JSON.
2. Create a new environment with the variables base_url, auth_key, channel_id, and reference_id.
3. Activate the environment and run Create Order first — copy the returned reference_id into the variable to test Get / Update / Delete.