OneSignal API APIs
2 APIs56 Endpoints1 Category
Categories
API Catalog
OneSignal API
Jentic publishes the only available OpenAPI specification for OneSignal API, keeping it validated and agent-ready. This minimal OneSignal entry exposes the core POST /notifications endpoint for sending push, email, SMS, or in-app messages to registered users, segments, or specific subscription ids. The endpoint accepts the OneSignal app id, target audience parameters, message content, and channel-specific options, and returns the created notification id along with delivery counters.
1 endpointsOneSignal API (Full)
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.
55 endpointsConnect Your Agent
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.