OneSignal APIs for AI Agents
CommunicationsPush NotificationsJentic-Generated SpecsAPI keyAgent Ready
onesignal.com·Developer portal → documentation.onesignal.com
OneSignal API Catalog
2 APIs across 1 product group. All share one credential.
Communications2
OneSignal API (Full)Manage OneSignal apps, users, subscriptions, segments, templates, and notifications across push, email, and SMS through the full 55-endpoint OneSignal API.~55 endpointsOneSignal APISend push notifications, email, SMS, and in-app messages to OneSignal audiences with a single notification creation endpoint.~1 endpoint
Which OneSignal API should I use?
| I want to... | Use | Why |
|---|---|---|
| Only need to send a notification | OneSignal API | The minimal spec exposes a single notification-creation endpoint, so the agent can be limited to sending and nothing else. |
| Manage apps, users, segments, subscriptions, or analytics | OneSignal API (Full) | The full 55-endpoint spec covers app, user, segment, subscription, template, and outcome operations beyond sending. |
| Create or edit audience segments before sending | OneSignal API (Full) | Segment create, update, and delete operations live only on the full spec; the minimal spec can reference existing segments by name but cannot manage them. |
Install Jentic One Beta
Connect the OneSignal APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OneSignal APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fonesignal.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fonesignal.com" | 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.
Once connected, ask your agent something like: .
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring OneSignal by hand means managing its REST API key and building calls across the full 55-endpoint spec and the minimal send spec against api.onesignal.com yourself. With Jentic One you install once, add the OneSignal APIs you need from the Jentic directory, store the key once, and your agent calls them.
Permission scoping
OneSignal puts the app id in the URL path on the full spec, so a rule in your own Jentic One instance can pin the agent to one app and one set of operations, for example sending and reading outcomes but not creating apps or exporting players. An agent that only needs to send can be limited to the minimal spec's single operation.
Credential isolation
Your OneSignal REST API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same key covers both specs.
FAQs
Specific to using OneSignal APIs through Jentic.
Which OneSignal spec should an agent use?
Use the minimal spec when the task is only to send a notification, since it exposes a single notification-creation endpoint. Use the full 55-endpoint spec when the agent needs to manage apps, users, subscriptions, segments, templates, or outcome analytics. Both authenticate with the same key, so an agent can start narrow and widen its allowed operations later.
Does one credential cover both OneSignal specs?
Yes. Both specs use the same OneSignal REST API Key in the Authorization header, so a single stored credential covers every operation across the full and minimal surfaces. You do not need separate keys for sending versus managing segments or users.
Why does Jentic publish OpenAPI specs for OneSignal?
OneSignal does not publish its own OpenAPI specification. Jentic generates and maintains both the full and minimal specs so that AI agents and developers can call OneSignal through structured tooling. Each spec is validated against the live API and kept up to date.
Can an agent both build audiences and send messages?
Yes. The full spec creates, updates, and deletes segments and manages user identities, while either spec can then send a notification targeted at those audiences. This lets an agent curate an audience and deliver to it within OneSignal, rather than splitting the work across separate tools.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
