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 -
@jayagogwani The respective symbol token not available from scrip master so before placing request do cross check with scrip master contract json file.
-
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? -
Hi @jayagogwani
Please find angel one scrip master json file link below.
https://margincalculator.angelone.in/OpenAPI_File/files/OpenAPIScripMaster.json
-
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. -
Hello, What's an Ans my last question
-
Hi @jayagogwani
Please share client ID, date & time to get to know more on this issue