https://data.mtgox.com/api/0/info.php gone?

[monsterer]

Hi guys,

Anyone else seeing a missing page error in version 0 api:

https://data.mtgox.com/api/0/info.php

?

I know its going to be deprecated, but the other calls work.

Cheers, Paul.

[1714860017]

1714860017

[1714860017]

1714860017

[1714860017]

1714860017

[qxzn]

Yep, I saw it too. Switched to api version 1.

[monsterer]

Yep, I saw it too. Switched to api version 1.

Damn it. Every time I'm about ready to test my bot live, something new comes along to bite me in the ass!

[nitrous]

Yep, I saw it too. Switched to api version 1.

Damn it. Every time I'm about ready to test my bot live, something new comes along to bite me in the ass!

It might be worth preemptively updating to version 2 so that when version 1 starts to be deprecated you won't be unprepared.

[monsterer]

It might be worth preemptively updating to version 2 so that when version 1 starts to be deprecated you won't be unprepared.

Wise words. Although it does mean changing the authentication hashing thingy... :|

[DeathAndTaxes]

It might be worth preemptively updating to version 2 so that when version 1 starts to be deprecated you won't be unprepared.

Wise words. Although it does mean changing the authentication hashing thingy... :|

Only for private API calls (and version 1 requires it as well).  The only major change between ver1 & ver2 is that version 2 includes the API path in the hash (to prevent substitution attack).  Public API calls (like ticker, depth, or trades) don't require authenitcation at all.

At this point there is absolutely no reason not to use ver2 unless you just enjoy your application breaking in the future.

[monsterer]

Only for private API calls (and version 1 requires it as well).  The only major change between ver1 & ver2 is that version 2 includes the API path in the hash (to prevent substitution attack).  Public API calls (like ticker, depth, or trades) don't require authenitcation at all.

At this point there is absolutely no reason not to use ver2 unless you just enjoy your application breaking in the future.

Actually, the hashing in V0 == V1 for private calls, they changed it in V2, so although I don't enjoy the idea of my bot breaking the in future, I do enjoy the idea of being able to forward test my bot as quick as possible to refine the algorithm, which means using V1 is a doddle compared to V2

[nitrous]

Only for private API calls (and version 1 requires it as well).  The only major change between ver1 & ver2 is that version 2 includes the API path in the hash (to prevent substitution attack).  Public API calls (like ticker, depth, or trades) don't require authenitcation at all.

At this point there is absolutely no reason not to use ver2 unless you just enjoy your application breaking in the future.

Actually, the hashing in V0 == V1 for private calls, they changed it in V2, so although I don't enjoy the idea of my bot breaking the in future, I do enjoy the idea of being able to forward test my bot as quick as possible to refine the algorithm, which means using V1 is a doddle compared to V2

Well if you do get the urge to update, have a look at my unofficial documentation of v2 - https://bitbucket.org/nitrous/mtgox-api/src - it should help you implement the hashing quite easily and there are already code examples in a few languages

[monsterer]

Well if you do get the urge to update, have a look at my unofficial documentation of v2 - https://bitbucket.org/nitrous/mtgox-api/src - it should help you implement the hashing quite easily and there are already code examples in a few languages

Thanks for the heads up - appreciated.

I have to say its absolutely shocking that it has to fall to a 3rd party to document the API calls of a commercial organisation's system.