OneSignal REST API integration

Quick start

Call OneSignal REST API from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to OneSignal REST API's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "ONESIGNAL_REST_API_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own OneSignal REST API API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

15 actions exposed via the OneSignal REST API integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• ONESIGNAL_REST_API_BEGIN_LIVE_ACTIVITY
• ONESIGNAL_REST_API_CREATE_NOTIFICATION
• ONESIGNAL_REST_API_CREATE_TEMPLATE
• ONESIGNAL_REST_API_CREATE_USER
• ONESIGNAL_REST_API_DELETE_ALIAS
• ONESIGNAL_REST_API_DELETE_DEVICE
• ONESIGNAL_REST_API_FETCH_USER_IDENTITY
• ONESIGNAL_REST_API_GET_ELIGIBLE_IAMS
• ONESIGNAL_REST_API_UPDATE_DEVICE
• ONESIGNAL_REST_API_UPDATE_SUBSCRIPTION
• ONESIGNAL_REST_API_VIEW_AN_APP
• ONESIGNAL_REST_API_VIEW_DEVICE