Strongly typed Node SDK for RiSE. RiSE is a developer focused eCommerce Platform as a Service that gives teams the industry's finest control over the development process and integration into their existing or new applications.

npm install @rise/sdk-js --save

RiSE separates requests into 3 major categories:

• Command
• Event
• Action

Commands are any type of request that will result in something being modified eg. create a user

An Event is a request listener that something has been modified eg, a user was created

An Action is a request made that does not modify anything eg, retrieve a user.

You can connect your applicatoin on the backend by authenticating it and then updating your application state with the token/session provided. This is useful when you are doing some grunt work.

// Create a new instance
const rise = new RiSE({
  sandbox: true,
  public_key: <public_key>,
  private_key: <private_key>
})

// Store the state specific token and session
let applicationToken, applicationSession

// Authenticate for later requests by the API
rise.authenticateApiUser(
  <channel_uuid>,
  <applicationIdentifier>,
  <applicationPassword>
)
  .then(res => {
    applicationToken = res.token
    applicationSession = res.session
  })
  .catch(err => console.log)
})

Unlike connecting with an application, you should probably forward your user's information to make the request. This is better for analytics and allows for information to be specific for the user requesting information.

const rise = new RiSE({
  sandbox: true,
  public_key: <public_key>
})

rise.<endpoint>.<method>({}, {
  session: <session>,
  token: <token>
})
  .then(res => {

  })
  .catch(err => console.log)
})

RiSE also let's you do everything through 2-way sockets either in a browser or your node.js application.

import sockets from '@rise/sdk-js-sockets'
// Create a new instance
const rise = new RiSE({
  sandbox: true,
  public_key: <public_key>,
  private_key: <private_key>,
  sockets: sockets
})

A quick start documentation, see the full documentation here.

Every response from RiSE will include certain properties:

data : An array of objects or an object

Occasionally, the responses will also include:

token: the JWT token to use on the next request

session: an optional session uuid to use on the next request if no token was provided.

url : the canonical endpoint to retrieve the obejct or list again

urls : <String[]> the canonical endpoints to retrieve the objects again

populated: an object of properties that were expanded in the response

If the Request was a command, the response will be an event and will also include:

event_type: the event name that was generated from the command.

If the Request was an action, the response will also include:

action: the action performed

If the Request was for a single object, the response will include:

object: the type of the object in the data attribute

If the Request was for multiple objects, the response will include:

includes: <String[]> the types of the object in the data attribute

If the Request was for a list of like objects, the response will include:

list: the type of like objects in the data attribute

limit: the number of potential objects in the data attribute

offset: the number from 0 of the total objects in a list

total: total amount of objects that meets the query criteria

query: calculated query

sort: describing how the list is sorted

If this is slightly confusing, don't worry, as each response will always have a data property with what you'd typically expect, the other properties are syntactical sugar to be more pragmatic with the responses.

Create a User

let user
rise.channelUser.create({
    name_first: 'First',
    name_last: 'Last',
    username: 'uniqueusername',
    email: '[email protected]'
}, {
// If you used the authenticateApiUser endpoint, then you don't need to specifiy the token or session, since that will be added to the request automatically.
  token: <token>,
  session: <session>, // if you have an auth token, session isn't required, as that is built into the token
  params: {
    channel_uuid: <channel_uuid>
  }
})
  .then((_res) => {
     user = _res.data
    // _res.event_type
    // _res.object
    // _res.url
    // ? _res.session
    // ? _res.token
  })
  .catch((err) => {
    // Handle Error
  })

Alternatively, you can pass parameters, query, body, and headers.

let user
rise.channelUser.create({
  name_first: 'First',
  name_last: 'Last',
  username: 'uniqueusername', // RiSE will generate one if this is blank
  email: '[email protected]' // Required for every user
}, {
  token: <token>,
  session: <session>,
  params: {
    channel_uuid: <channel_uuid>,
  },
  query: {
    attributes: ['user_uuid', 'username', 'roles'],
    populate: ['roles']
  },
  headers: {
    'x-application-my-app-header': 'any header with an "x-application-*" can be used here and will be included in the header of requests made to 3rd party apps passed through RiSE eg. "x-application-my-app-header" will pass "my-app-header" to the third party.'
  }
})
  .then((_res) => {
     user = _res.data

    // _res.event_type
    // _res.object
    // _res.url
    // ? _res.session
    // ? _res.token
  })
  .catch((err) => {
    // Handle Error
  })

Get a User by ID

rise.channelUser.get({}, {
  token: <token>,
  params: {
    channel_uuid: <channel_uuid>,
    user_uuid: user.user_uuid
  }
})
.then((_res) => {
  user = _res.data
})
.catch((err) => {
  // Handle Error
})

Using one the RiSE Socket Libraries, you can connect to RiSE through this SDK and subscribe to Event types and Resources.

The documentation for this SDK is under development, however the source code is easy to reason around and is well commented. Please see the src or tests for available actions.

When the master is tagged with a release, it will automatically publish to npm, updates the Changelog and bumps the version. The SDK uses the standard-version library to manage it all.

To run a patch release:

npm run release -- --release-as patch

and then commit to master. git push --follow-tags origin master

You can also test the release by running

npm run release -- --dry-run --release-as patch