[HOW-TO] Exchanges API

[nemgun]

Hello Bitcointalk, i would like to announce you the creation of a repository who will host several tutorials and libraries in PHP and javascript, maybe other languages but i am not sure.

https://github.com/nemgun32/Exchange-API-Tutorial

So from here, i will try to answer to as much questions as i can, and create tutorials for API integration, usage, and interaction, i know that it may had aleready been done, but regarding the popular demand i guess that it will still help.
I don't think that i will cover the private API usage as someone is aleready doing it, but i will do my best for the other parts.

If you are looking for the same on NODEJS, you just need to find a way to do the calls, for the data handling it is exactly the same, i will do NODEJS tutorials when PHP is finished.

-Update:

Added more features to the classes.
Extended examples.
---------------------------
 Now using CURL
 More informations on pages
 Examples

[1715021756]

1715021756

[1715021756]

1715021756

[Joel_Jantsen]

Appreciate the initiative but why limiting the Tutorials to only PHP ? And that is not exactly a tutorial but the actual code which I believe just works.Maybe you could explain the basics and such to know learners what exactly you're doing.

[falala69]

You could add more wrapper like node.js, python, go, ruby and explain their basic usage rather than just a code. Its more useful for anyone that still learning to code.

Here is lib that i used for trex (node.js): https://www.npmjs.com/package/node.bittrex.api and for polo, just simply make a request to their public api 

[nemgun]

i said in the OP that i will start with PHP as it is, well, it is PHP.
Then i will do for sure nodejs, javascript, perl, maybe bash, i don't want to stay only in PHP, i know that.
It is just the first release, expect the repo to change a lot, i am for now collecting informations, for example :

-Shall i group the informations by exchange or by language ?
- how about making a GH page.
- I will add more comments in codes.
- A wiki page may be better then just using Readme.

These are what i am thinking about, now for the code itself, i don't want to provide something too much advanced technically, it is a tutorial about how to get the data, and if someone needs the libraries, then he can pick them.
Making a fancy library who calls all the exchanges is not the objective, experienced uses don't even need to watch the repo as they aleready know how to do it.

[nemgun]

Following the comments i added more details to the repo, plus now i use CURL instead of file_get_contents. Next i will add more exchanges, and as soon as there are enough exchanges i will add more libraries for other languages, i think that some of them will be more like tutorials instead of libraries.

[nemgun]

Added more features to the classes.
Extended examples, note that some of them may be slow to execute depending on your bandwith as some exchanges have hundreds of pairs.

To do

Add support for Poloniex, Krakken, Bitfinex