This library is currently transistioning from bundling adapters for many sources to a single interface, to a set of tools for primary scraping of XBoxLive GamerCard and account data (which is what all existing APIs are doing). The reason I'm doing this is threefold:
- The number of upstream changes to these APIs is neverending, usually resulting in nothing more than attempting to match the APIs servers against MS host configurations and request limits, with little to no tangible benfits to users.
- Users of these kind of services are often small clans or semi-closed social groups which do not need the overhead or complexity of a monloithic API and could really work rather well off a proxied scrape of the GamerCard endpoint
- I've written a ton of scrapers, caches and proxies.
So in the new order, you just use my interface to write some code interfacing with your API, fork this project add the new service to the ./services directory and submit a pull request (with tests) and I'll enable it in the project. In this way, each maintatiner is only capable of breaking their own integration. Check out the sample.
I may run an open API on top of this, but that is TBD.
The initial version used the venerable xboxapi.duncanmackenzie.net, and subsequent vesions supported variants of xboxleaders.com and xboxapi.com. Today I support an interface through which you can implement your own service wrapper.
TBD (a set of returns and fields (per endpoint) to serve as a canonical standard).
Run the tests at the project root with:
mocha
Run a specific suite (one of gamer-card, overwatch or destiny) with:
mocha test/<suite>
If you want to run the destiny tests, you must set DESTINY_API_KEY in your environment
(run all tests before submitting a pull request)