Onesignal rest api MCP integration
Dispatches push notifications, resolves user aliases across devices, and retires stale device and subscription records.
15actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Create notification
Lyro creates and sends push notifications to engage users immediately. Agents reach customers directly without leaving the support interface.
Create user
Lyro creates a new OneSignal user with subscriptions configured. Agents onboard customers to messaging without separate signup steps.
Update subscription
Lyro updates a user's subscription settings to control message preferences. Agents fix contact availability issues without backend access.
How businesses use Onesignal rest api + Lyro
Each card is one request a support team gets, and the Onesignal rest api actions Lyro runs to close it.
Check what a subscriber was actually sent
Lyro reads the notification history for the app alongside the current state of that person's device, so a customer reporting a missing alert gets checked against the record instead of a guess.
View NotificationsView DeviceGet Eligible In-App MessagesSend a push from the conversation
When an update is worth pushing, Lyro dispatches the notification to the segment or subscriber it applies to, and can register a reusable template so the same message goes out the same way next time.
Create NotificationCreate TemplateBegin Live ActivityPoint one person's identities at one profile
Lyro looks up every alias mapped to a user, creates the user record when none exists, and drops an alias left over from an old account so notifications stop landing on two profiles.
Fetch User IdentityCreate UserDelete AliasRetire devices a customer no longer uses
Lyro audits the devices registered under an app, flips a subscription's enabled status when someone opts out, and deletes the retired handset so the send count reflects who is genuinely reachable.
View DevicesUpdate SubscriptionDelete Device
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Onesignal rest api actions it has and picks the ones a request needs.
- 01
Connect Onesignal rest api
Authorize the Onesignal rest api account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Onesignal rest api actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about Onesignal rest api
Setup, permissions, and the limits of what Lyro can do inside Onesignal rest api.
Push. Create Notification is the only dispatch action in the toolkit. Create Template does register templates for push, email, and SMS channels, but there is no separate email or SMS send action exposed here, so those channels stay with OneSignal's own sending.
Every action available in Onesignal rest api
All 15 actions your agent can call on Onesignal rest api, straight from the live MCP connection.
Begin live activity
Start a Live Activity on OneSignal.
Create notification
Create and send a OneSignal push notification.
Create template
Create reusable message templates for push, email, and SMS channels.
Create user
Create a OneSignal user with optional subscriptions and aliases.
Delete alias
Delete an alias by alias label from a OneSignal user.
Delete device
Delete a device (player) from a OneSignal app.
Fetch user identity
Retrieve all aliases for a user identified by a specific alias.
Get eligible in-app messages
Retrieve the manifest of In-App Messages that a subscription is eligible to display.
Update device
Update properties of an existing device.
Update subscription
Update an existing subscription's properties.
View onesignal app
Retrieve metadata for a single OneSignal app.
View device
Retrieve details of a specific device (player).
View devices
Retrieve a paginated list of devices (players) for a OneSignal app.
View notifications
Retrieve details of multiple notifications.
View segments
View segments for a OneSignal app.
The tools Onesignal rest api sits next to
Same connection, same setup. Pick the next one your team already uses.
Benchmark email
Adds contacts to lists and automations, reports opens and clicks, clears bounced addresses, and proofs a campaign before scheduling.
Doppler marketing automation
Adds and verifies subscribers, reads a contact's campaign delivery history, imports batches with error reporting, and records opt-outs on the spot.
Kickbox
Verifies an address the moment a customer types it, flags disposable domains, and catches a typo before a confirmation email is sent.
Moosend
Looks up subscribers by email, corrects and unsubscribes records, builds segment criteria, and clones, schedules and reports on campaigns.
Remarkety
Uploads and refreshes contacts in batches, syncs cart changes for remarketing, and reads campaign, customer and product records on request.
Thanks.io
Builds and cleans mailing lists, proofs a piece before print, dispatches postcards or queues stored sends, and looks up what already shipped.
Ready to connect Onesignal rest api?
Authorize the account and your agent has all 15 actions from the first conversation.