MTGOX Ticker 403 Error Since Yesterday

[nemercry]

Hello there folks,

i get this error since yesterday and i didnt change anything at the programm. How cna i change this and where does it come from, due that i did not make any changes.

15:02:10.397 [default] [main] DEBUG si.mazi.rescu.HttpTemplate - Executing GET request at http://data.mtgox.com/api/1/BTCUSD/ticker?raw
15:02:10.397 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Request body =
15:02:10.397 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Request headers = {Accept=application/json, Content-Type=application/x-www-form-urlencoded}
15:02:10.398 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Header request property: key='Accept-Charset', value='UTF-8'
15:02:10.398 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Header request property: key='User-Agent', value='ResCU JDK/6 AppleWebKit/535.7 Chrome/16.0.912.36 Safari/535.7'
15:02:10.398 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Header request property: key='Content-Type', value='application/x-www-form-urlencoded'
15:02:10.398 [default] [main] TRACE si.mazi.rescu.HttpTemplate - Header request property: key='Accept', value='application/json'
15:02:10.412 [default] [main] DEBUG si.mazi.rescu.HttpTemplate - Request http status = 403
There was an error at Update Market Data Service.

[timmolter]

This is a classic MtGox move. They change their API almost weekly it seems, breaking everyone's apps. I have verified this 403 response. I've found that using the V2 API in XChnage for MtGox works fine for the ticker. Addmittedly, V2 is still under development in XChange and the account and trade APIs still have an authentication issue.

My suggestion for a quick fix is to use the V2 api using the latest snapshot jars of XChange. I think moving forward, we just need to deprecate V0 and V1 and focus efforts on V2.

[timmolter]

Implemented MtGox V2 polling API: marketdata, account info, and trading!

Changes committed and pushed.

Snapshots deployed.

To stay up to date with the latest information regarding API changes: https://twitter.com/Xeiam