Onesignal APIs
2 APIs56 Endpoints1 Category
Categories
API Catalog(2 of 2)
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
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.