Sanaf AI
Start free
Notifications

OneSignal REST API, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your OneSignal REST API account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Notifications
  • Connects with a key
  • 8 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What OneSignal REST API is

The OneSignal REST API enables developers to programmatically send push notifications, emails, and SMS, manage users and subscriptions, and configure apps.

You paste in a key from your own OneSignal REST API account. It is kept encrypted, and you can withdraw it from inside OneSignal REST API whenever you like.

How a run works

One message in, the work done in OneSignal REST API.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in OneSignal REST API. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own OneSignal REST API account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

8 tools it already has

What it can do in OneSignal REST API

These are the ready-made tools your AI employee already has in OneSignal REST API. It is not limited to them, but it never has to be taught these.

  • Create NotificationTool to create and send a onesignal push notification. use when you have your message and target audience ready to dispatch notifications.
  • Delete DeviceTool to delete a device (player) from a onesignal app. use when you need to remove a specific device by its player id.
  • Update DeviceTool to update properties of an existing device. use when you need to modify device attributes after registration.
  • View DeviceTool to retrieve details of a specific device (player). use when you have a onesignal player id and need current device info.
  • View DevicesTool to retrieve a paginated list of devices (players) for a onesignal app. use when you need to list or audit all registered devices for a given app.
  • View NotificationsTool to retrieve details of multiple notifications. use when you need to list notifications for a specific app.
  • View OneSignal AppTool to retrieve metadata for a single onesignal app. use when you need to fetch app details by its id.
  • View SegmentsTool to view segments for a onesignal app. use when you need to list all segments associated with an app.
Access, and who is in charge of it

You stay the boss of your OneSignal REST API account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own OneSignal REST API account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in OneSignal REST API is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in OneSignal REST API and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about OneSignal REST API

Can an AI employee really work inside OneSignal REST API?
Yes. It signs in to your own OneSignal REST API account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of OneSignal REST API?
No. Nothing moves and nothing is replaced. Your records stay in OneSignal REST API, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my OneSignal REST API account?
You paste in a key from your own OneSignal REST API account. It is kept encrypted, and you can withdraw it from inside OneSignal REST API whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in OneSignal REST API?
It has 8 ready-made tools in OneSignal REST API today, among them Create Notification, Delete Device and Update Device. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use OneSignal REST API and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in OneSignal REST API and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in OneSignal REST API?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in OneSignal REST API is written down with what it did and when.