BitShares Forum
Main => General Discussion => Topic started by: clout on April 28, 2015, 09:03:13 pm
-
One of the things I've been most confused about is why there is no api for the internal exchange accessible from the web. With ripple and stellar you can easily make request to their server and build applications that integrate these payment networks. If we want people to develop apps using BitUSD or create better wallets and exchange interfaces, isn't this necessary? To that end, I think that all gateways and bridges should also have an api that developers can use. It doesn't make sense to me that blocktrades.us does haven't a public api.
-
One of the things I've been most confused about is why there is no api for the internal exchange accessible from the web. With ripple and stellar you can easily make request to their server and build applications that integrate these payment networks. If we want people to develop apps using BitUSD or create better wallets and exchange interfaces, isn't this necessary? To that end, I think that all gateways and bridges should also have an api that developers can use. It doesn't make sense to me that blocktrades.us does haven't a public api.
EDIT: I get it, you mean a public one, versus setting up your own. I think that is something the new referral system is intended to take care of. If I build it now, I don't see any profit. But with a referral system, I get a cut of the fees of people that use my gateway, so I have an incentive to build it.
original post:
There is:
https://github.com/BitShares/bitshares/wiki/Design-of-RPC-API-methods
example with python:
https://bitsharestalk.org/index.php?topic=13628.0
i'm using it with a bot I wrote based on:
https://github.com/xeroc/bitshares-pytools/
more examples of the API are there above
-
To that end, I think that all gateways and bridges should also have an api that developers can use. It doesn't make sense to me that blocktrades.us does haven't a public api.
We do have an API, and we're more than willing to share it with anyone who wishes to access it, we just haven't formally published it yet as it's subject to potentially rapid evolution right now, but that will certainly happen. It's at a lower priority level right now because there hasn't yet been a lot of interest expressed in accessing at the API level, but we did just recently send one of the forum members information on how to make calls to get current pricing and suggested deposit limit info.
-
https://metaexchange.info/apiDocs
-
... and there will be websocket implemented in the core client aswell .. foundations have been coded already .. I just don't know yet how to use it ..