Smart Order APIs (GTT)¶

This section outlines the APIs for placing, modifying, and canceling multi-leg "Good Till Triggered" (GTT) orders, which include simultaneous stop-loss and target legs, as well as Trigger orders.

How Smart Orders Work¶

When you place a smart order via /smart/order, the system creates two linked orders:

1. Parent Order — The primary order (MARKET, LIMIT, or TRIGGER) that gets sent to the exchange first (except if the entered limit price is outside the circuit bounds, then parent order is placed as a GTT order instead).
2. Child Order — A GTT (Good Till Triggered) order containing the stop-loss and/or target legs. It is linked to the parent and only activates once the parent order is successfully executed.

Order ID Prefixes¶

Each order ID carries a prefix that indicates its type:

• A parent order normally receives an EQ- or DRV- prefix depending on the segment.
• If the entered limit price is outside the circuit bounds, the parent order is placed as a GTT order instead and receives a GTT- prefix.
• Child orders always carry a GTT- prefix.

Placement Response¶

The API response returns both order IDs in a single payload:

{
  "status": "success",
  "data": {
    "order_data": [
      {
        "order_id": "DRV-28131451",
        "order_status": "CREATED",
        "child_order_details": {
          "order_id": "GTT-2914581",
          "order_status": "CREATED"
        }
      }
    ]
  }
}

Modification and Cancellation¶

Parent and child orders are independent entities. To modify or cancel a smart order, you must operate on each order separately using its own order_id:

• Use /smart/order/modify with the parent order_id (e.g. DRV-28131451) to modify the parent.
• Use /smart/order/modify with the child order_id (e.g. GTT-2914581) to modify the child.
• The same applies to /smart/order/cancel — each order must be cancelled individually.

Place Smart Order¶

This API allows you to place a new multi-leg smart order (GTT).

Endpoint

POST /smart/order

Request Body

Example Request — LIMIT order (Derivative)

curl --location 'https://api.indstocks.com/smart/order' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "txn_type": "BUY",
  "exchange": "NSE",
  "segment": "DERIVATIVE",
  "product": "MARGIN",
  "order_type": "LIMIT",
  "validity": "DAY",
  "security_id": "51011",
  "qty": 75,
  "limit_price": 37,
  "sl_trigger_price": 34,
  "tgt_trigger_price": 41,
  "sl_limit_price": 33,
  "tgt_limit_price": 38,
  "algo_id": "99999",
  "remarks": "momentum-v2/sig-4471"
}'

Example Request — Trigger-Market order (Equity)

curl --location 'https://api.indstocks.com/smart/order' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "txn_type": "BUY",
  "exchange": "NSE",
  "segment": "EQUITY",
  "product": "CNC",
  "order_type": "TRIGGER",
  "validity": "DAY",
  "security_id": "3045",
  "qty": 10,
  "trigger_price": 1520.00,
  "algo_id": "99999"
}'

Example Request — Trigger-Limit order (Derivative)

curl --location 'https://api.indstocks.com/smart/order' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "txn_type": "BUY",
  "exchange": "NSE",
  "segment": "DERIVATIVE",
  "product": "MARGIN",
  "order_type": "TRIGGER",
  "validity": "DAY",
  "security_id": "51011",
  "qty": 75,
  "trigger_price": 38.50,
  "trigger_limit_price": 38.75,
  "algo_id": "99999"
}'

Example Request — Trigger order with stop-loss and target legs (Derivative)

curl --location 'https://api.indstocks.com/smart/order' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "txn_type": "BUY",
  "exchange": "NSE",
  "segment": "DERIVATIVE",
  "product": "MARGIN",
  "order_type": "TRIGGER",
  "validity": "DAY",
  "security_id": "46997",
  "qty": 65,
  "trigger_price": 318.75,
  "trigger_limit_price": 319,
  "sl_trigger_price": 316.65,
  "sl_limit_price": 316.40,
  "tgt_trigger_price": 328.65,
  "tgt_limit_price": 328.90,
  "algo_id": "99999"
}'

