The opinions expressed in these forums do not represent those of C2, and any discussion of profit/loss is not indicative of future performance or success. There is a substantial risk of loss in trading. You should therefore carefully consider whether such trading is suitable for you in light of your financial condition. You should read, understand, and consider the Risk Disclosure Statement that is provided by your broker before you consider trading. Most people who trade lose money.
I use Data Service API to get certain data for my investigation of trading systems quality. Today and last couple days this API didn’t work well. I am able to get session ID, close the session, but system roster request gives Bad gateway error in my software. Also I can’t retrieve systems roster in browser - Collective2 is unreachable.
I am wondering if any changes were made in Data Service API?
Hi, Andrey:
We switched to all-SSL today, and perhaps that is the cause of the API issue. Would you mind sending over to our help desk specific examples of the service calls that didn’t work for you, and we’ll take a look ASAP. help@collective2.com
Hi, Andrey:
We think we fixed this problem. Can you give it a try and let us know? Feel free to report back privately via help@collective2.com, or let us know here in the forums.
Matthew
Hi Andrey,
Some additional fixes have been applied.
Please try again now and let us know about the results.
Also, please make sure you are using https calls.
Thanks.
Hello again 
Thank you for your efforts. I’ve run my code and got the following: I can get particular system stats, equity, trades and signals using data service API as described in your pdf file. Only systems roster request returns errors almost every time, if I use it according to the API instruction.
I am not an advanced programmer, so I am not sure that I understand correctly “https calls” remark from Vladimir. If it means just changing “http” to “https” in API request string, then it still doesn’t work. If it means new function usage in python, then I need some time to evaluate this approach.
One way to resolve the problem, which I’ve incorporated, was to request system roster number of times with 5-6 sec between each failed request. Usually 6th-8th request works and I get data that I need.
Hi, Andrey:
That doesn’t seem like a really great solution. How about if I try to fix whatever the problem is (if it’s on my side) or, alternately, tell you how to fix it (if it’s on your side)?
Please do the following. Please gather a log of your exact api calls and the exact C2 responses, and then email them to the Help Desk (help@collective2.com) and we’ll take a look and figure out what’s going on.
Matthew
Everything works great now. All data available from first request. Thanks for your help.
By the way, one question is showed up during recent updates: is it possible to identify using data API responses, if the system still actual and serves signals or it was closed?
