MtGox API version 2: Unofficial Documentation

[TimJBenham]

all I want right now is to monitor and issue a sell order in case of a large drop   kinda weird that isn't a standard feature yet through the web interface.

Yeah, it's weird that the big exchanges don't support standard exchange features such as order limits, short selling and margin trading.

In most markets those are broker features, not exchange features.

[1713994604]

1713994604

[1713994604]

1713994604

[1713994604]

1713994604

[brox]

Typo:

comprised <- compromised
completed useless, currently <- completely useless, currently

[MikeH]

Typo:

comprised <- compromised
completed useless, currently <- completely useless, currently

got the right thread?

[nitrous]

Typo:

comprised <- compromised
completed useless, currently <- completely useless, currently

Thanks, fixed

got the right thread?

He was pointing out typos in the documentation

[Viceroy]

all I want right now is to monitor and issue a sell order in case of a large drop   kinda weird that isn't a standard feature yet through the web interface.

Yeah, it's weird that the big exchanges don't support standard exchange features such as order limits, short selling and margin trading.

In most markets those are broker features, not exchange features.

Please consider contributing such ideas to this post:  https://bitcointalk.org/index.php?topic=179147.0

[baracuda]

At the end of the document, money/wallet/history has an optional parameter of page (in addition to the required currency parameter already listed.)

[nitrous]

At the end of the document, money/wallet/history has an optional parameter of page (in addition to the required currency parameter already listed.)

Thanks, the ones at the bottom I haven't got around to investigating yet so the only information is what I found on the official documentation, so any information is very helpful I've published what I could find out for the method. Have you confirmed this parameter works? I don't have more than 50 transactions in any of my wallets so I can't test it myself.

[nitrous]

Just added some brief information about streaming here - https://bitbucket.org/nitrous/mtgox-api/src/master/socket, including a basic websocket client for quick testing. Also documented the `stream/list_public method`. Note that I have not actually documented any of the actual streaming API, as the bitcoin wiki has a very good page on it themselves - https://en.bitcoin.it/wiki/MtGox/API/Streaming.

[advanced]

thanks!

[advanced]

I finally got some spare time to put together a small repo for documenting the Java Client.
Hope it helps. Thank you guys.

https://github.com/adv0r/mtgox-api-v2-java

[nitrous]

I finally got some spare time to put together a small repo for documenting the Java Client.
Hope it helps. Thank you guys.

https://github.com/adv0r/mtgox-api-v2-java

Thanks, that's great work, I linked it in my API examples section

[advanced]

You are welcome, thanks for the good words you used

PS: Today I observed another unexpected behaviour of the APIs. You cannot access the method MONEY/BITCOIN/SEND_SIMPLE if you are using an yubikey. Not even if you gave permissions to the API keys.  This is weird : i mean, i need the yubikey to login into my account, but this is not stopping me to be able to place orders via API. I opened a ticket on mtg.

 

[nitrous]

You are welcome, thanks for the good words you used

PS: Today I observed another unexpected behaviour of the APIs. You cannot access the method MONEY/BITCOIN/SEND_SIMPLE if you are using an yubikey. Not even if you gave permissions to the API keys.  This is weird : i mean, i need the yubikey to login into my account, but this is not stopping me to be able to place orders via API. I opened a ticket on mtg.

No problem, it's important to add a spectrum of examples, from quite simple to more sophisticated, to help people get started and then improve their projects, as well as having multiple languages

Thanks, I've updated the docs to note this. Update me if you get an official response, as it does make sense for it to be denied with yubikey enabled, but it is indeed inconsistent.

[IIzzII]

Can someone help me out, I feel like I'm going crazy here. I've been reading your documentation (which is great, by the way) and I can't seem to make even the basic calls work predictably. I'm trying to get some historical data. For testing reasons, I've started at 'since=0'. This url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=0

properly returns trades. The timestamp of the first trade is "1279408157" which is a date of  07/17/10 @ 6:09:17pm. The timestamp of the last trade is "1282128968" which is a date of 08/18/10 @ 5:56:08am EST. Now if I take that last timestamp and attach that to the url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=1282128968

the first timestamp of the first trade is "1309108565" which is a date of 06/26/11 @ 12:16:05pm EST. I've also tried using microseconds as suggested by the api but that returns the same thing. The url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=1282128968000000

returns the same thing as above. I've tried other timestamps from the first response and the all point to this 06/25/11 set of trades.

Any idea what I'm doing wrong?

[TimJBenham]

Not exactly a V2 issue but https://data.mtgox.com/api/1/BTCUSD/ticker_fast just started failing for me with the error "This query needs to be done via data.mtgox.com". It gives an endless redirect loop. Is it still working in V2?

[TimJBenham]

Looks like it's working again. Possible Cloudfare false positive?

[nitrous]

Can someone help me out, I feel like I'm going crazy here. I've been reading your documentation (which is great, by the way) and I can't seem to make even the basic calls work predictably. I'm trying to get some historical data. For testing reasons, I've started at 'since=0'. This url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=0

properly returns trades. The timestamp of the first trade is "1279408157" which is a date of  07/17/10 @ 6:09:17pm. The timestamp of the last trade is "1282128968" which is a date of 08/18/10 @ 5:56:08am EST. Now if I take that last timestamp and attach that to the url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=1282128968

the first timestamp of the first trade is "1309108565" which is a date of 06/26/11 @ 12:16:05pm EST. I've also tried using microseconds as suggested by the api but that returns the same thing. The url:

https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch?since=1282128968000000

returns the same thing as above. I've tried other timestamps from the first response and the all point to this 06/25/11 set of trades.

Any idea what I'm doing wrong?

Hmm, that's very strange, it seems to work for dates after 1309108565, but not for the data gap between. I'll have to have another look later when I have some more time, but for now maybe just try from 1309108565 instead. Sorry about that, I may need to contact mtgox and see if they can help.

[nitrous]

Looks like it's working again. Possible Cloudfare false positive?

Could be. At times of high lag/DDoS, the API can stop working properly, and it can result in undefined behaviour.

[advanced]

currently you can get the last price of 1 BTC from 4 sources. might be worth comparing them  and plot them for a testing period.this way we could check inconsistencies . Someone up for this?

[IIzzII]

Sorry about that, I may need to contact mtgox and see if they can help.

You don't need to apologize! I'll see if I can get it to work from that date on. Thanks so much.

UPDATE: It seems to be working fine as long as you don't provide a timestamp before 1309108565.