Author

Topic: Warning: Cryptsy public API returning stale data. Don't rely on it! (Read 427 times)

newbie
Activity: 26
Merit: 100
from what i know many times cryptsy api is late in 60 min or even more
because of this unprofessional state in crypto world (not just cryptsy but many other exchanges) ppl cant run proper bots
legendary
Activity: 2268
Merit: 1092
API's working again.

Good to hear.

Was a bit odd that the ticket was closed without response, not even a first level "we've passed it on to our specialists" reply.
newbie
Activity: 20
Merit: 0
API's working again.
newbie
Activity: 20
Merit: 0
fetch some data from cryptsy's public api and have a look at the "lasttradetime".
last update: 2015-12-04...
 
I have checked a few markets so far. It's all down...

e.g.: Market 2 (BTC/USD):

http://oi64.tinypic.com/2dhtoc1.jpg

The URL is: http://pubapi2.cryptsy.com/api.php?method=singlemarketdata&marketid=2

full member
Activity: 150
Merit: 100
He's right i been trying to pull DASH / BTC price for a few days and it steady at 0.006538 but when you goto the site actual price is 0.005867

Executed some trades that I wouldnt have otherwise because of this....THANKS CRYPTSY!!!!
legendary
Activity: 2268
Merit: 1092
Just a warning that the Cryptsy public API is completely broken; it is returning the exact same stale data each time. If you're using software which fetches order book and market data using this API, you're gonna have a bad time. It was because of a loss that I incurred that I noticed the problem.

I have personally observed the same data returned from http://pubapi2.cryptsy.com/api.php?method=orderdata (MD5 ea6f1a947a1bb124e11044198c809447) for about 36 hours, but I expect that the data is from at least a few days ago, possibly even more than a week (this is meant to be a live API!)

From a Linux/BSD commandline the following will fetch the data and report the MD5. Try it yourself:

Code:
wget -O - "http://pubapi2.cryptsy.com/api.php?method=orderdata" | md5sum

My ticket reporting this issue was open for a couple of days, then it was quietly closed without any response. You can draw your own conclusions from that.
Jump to: