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-, DRV- or COM- 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. This does not apply to COMMODITY: an out-of-range commodity limit is rejected (see Commodity (MCX) Smart Orders).
• 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.

Commodity (MCX) Smart Orders¶

/smart/order accepts segment: "COMMODITY" with exchange: "MCX". The fields and the placement response are the same as for any smart order; slicing works as described under Slicing Large Orders.

The commodity-specific rules — the price and leg constraints, the COM-/GTT- id combinations, and modify/cancel behaviour — are collected in Commodity (MCX) Trading.

Slicing Large Orders¶

A single exchange order is capped at the instrument's freeze quantity — and on COMMODITY, also at ₹3.5 crore of order value. Place Smart Order refuses a larger qty:

Qty exceeds freeze quantity of 3511; set slice_order=true to enable slicing

Set slice_order: true and the same request is split server-side into several independent orders, each within every applicable cap, with the stop-loss and target legs attached to every slice.

slice_order is an opt-in, not a mode switch. With qty inside the caps the flag has no effect: the request is placed as an ordinary smart order and answers synchronously with order_status: "CREATED".

Example Request

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": "48704",
  "qty": 7020,
  "limit_price": 22500,
  "sl_trigger_price": 22000,
  "sl_limit_price": 21950,
  "tgt_trigger_price": 23000,
  "tgt_limit_price": 22950,
  "slice_order": true,
  "algo_id": "99999",
  "remarks": "momentum-v2/sig-4471"
}'

Every other field behaves exactly as on Place Smart Order. limit_price, the stop-loss and target legs, and remarks are applied to every slice.

How the quantity is split¶

The slice size is the largest number of whole lots that fits every applicable cap. Each slice except the last is exactly that size; the last takes the remainder.

Both inputs are published in the instruments master — LOT_UNITS is the lot size, FREEZE_QTY the freeze quantity — so you can work the slice count out before you send:

slice size = floor(FREEZE_QTY / LOT_UNITS) × LOT_UNITS
slices     = ceil(qty / slice size)

Exchange freeze quantities are rarely whole multiples of the lot size — across the F&O master, 94% sit exactly one unit above a lot boundary — so the slice size rounds down to the nearest lot. Because the total must itself be a lot multiple, the remainder always is one too.

On COMMODITY the value cap usually binds first and the slice is then smaller than the freeze quantity alone would allow. For a silver contract with a lot size of 30 quoted at ₹220,000, one slice is 5 lots — floor(3,50,00,000 ÷ (220000 × 30)) — not the 20 lots the freeze quantity would permit.

Response¶

Each slice is a fully independent order. It has its own order_id, its own row in the order book, and its own stop-loss/target leg. It is modified or cancelled on its own through /smart/order/modify and /smart/order/cancel, parent and leg separately, exactly like any other smart order.

order_data holds one entry per slice, in slice order.

Response Payload (Success)

{
  "status": "success",
  "data": {
    "order_data": [
      { "order_id": "DRV-28131451", "order_status": "INITIATED" },
      { "order_id": "DRV-28131452", "order_status": "INITIATED" }
    ]
  }
}

There is no bulk_order_id in a sliced response. Reconcile the request through your own remarks tag, which is carried onto every slice.

Validations¶

Every Place Smart Order validation applies, checked on the total qty before anything is created, so a failed validation means nothing was placed — not a partial set of slices. Exceeding the freeze quantity is the expected input here, so that check alone is lifted.

Each of these returns 400 with error_type: "RequestValidationException" and the message shown.

Rate limits¶

The request itself counts once against the /smart/order request limit. Each slice is a real order, so when the background processor sends it, it counts against the per-second order placement cap exactly as a standalone order would. A request that produces 10 slices sends 10 orders.

Those units are spent when the slices are sent, not when the call returns, so the spend lands a moment after your request completes. If you are already close to the cap, a slice can be rate-limited and end up FAILED on the order book while its siblings go through. Pace your own submissions accordingly; firing several sliced requests back-to-back multiplies the order count, not just the request count.

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",
  "qty": 20,
  "limit_price": 0.35
}'

Example Request — Modify a stop-loss and target leg (OCO)

curl --location 'https://api.indstocks.com/smart/order/modify' \
--header 'Authorization: YOUR_ACCESS_TOKEN' \
--data '{
  "order_id": "GTT-2914581",
  "segment": "DERIVATIVE",
  "algo_id": "99999",
  "sl_trigger_price": 0.15,
  "sl_limit_price": 0.1,
  "tgt_trigger_price": 41,
  "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": "GTT-456",
  "segment": "EQUITY",
  "algo_id": "99999",
  "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": "DRV-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