ceven

OneSignal REST API

Triggers push notifications, emails, and SMS based on user behavior, manages device registrations, and audits notification delivery across all your apps.

Try OneSignal REST API in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native OneSignal REST API integration

    • Describe the outcome and Ceven picks the right OneSignal REST API calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your OneSignal REST API data, across all 15 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke OneSignal REST API access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in OneSignal REST API, when, and on whose behalf.
    • The agent pauses and asks when OneSignal REST API is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach OneSignal REST API.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every OneSignal REST API action to support review and sign off.

Supported tools

Every action Ceven's agents can run on OneSignal REST API, and when to use it.

Create Notification
Use this when you have a message and target audience ready to dispatch a push notification to specific players or segments.
Delete Device
Remove a specific device from a OneSignal app using its player id. Use this for user opt out requests or account deletions.
Update Device
Modify attributes or tags for an existing device. Use this to update user preferences or change a player segment.
View OneSignal App
Retrieve metadata and configuration for a single app. Use this to verify app id settings before sending a blast.
View Device
Pull details for a specific player id to check current device info, subscription status, and tags.
View Devices
Retrieve a paginated list of all registered devices for an app. Use this to audit your total reach.
View Notifications
Pull a history of notifications sent for a specific app to analyze delivery timing and volume.
View Segments
List all defined segments for an app. Use this to ensure the correct segment id is used in a notification call.
Create Segment
Define a new user segment based on specific filters. Use this to group users by behavior or location.
Update Notification
Modify the content or targeting of a scheduled notification before it is sent.
Delete Notification
Cancel a scheduled notification to prevent it from being delivered to users.
Search Devices
Find devices based on specific tags or external user ids to target individual users.

12 actions · scroll to see them all

Frequently asked questions

Ceven implements a smart queuing system that respects the OneSignal REST API limits. OneSignal applies different limits based on whether you are using the free tier or a paid plan. If the agent detects a 429 too many requests response, it automatically pauses the workflow and uses an exponential backoff strategy to retry the request. This ensures that large scale notification blasts do not get blocked or cause your API key to be temporarily throttled. You can monitor the queue status in the Ceven dashboard to see if a high volume campaign is being paced to match your specific OneSignal plan limits.
Yes. The agent can target notifications using player ids, external user ids, or specific tags. When you provide a user email or ID from your CRM, Ceven first uses the search devices action to find the corresponding OneSignal player id. Once the player id is retrieved, it passes that specific identifier into the create notification call. This allows for highly personalized triggers, such as a shipping update for a single order, rather than broadcasting a message to an entire segment. The agent handles the lookup and delivery mapping in a single step.
Ceven can coordinate push, email, and SMS through the OneSignal API. You can build a workflow that attempts a push notification first and then falls back to SMS if the user does not have a registered device. The agent manages the logic of checking device availability via the view device call before deciding which endpoint to hit. This ensures users get the message on their preferred channel without receiving redundant alerts across every platform. You just define the priority order in your workflow and Ceven executes the sequence.
The agent treats tags as dynamic metadata. You can tell Ceven to tag a user as a vip when they spend over one thousand dollars in your store. The agent then calls the update device endpoint to append that tag to the OneSignal player record. These tags can then be used by the agent to filter notifications or by you within the OneSignal dashboard to build segments. Because the agent can read and write tags in real time, your segments stay current without any manual CSV uploads or sync scripts.
Ceven can run a periodic cleanup workflow to keep your systems in sync. The agent pulls a list of active devices from OneSignal and compares them against your user database. If a device is missing from OneSignal, the agent can update your CRM to mark that user as unreachable via push. This prevents your workflows from wasting API calls on dead tokens and gives your marketing team an accurate view of reachable users. You can set this audit to run daily or weekly depending on your needs.
Yes, the agent can use the delivery time parameter in the create notification call. Instead of sending a message immediately, you can tell Ceven to schedule a notification for a specific date and time in the future. The agent handles the conversion of your natural language request into the required ISO 8601 timestamp format required by the OneSignal API. This is useful for time zone specific campaigns where the agent calculates the optimal send time for different regions and schedules multiple API calls accordingly.
OneSignal allows a large number of tags per player, but the API request size has limits. Ceven manages this by batching tag updates. If you need to add twenty different tags to a user, the agent groups them into a single update call to minimize network overhead and avoid hitting request limits. It is important to note that OneSignal tags are case sensitive, so the agent standardizes all tag keys to lowercase by default to prevent duplicate tags like Vip and VIP from being created for the same user.
Your OneSignal API key is stored in an encrypted vault and is never exposed to the end user or written in plain text within the workflow logs. When the agent needs to make a call, it retrieves the key from the vault and injects it into the request header at the moment of execution. You can rotate your key in the OneSignal dashboard and update it in the Ceven settings page without needing to rebuild your existing workflows. This ensures that your communication channel remains secure while allowing the agent full operational access.

Alternatives to OneSignal REST API

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Airship logoAirshipBraze logoBrazeFirebase Cloud Messaging logoFirebase Cloud MessagingAWS SNS logoAWS SNS

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect OneSignal REST API and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free