Bitcoin Forum
December 14, 2017, 07:21:54 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: https://data.mtgox.com/api/0/info.php gone?  (Read 612 times)
monsterer
Legendary
*
Offline Offline

Activity: 1008


View Profile
May 15, 2013, 07:33:27 AM
 #1

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.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513236114
Hero Member
*
Offline Offline

Posts: 1513236114

View Profile Personal Message (Offline)

Ignore
1513236114
Reply with quote  #2

1513236114
Report to moderator
qxzn
Hero Member
*****
Offline Offline

Activity: 604



View Profile
May 15, 2013, 04:32:29 PM
 #2

Yep, I saw it too. Switched to api version 1.
monsterer
Legendary
*
Offline Offline

Activity: 1008


View Profile
May 15, 2013, 04:42:07 PM
 #3

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
Sr. Member
****
Offline Offline

Activity: 246


View Profile
May 15, 2013, 04:45:49 PM
 #4

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.

Donations: 1Q2EN7TzJ6z82xvmQrRoQoMf3Tf4rMCyvL
MtGox API v2 Unofficial Documentation: https://bitbucket.org/nitrous/mtgox-api/overview
MtGox API v2 Unofficial Documentation Forum Thread: https://bitcointalk.org/index.php?topic=164404.0
monsterer
Legendary
*
Offline Offline

Activity: 1008


View Profile
May 15, 2013, 05:15:22 PM
 #5

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
Donator
Legendary
*
Offline Offline

Activity: 1218


Gerald Davis


View Profile
May 15, 2013, 05:18:46 PM
 #6

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
Legendary
*
Offline Offline

Activity: 1008


View Profile
May 15, 2013, 05:20:48 PM
 #7

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 Smiley
nitrous
Sr. Member
****
Offline Offline

Activity: 246


View Profile
May 15, 2013, 08:07:21 PM
 #8

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 Smiley

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 Smiley

Donations: 1Q2EN7TzJ6z82xvmQrRoQoMf3Tf4rMCyvL
MtGox API v2 Unofficial Documentation: https://bitbucket.org/nitrous/mtgox-api/overview
MtGox API v2 Unofficial Documentation Forum Thread: https://bitcointalk.org/index.php?topic=164404.0
monsterer
Legendary
*
Offline Offline

Activity: 1008


View Profile
May 15, 2013, 08:15:55 PM
 #9

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 Smiley

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.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!