Topic: MtGox API version 2: Unofficial Documentation - page 7. (Read 62534 times)
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?
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.
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?
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.
Looks like it's working again. Possible Cloudfare false positive?
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?
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?
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?
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.
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.
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.
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.
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
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
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
Hope it helps. Thank you guys.
https://github.com/adv0r/mtgox-api-v2-java
thanks!
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.
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.
At the end of the document, money/wallet/history has an optional parameter of page (in addition to the required currency parameter already listed.)
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.
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://bitcointalksearch.org/topic/the-next-mt-gox-mtgox-20-179147
Typo:
comprised <- compromised
completed useless, currently <- completely useless, currently
comprised <- compromised
completed useless, currently <- completely useless, currently
Thanks, fixed
got the right thread?
He was pointing out typos in the documentation
Typo:
comprised <- compromised
completed useless, currently <- completely useless, currently
comprised <- compromised
completed useless, currently <- completely useless, currently
got the right thread?
Typo:
comprised <- compromised
completed useless, currently <- completely useless, currently
comprised <- compromised
completed useless, currently <- completely useless, currently
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.
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.
Nitrous, my fault. The fast ticker seem to work with EUR too. I got confused with last_all in the crowded debug console
OT:
I'm actually building a simple trading bot myself if anybody is interested in participating to the beta test, PM me! I already collected 15 volunteers + myself. Of course you should trust it with your life, but this bot here runs locally on your machine. you can see the code yourself and the API keys are stored locally on your machine
Here you can see an example of the readme :> http://www.lize.it/up/prototype-botcoin/
This was how the node version looked like it saved me from big price drops), now I'm doing it better with java.
If any suggestion , please add
OT:
I'm actually building a simple trading bot myself if anybody is interested in participating to the beta test, PM me! I already collected 15 volunteers + myself. Of course you should trust it with your life, but this bot here runs locally on your machine. you can see the code yourself and the API keys are stored locally on your machine
Here you can see an example of the readme :> http://www.lize.it/up/prototype-botcoin/
This was how the node version looked like it saved me from big price drops), now I'm doing it better with java.
If any suggestion , please add
Have you got the JSON decoded yet? You could make debugging easier by pretty-printing it
I've updated the documentation with my findings for the new method so hopefully that will be helpful - although I still haven't been able to test the differences during a high lag period.That sounds interesting
Does it generate the trading strategy automatically or is it user-programmable? I haven't been able to dedicate any large amounts of time to tradebot development but I was planning to incorporate some forex technical indicators, have a look at http://en.wikipedia.org/wiki/MACD for example. It seems fairly accurate (although there is a bit of lag), moreso than simple limit orders. I think bitcoin needs a trading platform to monitor forex technical indicators in order to make more informed trading decisions, especially with the high volatility, you could make a really powerful tool here 
Yes I decoded the JSON and prettified it
The strategy is totally up to the user, I'm not a trading expert my self and I just want to provide a powerful tools to the people. The strategy(.csv) could then be shared among users and exchanged according to domain experties, forex indicators, and others.
I'm myself a follower of the mailing list on bitcoinbullbear.com and I take decisions accordingly, but I'm not a speculator crazy trader
thanks for the feedback!
Jump to: