Please check out this thread on twitter
https://twitter.com/TrueData2/status/1464819209783758848?s=20
https://twitter.com/TrueData2/status/1464819209783758848?s=20
Twitter
Kapil Marwaha 🇮🇳
Simulated feeds - Feed replay Live from today. Now ditto time stamp feeds on weekends as on Friday. Meaning at 10:15:02, you will get the same streaming ticks which came at this same time on Friday. Please use ur login with port 6082 to access the live simulated…
Important Information about the Previous Close Updates via the API
All are requested to please go through pages 13 & 14 of the PDF raw feed API documentation.
The Previous close which comes from the exchange comes with every tick in the real time feed. (Page 14 of Doc). Please make sure that you use this as your main reference for the 'Previous Close'. (in case you are not using our Libraries)
The 'Previous Close' which comes in the touchline is populated by us from the NSE Bhavcopy which comes in our feed and is correct 99% of the times and can be used as a good starting point. On some rare cases, the NSE does not update the Bhavcopy in time, and then the rates may come in late causing issues of the Previous Close not being updated and remaining that of the previous date.
You can continue using the Previous close from the Touchline if you are doing so now, however, you need to refer the Previous Close which comes in the real time feed also, to make sure that the Prev Close is updated properly.
The Previous Close coming in the Real time feed with each tick should be considered as the master.
All are requested to please go through pages 13 & 14 of the PDF raw feed API documentation.
The Previous close which comes from the exchange comes with every tick in the real time feed. (Page 14 of Doc). Please make sure that you use this as your main reference for the 'Previous Close'. (in case you are not using our Libraries)
The 'Previous Close' which comes in the touchline is populated by us from the NSE Bhavcopy which comes in our feed and is correct 99% of the times and can be used as a good starting point. On some rare cases, the NSE does not update the Bhavcopy in time, and then the rates may come in late causing issues of the Previous Close not being updated and remaining that of the previous date.
You can continue using the Previous close from the Touchline if you are doing so now, however, you need to refer the Previous Close which comes in the real time feed also, to make sure that the Prev Close is updated properly.
The Previous Close coming in the Real time feed with each tick should be considered as the master.
AWS Issue Today
Issue with AWS today. Network seems intermittent. On and Off. If any of you on AWS you would have faced the issue.
We are not on AWS and not faced any issue with the distribution. All those not on AWS would not have faced any Issue.
Issue with AWS today. Network seems intermittent. On and Off. If any of you on AWS you would have faced the issue.
We are not on AWS and not faced any issue with the distribution. All those not on AWS would not have faced any Issue.
Python Library Updated Version 4.2.1 (minor update)
-Requirements updated (lz4 Library pivoted to version 3.1.3 due to build issue in new version)
-Callback sample codes added to Readme
-Requirements updated (lz4 Library pivoted to version 3.1.3 due to build issue in new version)
-Callback sample codes added to Readme
Market Data API Planned Maintenance Completed Successfully!
We are extremely glad to inform you that, our Real-Time, Historical Data and Replay Feed servers maintenance has gone through successfully.
After monitoring our setup, we would like to confirm that the services have now resumed fully and in all respects.
NOTE: Replay Feed is working fine right now and you can use it and it would work tomorrow as well.
We are extremely glad to inform you that, our Real-Time, Historical Data and Replay Feed servers maintenance has gone through successfully.
After monitoring our setup, we would like to confirm that the services have now resumed fully and in all respects.
NOTE: Replay Feed is working fine right now and you can use it and it would work tomorrow as well.
Replay feed is NOW Available & Activated for all Active Subscribers
url = 'replay.truedata.in'
realtime_port = 8082
Replace the url - push.truedata.in to replay.truedata.in
Port remains the same - 8082
For python library users... use this...
repl
Nodejs library is now updated
Replay enabled. Downloaded latest version > https://www.npmjs.com/package/truedata-nodejs
url = 'replay.truedata.in'
realtime_port = 8082
Replace the url - push.truedata.in to replay.truedata.in
Port remains the same - 8082
For python library users... use this...
repl
ay_url = 'replay.truedata.in'r C# Users... just this one change...
realtime_port = 8082
td_obj = TD(username, password, live_port=realtime_port, url=replay_url)
Fo
tDWebSocket = new TDWebSocket("user_id", "user_pwd", "wss://replay.truedata.in", 8082);
Nodejs library is now updated
Replay enabled. Downloaded latest version > https://www.npmjs.com/package/truedata-nodejs
rtConnect(user, pwd, symbols, port, bidask = 1, heartbeat = 1, replay = 1);
replay > 1 = Feed replay, 0 = Normal feed ( default - If parameter not entered then replay = 0 )
Intermittent issues with Historical Data
We are facing issues with historical data downloads / distribution intermittently every 3-4 hours. The issue gets resolved every time it happens, but currently needs manual intervention from us for the resolution.
We are monitoring the feed and are working overtime to try to find a permanent solution for the same soon.
We are extremely sorry for any inconvenience being caused during this period. Appreciate your understanding in the matter.
We are facing issues with historical data downloads / distribution intermittently every 3-4 hours. The issue gets resolved every time it happens, but currently needs manual intervention from us for the resolution.
We are monitoring the feed and are working overtime to try to find a permanent solution for the same soon.
We are extremely sorry for any inconvenience being caused during this period. Appreciate your understanding in the matter.
Python Library Updated
Version 4.2.2
> OI when Null (first few ticks of first time traded options) throws error - Fixed
> Readme Updated with sample codes for Logging, callbacks etc...
> Bugs Removed
To Upgrade >> pip install --upgrade truedata-ws
See Updated Readme at >> https://pypi.org/project/truedata-ws/4.2.2/
Version 4.2.2
> OI when Null (first few ticks of first time traded options) throws error - Fixed
> Readme Updated with sample codes for Logging, callbacks etc...
> Bugs Removed
To Upgrade >> pip install --upgrade truedata-ws
See Updated Readme at >> https://pypi.org/project/truedata-ws/4.2.2/
PyPI
truedata-ws
Truedata's Official Python Package
Rate Limits for Historical Data
We have fine tuned the rate limits to ensure that the service runs smoothly for all. You will need to adjust to these new rate limits for the benefit of all. We will monitor activity with these and fine tune these up or down to ensure smooth availability of the data for all.
For Bar History ( 1 min to EOD )
Per second - 10 requests
Per minute - 600 requests
Per hour - 18,000 requests
For Tick History
Per second - 5 requests
Per minute - 300 requests
Per hour - 18,000 requests
These limits should not normally affect any user, unless you are continuously firing too many requests. Even in that case you can add a brief pause / sleep between a set of requests to keep it smooth.
For any feedback or clarification, please write to support@truedata.in
We have fine tuned the rate limits to ensure that the service runs smoothly for all. You will need to adjust to these new rate limits for the benefit of all. We will monitor activity with these and fine tune these up or down to ensure smooth availability of the data for all.
For Bar History ( 1 min to EOD )
Per second - 10 requests
Per minute - 600 requests
Per hour - 18,000 requests
For Tick History
Per second - 5 requests
Per minute - 300 requests
Per hour - 18,000 requests
These limits should not normally affect any user, unless you are continuously firing too many requests. Even in that case you can add a brief pause / sleep between a set of requests to keep it smooth.
For any feedback or clarification, please write to support@truedata.in
Dear Subscribers,
We are making things better and more robust for you at the backend.
All our Market Data API Servers and Services are getting upgraded and hence, both Real-Time and Historical data servers along with Feed Replay are planned for maintenance on 30th January 2022 from 12:00 AM (midnight) to 8:00 AM (morning).
These services would be available after 08:00 AM IST onwards on 30th January 2022. Please carry out any activity you wish to before the maintenance period.
An update about the completion of the maintenance would also be communicated to you.
Thank You For Your Patience and Cooperation.
We are making things better and more robust for you at the backend.
All our Market Data API Servers and Services are getting upgraded and hence, both Real-Time and Historical data servers along with Feed Replay are planned for maintenance on 30th January 2022 from 12:00 AM (midnight) to 8:00 AM (morning).
These services would be available after 08:00 AM IST onwards on 30th January 2022. Please carry out any activity you wish to before the maintenance period.
An update about the completion of the maintenance would also be communicated to you.
Thank You For Your Patience and Cooperation.
Dear Subscribers,
We are extremely glad to inform you that, our Real-Time, Historical Data and Replay Feed servers maintenance has gone through successfully.
After monitoring our setup, we would like to confirm that the services have now resumed fully and in all respects.
NOTE: All the Feeds are working fine right now and you can use it.
Thank You For Your Patience and Cooperation.
We are extremely glad to inform you that, our Real-Time, Historical Data and Replay Feed servers maintenance has gone through successfully.
After monitoring our setup, we would like to confirm that the services have now resumed fully and in all respects.
NOTE: All the Feeds are working fine right now and you can use it.
Thank You For Your Patience and Cooperation.