OneSignal through Squiid

What OneSignal is

OneSignal is a messaging platform built around push. It handles the awkward parts of web push and mobile push directly: service worker registration, permission prompts, APNs and FCM credentials, device token lifecycle, and delivery retries. On top of that sit segments based on user properties and behaviour, scheduled and time-zone-aware sends, A/B testing, journeys for multi-step sequences, and email and SMS channels for teams that want one vendor. Delivery reporting shows what was sent, received and clicked per campaign, which is the only way to know whether push is working at all.

For AI-coded apps push is the channel an agent is least likely to get right unaided, because it involves platform credentials, a service worker file served from the correct scope, and different behaviour on iOS Safari than everywhere else. Using a platform that has solved those details is usually the difference between push working and push being quietly abandoned. Segments also let a release announcement reach only the users on the affected platform, rather than everyone who ever installed the app.

Why connect it through Squiid

OneSignal is on the Squiid roadmap. When it lands, Squiid will provision the app, hold the REST API key and route calls through https://api.squiid.io/v1/onesignal/... with Authorization: Bearer $SQUIID_API_KEY, with official SDKs working by base URL swap (gateway convention). Notification volume and plan cost will bill at OneSignal's listed price on one Squiid invoice. The REST key is worth protecting, since anyone holding it can send a push notification to your entire user base. Volume grows with your user base rather than with your traffic, so the cost curve is different from an API you call per request.

• One account, one key, one bill, one dashboard. OneSignal sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the OneSignal credentials. Your code carries SQUIID_API_KEY, so ONESIGNAL_APP_ID, ONESIGNAL_REST_API_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what OneSignal costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned OneSignal app with the key held by Squiid
• Web, iOS and Android push with token management
• Segments, scheduling and A/B testing
• Email and SMS channels on the same account
• OneSignal list pricing, no markup

How to connect OneSignal

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces ONESIGNAL_APP_ID, ONESIGNAL_REST_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/onesignal/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

OneSignal charges by subscriber volume and plan tier, with additional channels priced separately, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of OneSignal usage, with no markup and no per-request margin.

OneSignal has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so OneSignal usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: channels, keys and delivery configuration are re-created in your own OneSignal account from the documented setup. Squiid never owns your code, your schema or your domain, and the gateway speaks OneSignal's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

OneSignal through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on OneSignal usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.