Clarification on GTT API Static IP and Closing Price Requirements

rajatShah56
rajatShah56 edited 6:33AM in Kite Publisher
Hello,
I have a question regarding Kite Connect GTT APIs:
1. Can `place_gtt`, `modify_gtt` and `delete_gtt` be used without a registered static IP?
2. Can the previous trading session's closing price be used as `last_price` when creating or modifying a GTT, or must it be the current market price?
3. Are GTT operations supported on the free Personal API plan without paid live market data?
Please clarify these requirements.
Thank you.
Tagged:
  • salim_chisty
    1. Can `place_gtt`, `modify_gtt` and `delete_gtt` be used without a registered static IP?
    A static IP is required only for order-placement API requests.GTT operations (place_gtt, modify_gtt and delete_gtt) do not require a registered static IP. Please check the GTT API documentation.
    2. Can the previous trading session's closing price be used as `last_price` when creating or modifying a GTT, or must it be the current market price?
    The last_price field is mandatory when creating or modifying a GTT. It should represent the instrument's last traded price at the time of the request. Using the previous trading session's closing price is not recommended, as it may be stale and can affect GTT validation.
    3. Are GTT operations supported on the free Personal API plan without paid live market data?
    The free Personal API plan does not provide live market data, so it cannot automatically fetch the current LTP. However, you can manually use last_price, as the free plan does not provide live market quotes. For automated GTT management requiring current prices, a paid Kite Connect subscription is recommended. For more details, you may refer to the similar discussion here.
Sign In or Register to comment.