Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs
    1. Home
    2. jayagogwani
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 7
    • Best 0
    • Groups 0

    jayagogwani

    @jayagogwani

    1
    Reputation
    3
    Profile views
    7
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    jayagogwani Unfollow Follow

    Latest posts made by jayagogwani

    • RE: Issue with placeOrder API showing Bad Request for some NFO tokens

      Hello, What's an Ans my last question

      posted in C#/.Net SDK
      J
      jayagogwani
    • RE: Issue with placeOrder API showing Bad Request for some NFO tokens

      Okay, thanks for your response.
      But the F&O stocks are not getting placed. For example, I tried using the token ‘107755’ for ‘HDFCBANK25NOV25930CE’, and I’m creating the payload exactly the same way as I shared with you earlier.
      We’ve also purchased multiple F&O stocks, but the orders are still not being placed.

      posted in C#/.Net SDK
      J
      jayagogwani
    • RE: Issue with placeOrder API showing Bad Request for some NFO tokens

      Ok Thank you for reply
      Do the stock symbols in your OpenScript master JSON file change every day?
      If yes, is there any Angel One API available that provides updated stock prices along with token and symbol names properly?

      posted in C#/.Net SDK
      J
      jayagogwani
    • Issue with placeOrder API showing Bad Request for some NFO tokens

      Hi Angel One Team,

      I’m facing an issue while placing orders through the SmartAPI https://apiconnect.angelone.in/rest/secure/angelbroking/order/v1/placeOrder endpoint.
      The same API works fine for most symbols, but for some NFO option tokens it returns “400 Bad Request” with no proper error message in the response.

      Here’s an example payload that fails:

      {
      "variety": "NORMAL",
      "tradingsymbol": "FINNIFTY28OCT2527600PE",
      "symboltoken": "57121",
      "transactiontype": "BUY",
      "exchange": "NFO",
      "ordertype": "MARKET",
      "producttype": "NRML",
      "duration": "DAY",
      "price": "0",
      "squareoff": "0",
      "stoploss": "0",
      "quantity": "65"
      }

      I’ve already checked:

      Token and symbol are from the latest OpenAPIScripMaster.json
      All headers (API key, Bearer token, IP, MAC, etc.) are correctly added
      Other tokens work fine using the same setup
      Could you please confirm why some tokens return 400 with no message?
      Is it due to token expiry, contract restriction, or product type issue?
      Also, can you help me get more detailed error logs for debugging?

      Client ID: J241150
      Platform: .NET (C#)

      Thanks,
      Jaya gogwani
      jayagogwani1730@gmail.com

      posted in C#/.Net SDK
      J
      jayagogwani
    • RE: Issues with placing orders via Angel One API (Cautionary stocks / Symbol-token mismatch)

      @admin Thanks for the reply...the link and the suggestion which you provided to me provided already we have done. Still we are getting mismatch error. Please find the below message which we are receiving
      "data": null,
      "isSuccess": true,
      "errorMessage": "The order cannot be processed as the token is categorised under cautionary listings by the exchange."
      },

      Where i can find " Surveillance Indicator new" api to fetch daily data ...So that we can put it in our application

      posted in C#/.Net SDK
      J
      jayagogwani
    • Issues with placing orders via Angel One API (Cautionary stocks / Symbol-token mismatch)

      Hello Angel One Support Team,

      I am facing repeated issues while placing orders through the Angel One API for certain stocks, such as IDEA-EQ (symbol token: 14366) on NSE.

      The API sometimes returns the following errors even when all details are correctly filled:
      1. "The order cannot be processed as the token is categorised under cautionary listings by the exchange."
      2. "Entered trading symbol and symbol token is mismatch" (AB1019)

      I would like to understand:
      1. Why certain stocks are categorized under cautionary listing and if they will be tradable in the future.
      2. Why the symbol-token mismatch occurs even when the correct symbol and token are used.
      3. If there is any way to programmatically check both the cautionary status and correct symbol-token mapping before placing an order via API to avoid these failures.

      Request you to provide guidance or resolution so that these repeated order issues can be avoided.

      Thank you,
      Jaya Gogwani
      Client ID: J241150
      Email: jayagogwani1730@gmail.com

      posted in C#/.Net SDK
      J
      jayagogwani
    • Bad Request

      Hey,

      I am using the getRMS call using the postman but receiving "bad request" response. Like below

      angel.PNG .

      So can you please let me know what I am doing wrong here.

      posted in General Discussion
      J
      jayagogwani