Here the legs are checked against an entry price of 319 — the trigger_limit_price — rather than limit_price, which plays no part in a TRIGGER order's execution.

Trailing Stop Loss (TSL)¶

A trailing stop loss is a stop-loss leg whose trigger price follows the market in your favour. As the price moves favourably, the stop-loss trigger is stepped along behind it by tsl_step_size; when the price moves against you, the trigger stays where it is. It only ever ratchets one way, which is what locks in gains.

TSL is not a separate order type — it is a modifier on the stop-loss leg of a smart order. You enable it with two fields:

Example Request — Trailing stop loss (Equity)

curl --location 'https://api.indstocks.com/smart/order' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "txn_type": "BUY",
  "exchange": "NSE",
  "segment": "EQUITY",
  "product": "CNC",
  "order_type": "LIMIT",
  "validity": "DAY",
  "security_id": "2885",
  "qty": 1,
  "limit_price": 1400.05,
  "sl_trigger_price": 1375.00,
  "sl_limit_price": 1374.50,
  "is_tsl": true,
  "tsl_step_size": 0.05,
  "algo_id": "99999"
}'

In this example the stop-loss starts at ₹1375.00. If the price climbs, the trigger is trailed upward in ₹0.05 steps; if the price falls back, the trigger holds at the highest level it reached.

Requirements¶

• A stop-loss leg is mandatory: send both sl_trigger_price and sl_limit_price. TSL rides on the stop-loss leg, so a request with is_tsl: true and no stop-loss is rejected.
• is_tsl and tsl_step_size must agree — is_tsl: true requires tsl_step_size > 0, and sending a tsl_step_size without is_tsl: true is rejected.
• tsl_step_size must be a multiple of the instrument's tick size.
• Not supported for order_type: "TRIGGER". A trigger order can carry an ordinary stop-loss leg, but that leg cannot trail.
• Supported on /smart/order only. is_tsl sent to the plain /order endpoint is ignored.

Reading the trailed price¶

On /order and /order-book, a trailing stop-loss order carries two extra fields:

For a TSL order, sl_trigger_price reflects the live trailed trigger — the current, stepped-up value — not the price you originally submitted. sl_limit_price moves with it, preserving your original trigger-to-limit gap.

Changing a trailing stop loss¶

Modify Smart Order¶

This API allows you to modify a pending smart order.

Endpoint

POST https://api.indstocks.com/smart/order/modify

Request Body

Example Request — Modify LIMIT order

curl --location 'https://api.indstocks.com/smart/order/modify' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--data '{
  "order_id": "DRV-123",
  "segment": "DERIVATIVE",
  "algo_id": "99999",
  "order_type": "LIMIT",
  "qty": 20,
  "limit_price": 0.35,
  "sl_trigger_price": 0.15,
  "tgt_trigger_price": 41,
  "sl_limit_price": 0.1,
  "tgt_limit_price": 42
}'

Example Request — Modify Trigger order

curl --location 'https://api.indstocks.com/smart/order/modify' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--data '{
  "order_id": "EQ-456",
  "segment": "EQUITY",
  "algo_id": "99999",
  "order_type": "TRIGGER",
  "qty": 10,
  "trigger_price": 1530.00,
  "trigger_limit_price": 1532.00
}'

Cancel Smart Order¶

This API allows you to cancel a pending smart order.

Endpoint

POST /smart/order/cancel

Request Body

Example Request

curl --location 'https://api.indstocks.com/smart/order/cancel' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--data '{
  "segment": "DERIVATIVE",
  "order_id": "123456789"
}'

See Also¶

• Orders — standard (non-GTT) order placement and management
• Margin Calculator — check required margin before placing an order
• Glossary & Constants — EQ-/DRV-/GTT- ID prefixes and shared enums
• Error Bucket — RMS rejection messages and OrderException handling