Open jphackworth opened 10 years ago
So is adding trade support (for all exchanges) is a desired feature? How do you want to manage this as I don't know if the HTTP library you are using provides support for setting the requisite custom headers for most exchanges "secured" API subsets.
As discussed on IRC, my short-term goal is to add public data such as trades and orderbooks.
After reading API docs this afternoon with an eye to feasability, it looks like supporting BTC-E and Cryptsy with a common or shared API is reasonable. Havelock may not fit into the same mould however.
Is that based on having currency exchange pairs, vs. securities exchange fund symbols?
Example trade data url https://btc-e.com/api/2/btc_usd/trades