Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs

    Estimate Charges API suddenly failing for Options/Derivatives (was working earlier)

    General Discussion
    1
    1
    12
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      kondapalli6148 last edited by

      Hi Team,

      I am using the Estimate Charges API in SmartAPI. It used to work for options/derivatives, but for the past few days, it started failing.

      function that i used:

      def transaction_cost_of_ticker(session):
          # Try different symbol formats
          params = {
              "orders": [{
                  "product_type": "INTRADAY",
                  "transaction_type": "BUY", 
                  "quantity": "75",
                  "price": "300",
                  "exchange": "NFO",
                  "symbol_name": "NIFTY",  # Original format
                  "token": "58901"
              }]
          }
          response = session.estimateCharges(params)
          summary_total = response["data"]["summary"]["total_charges"]
          print(f"Estimated charges: ₹{summary_total}")
          return summary_total
         
      session, _ = initialize_session()
      transaction_cost_of_ticker(session)
      

      Error Message:
      'Symbol Not Found', 'errorcode': 'AB1009', 'status': False, 'data': None}

      Environment Details:
      OS: Windows 10
      Python: 3.9
      SmartAPI SDK: smartapi-python==1.4.8

      Observation:

      • API works fine for Equity.
      • API fails for Options, which worked earlier.
      • Payload format has not changed.

      Request:

      • Could you please check if there has been any recent change in the Estimate Charges API affecting options/derivatives?

      • Also, please suggest the correct payload or workaround if this is an issue on your side.

      Thanks,
      kondapalli

      1 Reply Last reply Reply Quote 0
      • First post
        Last post