Angel One API — Unable to Identify MTF Holdings

Issue

We need to identify whether an existing equity holding in an Angel One account was purchased using MTF (Margin Trading Facility) or as a normal Delivery/CNC position.

Scenario

Suppose a user buys:

• Stock: RELIANCE-EQ
• Quantity: 100
• Product: MTF

Initially, the order appears in the positions/order information. After the position is converted into a holding, we fetch the user's holdings using the Angel One SmartAPI getHolding / getAllHolding API.

The holding response provides information such as:

{
  "tradingsymbol": "RELIANCE-EQ",
  "quantity": 100,
  "averageprice": 2500,
  "product": "DELIVERY"
}

However, there does not appear to be a field that tells us:

"is_mtf": true

or:

"product_type": "MTF"

Problem

Once the position becomes a holding, our application cannot reliably determine whether the shares are:

1. Normal delivery/CNC shares, or
2. Shares purchased using MTF.

This creates a problem for OMS/reconciliation systems that need to calculate:

• MTF-funded quantity
• Customer's own-funded quantity
• Outstanding MTF amount
• MTF interest
• MTF liquidation/risk exposure
• Pledge/collateral requirements

Expected

Is there any Angel One SmartAPI endpoint or field that can provide the following information for a user's existing holdings?

Symbol
Quantity
MTF Quantity
Normal Delivery Quantity
MTF Outstanding Amount

Ideally, the API response should expose something similar to:

{
  "tradingsymbol": "RELIANCE-EQ",
  "quantity": 100,
  "mtf_quantity": 100,
  "delivery_quantity": 0,
  "is_mtf": true
}

Question

Does Angel One provide any API/endpoint through SmartAPI that can determine whether an existing holding is an MTF holding, after the original MTF order has moved from Position to Holding?

If yes, please provide the API endpoint and response fields/documentation.

If not, please confirm whether the recommended approach is to maintain the MTF state in the client's own OMS based on the original order's product type.

Environment

• Broker: Angel One
• API: SmartAPI
• Use case: OMS / Broker Integration
• Requirement: Identify MTF holdings after settlement/conversion to holdings