vk-dirty-api

vk-dirty-api

VK API for Node.js with authentication using login and password (the dirty way)

Sometimes it is needed to use VK API directly from the Node app, however, using either signing requests or OAuth allows access only to server-side methods. In order to 'overcome' this limitation, this dirty if you know what I mean way of getting access_token for VK API was developed

Installation

$ npm install vk-dirty-api --save

Usage

Super simple to use

const vk = require('vk-dirty-api')

const credentials = {
  client_id: 0, // application ID (available in app settings at https://vk.com/apps?act=manage)
  login: '[e-mail]',
  pass: 'your_super_secret_password',
  phone: '[phone]',
  tokenStorage: new vk.TokenStorage() // built-in token storage that stores retrieved access token in file for
                                      // further use
}

/**
 * Retrieve access_token using credentials defined above
 */
vk.token(credentials)
  .then(token => {
    console.log(`Successfully authenticated (access_token: ${token})`)

    /**
     * Use built-in API call helper
     */
    const api = vk.api(token)

    /**
     * Request current account info
     */
    return api('account.getInfo', { fields: 'country' })
      .then(info => console.log('Account info', info))
      .catch(err => console.error('Unable to complete API request', err))
  })
  .catch(err => console.error('Unable to authenticate', err))

Changelog

3.0.2

Changes

• Switch to Standard code style
• Update example usage in README
• Refactor built-in token file storage to be an ES2015 class
• Use babel-eslint parser in ESLint
• Update babel-cli to 6.8.0 from 6.4.5
• Update fs-jetpack to 0.9.0 from 0.8.0
• Update mocha to 3.0.2 from 2.3.4
• Update eslint to 3.5.0 from 2.5.0
• Update request-promise to 4.0.2 from 3.0.0
• Update joi to 9.0.4 from 8.0.1
• Update cheerio to 0.22.0 from 0.20.0