@smartapi-0
hello can you help me to get use websocket 2.0. infact so far failed to use ws even in version1. need some help .i am new coder.

@aabm694602 Checking the issue, meanwhile please use the trading API key for the same purpose.

@prasannkoli16 , Hey there!
Are you perhaps using environment variable to store your api key , client id and topt ?

@jyotsna-patel said in Symbol search stopped working:

@mannsavaliya https://margincalculator.angelbroking.com/OpenAPI_File/files/OpenAPIScripMaster.json

NEW URL THAT WORKS .

@jyotsna-patel
thank you

same issue, any ETA

Response: {'message': 'Internal Error', 'errorcode': 'AB2001', 'status': False, 'data': None}

Getting this error since yesterday.

Team Team,

I cant find the Nifty and BANKNIFTY Futures symbol Token, from the Master API/Jason : https://margincalculator.angelone.in/OpenAPI_File/files/OpenAPIScripMaster.json

I can only see Nifty Futures Token as 5, 13,14 as NIFTY NEAR MONTH, MID MONTH AND FAR MONTH Respectively but i am not able to retrieve any data.

while running my code Its strange that i am not getting any error although the files in blank.

Please note that i am able to get the data for other symbols like Stocks

#SymbolToken

admin 17 Jun 2021, 16:00

HI @anuragbaheti We have noted this we will test this and update you on this.
<h1>sujal</h1>

@sejpalsinh said in Incorrect Websocket Data:

if you found any s

I got to know that Brokers do not provide Tick-by-Tick data. The data provided by AngelOne is aggregated data, provided at almost one second frequency.
So, high or low prices cannot be known by 'last_traded_price'.
There are parameters 'high_price_of_the_day' and 'low_price_of_the_data' in the tick data, but the issue is that it includes pre-opening session data too, so these prices may not represent the high and low prices of the actual trading session.

@Simba007 Please try again and check.

@Subhash_indian were you able to log in previously? The login mechanism is working fine.

please send the API request that you are punching.

@harishgrt 400 bad request would mean the request body is not proper.