@Moderator_3 Can you please update on the issue
Posts made by nitish.bane
-
RE: Max Days in historical data
@Moderator_3 Please find the curl below
curl --location 'https://apiconnect.angelone.in/rest/secure/angelbroking/historical/v1/getCandleData'
--header 'X-ClientLocalIP: 192.168.200.129'
--header 'X-ClientPublicIP;'
--header 'X-MACAddress;'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer Token'
--header 'X-PrivateKey: 3J9h3Ukp'
--header 'X-SourceID: WEB'
--header 'X-UserType: USER'
--header 'Cookie: TS0179ac75=0167ca9f9b63a06781743099d6697bce61dc9aa8211897f10c1005ebdd27b3c45b539edb25cc338e3493a9a7f806186d58b17e335d'
--data '{
"exchange": "NSE",
"symboltoken": "99926000",
"interval": "FIVE_MINUTE",
"fromdate": "2024-07-29 09:15",
"todate": "2024-09-20 15:30"
}
'
I am querying from 29 july 2024 to 20 sept 2024 for 5 min interval data. But I am getting response date starting from 14th Aug. Please find the snap below
-
Max Days in historical data
Hi Smart Api Team,
Are there any changes introduced in the max days that can be queried with Historical api?
I am not able to fetch 100 days data for 5 Min interval and 30 Days data for 1 Min interval. It used to work earlier. Can you please check.Thanks.
-
RE: Create basket order
@Moderator_1 How would margin calculation/requirement work in that case?
Does it takes into account of the live orders? -
Create basket order
Hi @Moderator_1 @Moderator_2
How to create basket orders with smart api? -
RE: Issue with tick data when large number of tokens are subscribed
@Moderator_1 @Moderator_2 @admin123 Any update on the issue? I am not able to launch my strategy because of this
-
RE: Option Greeks
@Mnagesh Do you know how can we calculate option greeks at our side? I need to for past expiry for back testing purpose
-
RE: Announcing Option Greeks API for SmartAPI Users
@Moderator_1 @Moderator_2 Can you share the logic or code you are using to calculate the option greek. I need options greeks for past expiries but it is not provided by api.
-
RE: Issue with tick data when large number of tokens are subscribed
@DevPatel You need to use historical data or use getCandleData method from sdk.
getCandleData({
"exchange": exchange,
"symboltoken": symboltoken,
"interval": interval,
"fromdate": fromdate,
"todate": todate
}) -
RE: Issue with tick data when large number of tokens are subscribed
@Moderator_2 I am just using the tick data to create candles. It is working fine for index tokens i.e for Nifty and Bank Nifty candles are matching with angel candles. However when I subscribe to large number of tokens there is delay observed in getting the ticks. I am getting one tick as part of one websocket response. I think websocket should contain data as an array of tokens subscribed.
-
RE: Announcing Option Greeks API for SmartAPI Users
@Moderator_1 The option greeks provided by angel one does not match with that of sensibull. Do you know why is that happening and which one would be correct?
-
RE: Web Socket Issues
@perceptron I think there is some issue with websockets when more number of tokens are subscribed. I facing a similar problem where I am subscribing to 200 tokens and I am observing delays in receiving ticks.
-
RE: Issue with tick data when large number of tokens are subscribed
Hi @Moderator_1 @Moderator_2 Can you please look into this issue? I beleive websocket only works if we subscribe to less number of tokens. There are delays observed in ticks if we subscribe to more tokens. Please correct me if I am wrong
-
RE: Issue with tick data when large number of tokens are subscribed
@DevPatel Feed type should be the feed token you receive from authentication response
-
RE: Issue with tick data when large number of tokens are subscribed
@DevPatel Please find the cide below
let {WebSocketV2} = require('smartapi-javascript');
let web_socket = new WebSocketV2({
jwttoken:jwtToken, // replace this with your own credentials
apikey: apiKey,
clientcode: clientId,
feedtype: feedToken,
});
web_socket.connect().then((res) => {
let json_req = {
correlationID: 'abcde12345',
action: 1,
mode: 2,
exchangeType: 1,
tokens: ["99926009","99926000"]// token for nifty and bank nifty
};web_socket.fetchData(json_req); web_socket.on('tick', receiveTick);
function receiveTick(data) { // your code to process tick data
} -
RE: Issue with tick data when large number of tokens are subscribed
@jaideep-siddula I am developing a strategy where I need to select a strike price based on a premium criteria. There are two ways of doing it. Subscribe to all strike prices of an index to get premum prices or use market data api. I am trying the first way out so that I can develop any strategy in the future that may work on premium chart
-
RE: Issue with tick data when large number of tokens are subscribed
@Moderator_1 @Moderator_2 @admin Can some one please help here?
-
RE: Issue with tick data when large number of tokens are subscribed
@chetansuri Even if I consider that case it should not exceed limit of 1000 tokens as I am only subscribing for all strike prices of bank nifty which counts for 198 tokens.
-
Issue with tick data when large number of tokens are subscribed
Hi Team,
I am subscribing to all strike price of bank nifty which tallies to 198 tokens in one websocket connection. I am observing an issue where I am not receiving intermediate ticks for the each strike price because of which there is a discrepancy in the candle data that I am creating at my end. Please find the websocket request for 198 tokens for the current expiry.
{
correlationID: "abcde12345",
action: 1,
mode: 2,
exchangeType: 2,
tokens: [
"53955",
"39011",
"54061",
"53867",
"54132",
"54320",
"53925",
"54029",
"54108",
"54191",
"47787",
"48448",
"49231",
"54069",
"54030",
"53816",
"53949",
"53847",
"54059",
"39013",
"54135",
"39010",
"53822",
"53982",
"53812",
"53887",
"54065",
"53967",
"48446",
"54060",
"54031",
"54323",
"53948",
"54106",
"53869",
"53898",
"53995",
"53831",
"54087",
"47772",
"47785",
"53950",
"53863",
"39012",
"53823",
"54002",
"53921",
"54063",
"54289",
"54109",
"53944",
"53934",
"54033",
"53985",
"53952",
"53896",
"53854",
"48451",
"54159",
"53941",
"54151",
"54287",
"54011",
"53951",
"54016",
"47786",
"54009",
"54051",
"53888",
"53923",
"54175",
"54221",
"54064",
"53912",
"48447",
"53963",
"47784",
"54092",
"54150",
"39008",
"54077",
"53832",
"54164",
"53926",
"54298",
"54163",
"53840",
"54167",
"45999",
"53984",
"54321",
"54134",
"39028",
"53806",
"53821",
"49223",
"54112",
"54111",
"54160",
"47758",
"54076",
"53924",
"54257",
"39799",
"53833",
"39027",
"53834",
"54123",
"54062",
"39009",
"54007",
"54176",
"54146",
"53820",
"54070",
"47771",
"49232",
"53983",
"53922",
"54003",
"39800",
"53852",
"53870",
"54006",
"54179",
"54130",
"53932",
"54068",
"54299",
"54169",
"54027",
"53803",
"53864",
"53897",
"53902",
"54045",
"53935",
"54131",
"53865",
"54220",
"54066",
"53876",
"54168",
"47759",
"53853",
"54322",
"54067",
"54094",
"53866",
"54017",
"53956",
"53958",
"53962",
"54129",
"54177",
"39029",
"54192",
"54288",
"48444",
"53964",
"53851",
"54128",
"54028",
"53877",
"53807",
"48445",
"54309",
"53859",
"53868",
"53813",
"53965",
"54161",
"54162",
"53805",
"53804",
"53947",
"53848",
"54071",
"53966",
"54004",
"39014",
"53994",
"53961",
"54052",
"54310",
"45996",
"54010",
"54319",
"54136",
"54258",
"54093",
"54026",
"49228",
"54032",
"54133",
"54046",
"53913",
"53957",
],
}Please note that tick data is working perfectly fine when I subscribe only to Nifty and Bank nifty index tokens.
-
RE: Historic API not working
Looks like issue is resolved now. I am able to pull historical data. Thanks @admin