onesignal-node

A Node.js client library for OneSignal API.

Table of Contents

* Overview
* Installation
* Usage
* Client Types
* Creating Client
* Create notification
* Cancel notification
* View notifications
* View notification
* View apps
* Create an app
* Update an app
* View devices
* View device
* Add a device
* Edit a device
* Edit tags with external user id
* New session
* New purchase
* Increment Session Length
* CSV Export
* Identity verification
* Tests
* Contributing

Overview

This is a wrapper library over OneSignal REST API. You can create notifications,
view apps, edit a device and all other actions you can take on OneSignal REST API.

Installation

``
npm install onesignal-node --save
`

Usage

` js
const OneSignal = require('onesignal-node');
`
OR
` js
import * as OneSignal from 'onesignal-node';
`

$3

For all the actions that require your OneSignal app id and app api key, you should use OneSignal.Client.
Sample actions: create notification, add device, csv export, create segment...

` js
const client = new OneSignal.Client('appId', 'apiKey');
`

For all the actions that require your User Auth Key you should use OneSignal.UserClient.
Sample actions: view apps, update an app, create an app...

` js
const userClient = new OneSignal.UserClient('userAuthKey');
`



$3

You can create a Client object as shown below. It requires two parameters: appId and apiKey, which you can find them on
your applications page on OneSignal dashboard.

There is also an optional parameter called options. You can set OneSignal rest api endpoint if you wish to using options.
By default the library uses https://onesignal.com/api/v1 for api endpoint.

`js
// With default options
const client = new OneSignal.Client('appId', 'apiKey');

// With custom API endpoint
const client = new OneSignal.Client('appId', 'apiKey', { apiRoot: 'https://onesignal.com/api/v2'});
`

$3

You can create a UserClient object as shown below. It requires one parameter: userAuthKey, which you can find it on
your OneSignal dashboard.

There is also an optional parameter called options. You can set OneSignal rest api endpoint if you wish to using options.
By default the library uses https://onesignal.com/api/v1 for api endpoint.

`js
// With default options
const userClient = new OneSignal.UserClient('userAuthKey');

// With custom API endpoint
const userClient = new OneSignal.UserClient('userAuthKey', { apiRoot: 'https://onesignal.com/api/v2'});
`

$3

https://documentation.onesignal.com/reference/create-notification

`ts
.createNotification(body: CreateNotificationBody): Promise
`

Please read the sections above to learn how to create a Client object.

`js
// See all fields: https://documentation.onesignal.com/reference/create-notification
const notification = {
contents: {
'tr': 'Yeni bildirim',
'en': 'New notification',
},
included_segments: ['Subscribed Users'],
filters: [
{ field: 'tag', key: 'level', relation: '>', value: 10 }
]
};

// using async/await
try {
const response = await client.createNotification(notification);
console.log(response.body.id);
} catch (e) {
if (e instanceof OneSignal.HTTPError) {
// When status code of HTTP response is not 2xx, HTTPError is thrown.
console.log(e.statusCode);
console.log(e.body);
}
}

// or you can use promise style:
client.createNotification(notification)
.then(response => {})
.catch(e => {});
`



$3

https://documentation.onesignal.com/reference/cancel-notification

`ts
.cancelNotification(notificationId: string): Promise
`

`js
const response = await client.cancelNotification('notification-id');
console.log(response.body);
console.log(response.headers);
console.log(response.statusCode);
`



$3

https://documentation.onesignal.com/reference/view-notifications

`ts
.viewNotifications(query?: ViewNotificationsQuery): Promise
`

`js
// without query
const response = await client.viewNotifications();
console.log(response.body);

// with query
const response = await client.viewNotifications({ limit:10, kind: 2, offset: 2 });
`



$3

https://documentation.onesignal.com/reference/view-notification

`ts
.viewNotification(notificationId: string): Promise
`

`js
const response = await client.viewNotification('notification-id');
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/view-apps-apps

You should use UserClient for view apps since it requires User Auth Key

`ts
.viewApps(): Promise
`

`js
const response = await userClient.viewApps();
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/create-an-app

You should use UserClient for view apps since it requires User Auth Key

`ts
.createApp(body: CreateAppBody): Promise
`

`js
const response = await userClient.createApp( { name: 'APP 1' });
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/update-an-app

You should use UserClient for view apps since it requires User Auth Key

`ts
.updateApp(appId: string, body: UpdateAppBody): Promise
`

`js
const response = await userClient.updateApp( 'app-id',{ site_name: 'test' });
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/view-devices

`ts
.viewDevices(query?: LimitOffsetQuery): Promise
`

`js
const response = await client.viewDevices({ limit: 200, offset: 0 });
console.log(response.body);
`




$3

https://documentation.onesignal.com/reference/view-device

`ts
.viewDevice(identifier: string): Promise
`

`js
const response = await client.viewDevice('device-id');
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/add-a-device

`ts
.addDevice(body: AddDeviceBody): Promise
`

`js
const response = await client.addDevice({
device_type: 'ios',
identifier: 'id1',
});
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/edit-device

`ts
.editDevice(deviceId: string, body: EditDeviceBody): Promise
`

`js
const response = await client.editDevice('device-id',{
identifier: 'id2',
});
console.log(response.body);
`

$3

https://documentation.onesignal.com/reference/edit-tags-with-external-user-id

`ts
.editTagsWithExternalUserIdDevice(externalUserId: string, body: EditTagsBody): Promise
`

`js
const response = await client.editTagsWithExternalUserIdDevice('external-user-id', {
tags: {
customTag: "customValue"
},
});
console.log(response.body);
`

$3

https://documentation.onesignal.com/reference/new-session

`ts
.newSession(deviceId: string, body: NewSessionBody): Promise
`

`js
const response = await client.newSession('device-id',{
language: 'tr',
});
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/new-purchase

`ts
.newPurchase(deviceId: string, body: NewPurchaseBody): Promise
`

`js
const response = await client.newPurchase('device-id',{
purchases: [...],
});
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference#increment-session-length

`ts
.incrementSessionLength(deviceId: string, body: IncrementSessionLengthBody): Promise
`

`js
const response = await client.incrementSessionLength('device-id',{
state: '',
active_time: 11,
});
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/csv-export

`ts
.exportCSV(body: ExportCSVBody): Promise
`

`js
const response = await client.exportCSV({});
console.log(response.body);
`



$3

https://documentation.onesignal.com/reference/create-segments

`ts
.createSegment(body: CreateSegmentBody): Promise
`

`js
const response = await client.createSegment({
name: 'new-segment',
filters: [..]
});
console.log(response.body);
`

$3

https://documentation.onesignal.com/reference/delete-segments

`ts
.deleteSegment(segmentId: string): Promise
`

`js
const response = await client.deleteSegment('segment-id1');
console.log(response.body);
`

$3

https://documentation.onesignal.com/docs/identity-verification

You can use these simple helpers to sign user id or email to be used in client-side code.

`ts
.signUserExternalId(id: string | number): string
.signUserEmail(email: string): string
`

Each of these will return SHA-256 hash, that was generated using apiKey.



Tests



Running all tests, coverage, build:
`bash
$ npm run test
$ npm run test-integration
$ npm run coverage
$ npm run build
`

Contributing

$3

To send a pull request:
- Fork the repo
- Clone the forked repo on your computer
- Switch to master branch
- Create a feature branch (git checkout -b feature/new-feature-name`)
- Make your changes and add new tests if necessary
- Push your changes to your fork
- Open a pull request

License

This project is under the MIT license.