OneSignal
OneSignal is a lifecycle customer engagement platform for mobile push, web push, email, SMS/RCS, in-app messaging and iOS Live Activities, orchestrated through Journeys, segments and a single REST API at api.onesignal.com. It reports 1.3 trillion messages a year across 200k apps and 1.5 billion monthly active users. The developer surface is a published OpenAPI 3.1 contract, a full set of first-party server and client SDKs, a hosted OAuth-authenticated MCP server, an A2A agent card and six provider-published Agent Skills.
OneSignal publishes 6 API contracts indexed on the APIs.io network, including Apps API, Notifications API, Players API, and 3 more. Tagged areas include Notification, Push, Email, SMS, and Mobile.
The OneSignal catalog on APIs.io includes 1 event-driven AsyncAPI specification.
OneSignal’s developer surface includes authentication, engineering blog, changelog, CLI, documentation, API reference, getting-started guide, and 40 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
What people ask OneSignal 5
The questions people put to an LLM, and the jobs they hand an agent, that OneSignal's APIs answer — each one linked to the operation that does it. Generated by API Evangelist
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Communications (CPaaS) | covered | 35.2 | - | 1 |
| Martech and Customer Data Platforms | covered | 35.2 | - | 1 |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
OneSignal Apps API
The Apps API from OneSignal — 21 operation(s) for apps.
OneSignal Notifications API
The Notifications API from OneSignal — 4 operation(s) for notifications.
OneSignal Players API
The Players API from OneSignal — 1 operation(s) for players.
OneSignal Templates API
The Templates API from OneSignal — 3 operation(s) for templates.
OneSignal MCP Server
OneSignal's hosted Model Context Protocol server at https://api.onesignal.com/mcp/oauth, connected over browser-based OAuth 2.1 with PKCE. Listed in the Cursor marketplace and C...
OneSignal Organizations API
The Organizations API from OneSignal — 1 operation(s) for organizations.
Open Collections 6
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONOneSignal Apps API
OPEN COLLECTIONOneSignal Notifications API
OPEN COLLECTIONOneSignal Players API
OPEN COLLECTIONOneSignal Templates API
OPEN COLLECTIONOneSignal
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
OneSignal MCP
OneSignal ships two distinct remote MCP servers. The product server at api.onesignal.com/mcp/oauth is the one Cursor, Claude, Copilot and ChatGPT connect to; it is OAuth-gated, ...
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Onesignal Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Onesignal Finops
FINOPSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Onesignal Webhooks
ASYNCAPIOpenAPI Overlays 9
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Onesignal Apps Api Phrasing Overlay
GENERATEDOnesignal Apps Overlay
GENERATEDOnesignal Notifications Overlay
GENERATEDOnesignal Players Api Phrasing Overlay
GENERATEDOnesignal Players Overlay
GENERATEDOnesignal Templates Api Phrasing Overlay
GENERATEDOnesignal Templates Overlay
GENERATEDScroll for all 9
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll for all 7
Access & Security 7
Authentication, authorization, and security posture
Scroll for all 7
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.