OneSignal vs SuprSend

OneSignal

Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026.

SuprSend

MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.

OneSignal

1. Use Authorization: Key <key>, not Bearer, and put app_id in the body
2. Send an idempotency_key UUID with every create call and reuse it on each retry
3. On 429, wait for Retry-After, then back off with jitter, up to 10 attempts
4. Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled
5. Target people with include_aliases.external_id and set target_channel

SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with --tools set to read-only groups for production workspaces
3. Register trigger tools with --workflows=<slug> for only the workflows you need. The default registers none
4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
5. Treat management API responses as secrets. They include the workspace secret in plain text