Exposure Margin coming as 0

shbhnkr
I am using the API to calculate margins for Equity Options. I have tried using any basket, it gives me the correct SPAN but the exposure margin is always 0. See the trade below. I am buying 1 lot of TataSteel at strike price of 1000 and selling 3 lots at strike price of 1100. It is showing me correct span but exposure margin is showing as 0.
{"exchange": "NFO",
"tradingsymbol": "TATASTEEL22JUL1100CE",
"transaction_type": "SELL",
"variety": "regular",
"product": "NRML",
"order_type": "MARKET",
"quantity": 1275,
"price": 0,
"trigger_price": 0},
{"exchange": "NFO",
"tradingsymbol": "TATASTEEL22JUL1000CE",
"transaction_type": "BUY",
"variety": "regular",
"product": "NRML",
"order_type": "MARKET",
"quantity": 425,
"price": 0,
"trigger_price": 0}
  • shbhnkr
    Now I am getting for some symbols. Getting the correct SPAN and Exposure for SBIN but not for TATASTEEL and RELIANCE
  • rakeshr
    We just checked for the same basket param and it's coming fine.
    {
    "type": "equity",
    "tradingsymbol": "TATASTEEL22JUL1100CE",
    "exchange": "NFO",
    "span": 110720.745,
    "exposure": 38580.990000000005,
    "option_premium": 0,
    "additional": 0,
    "bo": 0,
    "cash": 0,
    "var": 0,
    "pnl": {
    "realised": 0,
    "unrealised": 0
    },
    "leverage": 1,
    "total": 149301.735
    },
  • SRIJAN
    SRIJAN edited July 2022
    @rakeshr Sir,

    In the morning,the exposure was actually showing 0 for the basket shown by @shbhnkr .

    Also,the exposure was showing 0 for just the call short position(Tatasteel 1100CE).

    I had made a test basket on Kite too consisting of index options ,on Friday to check something. On Friday,the required margin was around 30k,but today morning when market opened, around 9:30,the required margin dropped to below 10k(that was below the max loss of 12k of that basket),I guess that was also due to the exposure margin being 0 at that point of time .

    Why did the exposure drop to 0 in the morning??
  • sujith
    There was some issue in the morning yesterday and it was fixed later.
  • SRIJAN
    @sujith Sir,

    Thank you for the clarification. :)
Sign In or Register to comment.