JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1
  • Score
    100M100P100Q42851F
  • License MIT

A zero dependency library for the Bungie.net api

Package Exports

  • bungie-net-api

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (bungie-net-api) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Node.js Bungie.net API Library

This library aims to be the fastest, lightest-weight JavaScript implementation of the Bungie.net API. This project has 3 sacred goals

  1. Zero Dependency
  2. Fully Asynchronous
  3. Well Documented

Setup

  1. First create a project at https://www.bungie.net/en/Application
  2. Make sure that your OAuth client type is "Confidential" if you need to make oAuth calls
  3. Install this library npm install bungie-net-api
  4. Finally, create an API object as show below
  const ApiCredentials = {
    key : "you_secret_key",
    clientId : "your_client_id",
    clientSecret: "your_client_secret"
  }

  const BungieLib = require( 'bungie-net-api' );

  // This will load ALL micro-libraries
  const Api = new BungieLib( ApiCredentials );
  1. If you only need to load certain endpoints, you can do so by passing an array of micro-libraries that you will need to the BungieLib constructor
  const ApiCredentials = {
    key : "you_secret_key",
    clientId : "your_client_id",
    clientSecret: "your_client_secret"
  }

  const BungieLib = require( 'bungie-lib' );

  // This will only load the Destiny2, Forum, and User Micro-Libraries
  const Api = new BungieLib( ApiCredentials, [ 'destiny2', 'forum', 'user' ] );
  1. The first thing that you should do now is redirect your end user to the authentication endpoint and have them give your app permission to interact with their account
  // Redirect the end user to the auth uri somehow
  WebSocket.send( Api.authUri );
  1. Once the user has approved your application, they will be redirected to the uri that you specified at https://www.bungie.net/en/Application/Detail/ and your accessCode will be a querystring parameter. Grab it associate it with this client somehow (I use a session store). You'll need this code if you want to make privileged API requests

Fully Asynchronous

The library makes extensive use of native ES6 promises. Any non-trivial work load is exectued asynchonously making the library extrememly scalable. All API call return an ES6 Promise that resolves with the parsed Bungie.net API response.

  Api.User.getAvailableThemes().then( resp => {
    console.log( resp ); // Do something with the response
  } );

This means that you can make as many API calls as you want simultaneously.

  // All of these API calls will me made simultaneously.
  let calls = [
    Api.User.searchUsers( 'JackSparrow' ),
    Api.User.getAvailableThemes(),
    Api.Destiny2.searchPlayer( "JackSparrow", "TIGERPSN" ),
    Api.Trending.getTrendingCategory()
  ];

  // Once all of those API calls have finished, do work
  Promise.all( calls ).then( data => {
    // data[0] is the result of Api.User.searchUsers( 'JackSparrow' ), etc
  } );

Api Call Chaining

The Flexibility of promises allows us to take multiple API calls and chain them one after the other. FOr instance, lets request an oAuth access token and then immediately refresh that token. (You would never do this in real life, but it's a good example of an instance when we need one promise to wait on another promise)

  Api.OAuth.requestAccessToken( ApiCreds )
    .then( accessToken => Api.OAuth.refreshAccessToken( accessToken) )
    .then( newToken => {
        // Store our latest token somehow
    }) ;

Requesting an oAuth token

  Api.OAuth.requestAccessToken( ApiCreds.authCode ).then( oAuth => {
    // Save your oAuth tokens. A session store is recommended
  } );

Refreshing an oAuth token

  Api.OAuth.refrshAccessToken( oAuth ).then( oAUth => {
    // Save your oAuth tokens. A session store is recommended
  } );