onesignal-node-api
onesignal-node-api copied to clipboard
OneSignal
OneSignal Node Client
# Description ## One Line Summary I've exported the `ConfigurationParameters` from the lib so that it can be reused by dependees. ## Details ### Motivation I'm wrapping OneSignal in a...
close https://github.com/OneSignal/onesignal-node-api/issues/61 # Description ## One Line Summary Add the missing REST API parameter disable_email_click_tracking ## Details ### Motivation The parameter of the REST API create email message `disable_email_click_tracking` (https://documentation.onesignal.com/reference/email#disable_email_click_tracking)...
close https://github.com/OneSignal/onesignal-node-api/issues/83 # Description ## One Line Summary Remove `node-fetch` as `fetch` is available in the modern environments (browser and Node >= 18) ## Details ### Motivation This package depends...
### What happened? Based on readme.md these methods should be ready to use, but they are missing in the implementation. ### Steps to reproduce? ```Markdown yarn add @onesignal/node-onesignal then try...
### What happened? It seems there is an issue with the `@onesignal/[email protected]` in which, if I create a notification class object: ```js const notification = new Notification(); notification.target_channel = 'email';...
### How can we help? This code is getting error 403. I believe `key` and `appId` was not wrong because I used them on https://documentation.onesignal.com/reference/update-user?playground=open#parameter-app-id and API was called successfully....
I don't know why for such a critical property, it's just been given a type of 'any'. Is it always an array of strings? How is this acceptable? https://github.com/OneSignal/onesignal-node-api/blob/0d5de918894384cc284b205b0c5c1bdb8e2aa3f0/models/CreateNotificationSuccessResponse.ts#L17
