Get started

OneSignal User Auth for AI agents

OneSignal User Auth covers the user- and device-management side of OneSignal's customer engagement platform, spanning push, email, SMS, and in-app messaging. Teams use it to keep audience data accurate. 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 User AuthSee the 12 actions ↓
CommunicationAPI keyMCP + RESTonesignal.com
AUDIT LOG · ONESIGNAL USER AUTHPOLICY: acme-support
09:41:07 · claude · u_8f2read
onesignal_user_auth.view_app
View App✓ allowed · 212ms
09:41:08 · claude · u_8f2read
onesignal_user_auth.view_user
View OneSignal User✓ allowed · 164ms
09:41:09 · claude · u_8f2write
onesignal_user_auth.create_user
Create or Update OneSignal User✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
onesignal_user_auth.delete_alias
Delete User Alias✕ blocked · policy: deny
EVERY ONESIGNAL USER AUTH CALL, ON THE RECORD
01 · USE CASES

What agents do in OneSignal User Auth.

01

Update a user's subscription

Update a subscription by token when a user changes their notification preferences.

02

Check segment membership read-only

View which segment a user belongs to before including them in a targeted send.

03

Review broadcast history

List past broadcasts to confirm what messaging a user has already received.

02 · ACTIONS

12 OneSignal User Auth actions, graded by risk.

Every OneSignal User Auth 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_user_auth.view_app
    View App
  • onesignal_user_auth.view_user
    View OneSignal User
  • onesignal_user_auth.view_device
    View OneSignal Device
  • onesignal_user_auth.view_outcomes
    View Outcomes
  • onesignal_user_auth.view_segments
    View Segments
  • onesignal_user_auth.view_broadcasts
    View Broadcasts
  • onesignal_user_auth.view_user_unread_message_count
    View User Unread Message Count

write

4

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

  • onesignal_user_auth.create_user
    Create or Update OneSignal User
  • onesignal_user_auth.update_subscription_by_token
    Update Subscription By Token
  • onesignal_user_auth.edit_device
    Edit OneSignal Device
  • onesignal_user_auth.onesignal_view_segment
    View OneSignal Segment

destructive

1

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

  • onesignal_user_auth.delete_alias
    Delete User Alias
03 · HOW IT WORKS

OneSignal User Auth in three steps.

  1. 01Your users connect OneSignal User AuthThey add their OneSignal User Auth api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create or Update OneSignal User” can wait for the user, and “delete User Alias” can be denied outright.
  3. 03Any agent can actYour agent calls OneSignal User Auth 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_user_auth', {
  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 User Auth connects.

Users add their OneSignal User Auth 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 User Auth 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 User Auth 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 User Auth and Arc0, answered.

Q01

Can I use OneSignal User Auth with Claude, ChatGPT or Cursor?

Yes. Connect OneSignal User Auth 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 User Auth actions you allow.

Q02

How do users connect OneSignal User Auth?

Users add their OneSignal User Auth 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 User Auth actions can my agent take?

12 in total: 7 read, 4 write and 1 destructive, such as “create or Update OneSignal User”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in OneSignal User Auth?

Yes. Actions like “delete User 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 User Auth too?

Yes. The same OneSignal User Auth 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 User Auth into your agent.

Your users connect OneSignal User Auth once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.

Connect OneSignal User AuthBrowse all apps →

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