Get started

OneSignal REST API for AI agents

The OneSignal REST API lets applications send push notifications, emails, and SMS, and manage users and subscriptions programmatically. Product and marketing teams use it to reach users across channels. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect OneSignal REST APISee the 15 actions ↓
CommunicationAPI keyMCP + RESTonesignal.com
AUDIT LOG · ONESIGNAL REST APIPOLICY: acme-support
09:41:07 · claude · u_8f2read
onesignal_rest_api.get_eligible_iams
Get Eligible In-App Messages✓ allowed · 212ms
09:41:08 · claude · u_8f2read
onesignal_rest_api.view_an_app
View OneSignal App✓ allowed · 164ms
09:41:09 · claude · u_8f2write
onesignal_rest_api.create_user
Create User✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
onesignal_rest_api.delete_alias
Delete Alias✕ blocked · policy: deny
EVERY ONESIGNAL REST API CALL, ON THE RECORD
01 · USE CASES

What agents do in OneSignal REST API.

01

Send a push notification

Create and send a notification to a segment of subscribed users or devices.

02

Check a user's subscription status

Look up a device or user's subscription details read-only before targeting a campaign.

03

Delete a device with approval

Remove a stale device record only after confirming the user has uninstalled the app.

02 · ACTIONS

15 OneSignal REST API actions, graded by risk.

Every OneSignal REST API action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • onesignal_rest_api.get_eligible_iams
    Get Eligible In-App Messages
  • onesignal_rest_api.view_an_app
    View OneSignal App
  • onesignal_rest_api.view_device
    View Device
  • onesignal_rest_api.view_devices
    View Devices
  • onesignal_rest_api.view_segments
    View Segments
  • onesignal_rest_api.view_notifications
    View Notifications
  • onesignal_rest_api.fetch_user_identity
    Fetch User Identity

write

6

Create and change things. Allow, or ask the user first.

  • onesignal_rest_api.create_user
    Create User
  • onesignal_rest_api.update_device
    Update Device
  • onesignal_rest_api.create_template
    Create Template
  • onesignal_rest_api.create_notification
    Create Notification
  • onesignal_rest_api.update_subscription
    Update Subscription
  • onesignal_rest_api.begin_live_activity
    Begin Live Activity

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • onesignal_rest_api.delete_alias
    Delete Alias
  • onesignal_rest_api.delete_device
    Delete Device
03 · HOW IT WORKS

OneSignal REST API in three steps.

  1. 01Your users connect OneSignal REST APIThey add their OneSignal REST API api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create User” can wait for the user, and “delete Alias” can be denied outright.
  3. 03Any agent can actYour agent calls OneSignal REST API through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('onesignal_rest_api', {
  read: 'allow',
  write: 'ask',        // create_user
  destructive: 'deny',  // delete_alias
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How OneSignal REST API connects.

Users add their OneSignal REST API api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same OneSignal REST API connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use OneSignal REST API from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More communication apps.

Slack168 actionsMicrosoft Teams174 actionsDiscord28 actionsSlackbot101 actions2chat5 actionsAimTell15 actionsAndroid Texter11 actionsDialpad192 actions
ALL COMMUNICATION APPS →
07 · FAQ

OneSignal REST API and Arc0, answered.

Q01

Can I use OneSignal REST API with Claude, ChatGPT or Cursor?

Yes. Connect OneSignal REST API to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the OneSignal REST API actions you allow.

Q02

How do users connect OneSignal REST API?

Users add their OneSignal REST API api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which OneSignal REST API actions can my agent take?

15 in total: 7 read, 6 write and 2 destructive, such as “create User”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in OneSignal REST API?

Yes. Actions like “delete Alias” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call OneSignal REST API too?

Yes. The same OneSignal REST API connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug OneSignal REST API into your agent.

Your users connect OneSignal REST API once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.

Connect OneSignal REST APIBrowse all apps →

Free to build · MCP + REST · Audit log on every plan