Kite publisher not working after migration to Kite 3.0

i'm facing the same issue. i use javascript to bind the orders to buttons on the dom (kiteconnect.add, kiteconnect.link)

Can you paste your basket code?

cstext1.Append(" ");
cstext1.Append("");
cstext1.Append("KiteConnect.ready(function() {");

cstext1.Append(" var kite = new KiteConnect(\"kitedemo\");");


cstext1.Append("kite.add({");
cstext1.Append("\"exchange\": \"NSE\",");
cstext1.Append("\"tradingsymbol\": \"" + item["StockName"].ToString() + "\",");
cstext1.Append("\"quantity\": \"" + Qty + "\",");
cstext1.Append("\"transaction_type\": \"" + item["Signal"].ToString() + "\",");
cstext1.Append("\"product\": \"MIS\",");
cstext1.Append("\"order_type\": \"MARKET\",");
cstext1.Append(" });");

cstext1.Append("kite.add({");
cstext1.Append("\"exchange\": \"NSE\",");
cstext1.Append("\"tradingsymbol\": \"" + item["StockName"].ToString() + "\",");
cstext1.Append("\"quantity\": \"" + QtySL + "\",");
cstext1.Append("\"transaction_type\": \"" + SLSignal + "\",");
cstext1.Append("\"product\": \"MIS\",");
cstext1.Append("\"trigger_price\": \"" + SLTrigger + "\",");
cstext1.Append("\"order_type\": \"SL-M\",");
cstext1.Append(" });");



cstext1.Append(" kite.renderButton(\"#default-button\");");
cstext1.Append("kite.link(\"#custom-button\");");
cstext1.Append(" });");


cstext1.Append("");

Hey Guys ... after a lot of debugging ... i figured it out ... basically ... in the earlier version of the API ... your code have sent the prices / trigger price in string format with double quotes. And it still used to work just fine.

I guess with the new version of the code ... the integer / double check is enforced somewhere at the app layer. API remains the same.

Just remove the double quotes around prices or any trigger price and it would work like a charm ...

Fix now ... thank me later ;-)

One more Issue We cannot Place the MIS Orders in Kite Publisher all orders are going as CNC

@cdesai1987,
The backend has become robust now, it expects a proper type. We are sorry for the inconvenience. The only solution here is to send the typed params as in number as number and string as a string.

We are looking into this.

@abhivin123,
This should be fixed now. Can you check and update about the same?