OneSignal API (Full)

Name: OneSignal API (Full) API
Brand: OneSignal API (Full)
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsPush NotificationsapiKey55 EndpointsREST

For Agents

Manage OneSignal apps, users, subscriptions, segments, templates, and notifications across push, email, and SMS through the full 55-endpoint OneSignal API.

Quickstart

Get started with OneSignal API (Full) in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"manage onesignal apps and notifications"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with OneSignal API (Full) API.

Create, update, and view OneSignal apps under an organization

Send push, email, and SMS notifications and pull message history

Build, edit, and delete user segments based on tags and properties

Create and update users by alias and manage subscription ownership transfers

GET STARTED

Start building with OneSignal API (Full) API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for OneSignal API (Full), keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for OneSignal API (Full), keeping it validated and agent-ready. The full OneSignal API exposes 55 endpoints covering apps, notifications, segments, users, subscriptions, templates, players, organizations, and outcomes analytics. Agents and applications can create and update apps, send notifications across push, email, and SMS channels, manage user records and aliases, build and edit segments, transfer subscription ownership, and pull outcome metrics filtered by attribution, platform, and time range.

Use Cases

Patterns agents use OneSignal API (Full) API for, with concrete tasks.

★ Multi-Channel Notification Campaigns

Coordinate push, email, and SMS sends from one API for a marketing campaign and inspect delivery outcomes afterwards. Notifications are created against an app, history can be pulled per message, and outcome analytics reveal conversions broken down by platform and attribution window.

Send a push notification to the 'Lapsed Users' segment under app id 'app-xyz' with heading 'We miss you' and pull the outcomes for 'click' over the next 7 days.

User and Subscription Management

Manage end-user identities through OneSignal aliases, link multiple device subscriptions to a single user, and transfer ownership when a subscription moves between accounts. POST /apps/{app_id}/users creates the user; PATCH endpoints update aliases and subscription assignments.

Create a user under app 'app-xyz' with external_id 'cust-123' and attach an existing iOS subscription id to that user.

Segmentation for Targeted Messaging

Define audience segments inside OneSignal programmatically based on tags or user properties, then reuse those segments when creating notifications. POST /apps/{app_id}/segments creates the segment, PATCH updates it, and DELETE removes it when no longer needed.

Create a segment named 'Active iOS Premium' under app 'app-xyz' filtered to platform=iOS and tag plan=premium.

Outcome and Conversion Analytics

Pull outcome metrics with platform and attribution filters to evaluate campaign performance after a send. GET /apps/{app_id}/outcomes accepts outcome names, a time range, platforms, and attribution windows, returning aggregate counts ready for reporting dashboards.

Pull outcome metrics for 'os__click' on app 'app-xyz' for the last 7 days filtered to iOS with direct attribution.

Agent-Run OneSignal Operations via Jentic

Customer engagement and marketing-ops agents drive OneSignal end to end through Jentic — sending notifications, editing segments, transferring subscriptions, and pulling outcomes — without ever holding the REST API key. Agents search by intent, load the matching schema, and execute against the OneSignal endpoint.

Use Jentic search 'create onesignal segment' to locate POST /apps/{app_id}/segments, load the schema, and execute with the segment definition.

Key Endpoints

55 endpoints — jentic publishes the only available openapi specification for onesignal api (full), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/apps

Create a OneSignal app

GET

/apps

List apps under the organization

POST

/apps/{app_id}/segments

Create a user segment

POST

/apps/{app_id}/users

Create a user

PATCH

/apps/{app_id}/subscriptions/{subscription_id}/owner

Transfer a subscription to another user

GET

/apps/{app_id}/outcomes

Retrieve outcome analytics with filters

POST

/players/csv_export

Export player records to CSV

POST

/notifications/{message_id}/history

Retrieve message history for a notification

POST

/apps

Create a OneSignal app

GET

/apps

List apps under the organization

POST

/apps/{app_id}/segments

Create a user segment

POST

/apps/{app_id}/users

Create a user

PATCH

/apps/{app_id}/subscriptions/{subscription_id}/owner

Transfer a subscription to another user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OneSignal REST API keys are stored encrypted in the Jentic vault (MAXsystem). Agents only ever hold a scoped reference, so the raw key never enters their context.

Intent-based discovery

Agents search by intent (e.g. 'create onesignal segment') and Jentic returns the matching operation across the 55-endpoint surface with its input schema attached.

Time to first call

Direct integration: 3-5 days to wrap auth, segments, users, and subscriptions. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

OneSignal API (minimal)

The minimal OneSignal entry covering only the notification creation endpoint.

Choose the minimal spec when the agent only needs to send notifications and not manage apps, users, or segments.

Alternative

Pusher Beams

Pusher Beams is an alternative push notification delivery platform.

Choose Pusher when the team is already standardised on Pusher channels.

Alternative

Pushover API

Pushover offers a simpler push API focused on personal and developer use cases.

Pick Pushover for personal-scale push rather than consumer-app multi-channel campaigns.

FAQs

Specific to using OneSignal API (Full) API through Jentic.

Why is there no official OpenAPI spec for OneSignal API (Full)?

OneSignal does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OneSignal API (Full) via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the OneSignal API (Full) use?

The API uses an apiKey credential — the OneSignal REST API Key sent in the Authorization header. Through Jentic the key is held encrypted in the vault (MAXsystem) and the agent only sees a scoped reference.

Can I manage OneSignal segments programmatically?

Yes. POST /apps/{app_id}/segments creates a segment, GET lists segments, PATCH updates an existing segment, and DELETE removes it. Segments can then be referenced when sending notifications.

How do I transfer a subscription between users?

Use PATCH /apps/{app_id}/subscriptions/{subscription_id}/owner with the target user's identity. The endpoint reassigns the subscription so future activity is attributed to the new owner.

Does the OneSignal API expose outcome analytics?

Yes. GET /apps/{app_id}/outcomes returns aggregated counts for named outcomes filtered by time range, platform, and attribution window, suitable for campaign reporting.

What are the rate limits for the OneSignal API (Full)?

Rate limits are not declared in this OpenAPI spec. Consult documentation.onesignal.com for the current REST API limits, which differ by endpoint family.

How do I run a OneSignal segment update through Jentic?

Run pip install jentic, search 'update onesignal segment', then load the PATCH /apps/{app_id}/segments/{segment_id} schema and execute. Jentic injects the REST API key from its vault.