OneSignal REST API
for LuumenAI
Send push, email, and SMS from the terminal, with each send held for approval
Connect OneSignal and Luumen can read your apps, segments, devices, and past notifications while you work. Check who a segment covers before you message them. Look up a device that stopped receiving pushes. When it is time to send a notification, update a subscription, or remove a device, Luumen shows the exact payload first and waits for your approval. Authentication is by API key.
The OneSignal REST API toolbox
15 tools: 7 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFetch User IdentityRetrieve all aliases for a user identified by a specific alias.
- ReadGet Eligible In-App MessagesRetrieve the manifest of In-App Messages that a subscription is eligible to display.
- ReadView OneSignal AppRetrieve metadata for a single OneSignal app.
- ReadView DeviceRetrieve details of a specific device (player).
- ReadView DevicesRetrieve a paginated list of devices (players) for a OneSignal app.
- ReadView NotificationsRetrieve details of multiple notifications.
- ReadView SegmentsView segments for a OneSignal app.
- WriteBegin Live ActivityStart a Live Activity on OneSignal. Approval by default
- WriteCreate NotificationCreate and send a OneSignal push notification. Approval by default
- WriteCreate TemplateCreate reusable message templates for push, email, and SMS channels. Approval by default
- WriteCreate UserCreate a OneSignal user with optional subscriptions and aliases. Approval by default
- WriteDelete AliasDelete an alias by alias label from a OneSignal user. Approval by default
- WriteDelete DeviceDelete a device (player) from a OneSignal app. Approval by default
- WriteUpdate DeviceUpdate properties of an existing device. Approval by default
- WriteUpdate SubscriptionUpdate an existing subscription's properties. Approval by default
One prompt, start to finish
What a governed OneSignal REST API run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — begin live activity, create notification, create template, create user, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to OneSignal REST API — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut OneSignal REST API to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.