Channels overview
The channels Pushizo supports (Web Push, iOS, Android, Huawei, email, SMS, WhatsApp, RCS, in-app, notification inbox, Live Activities), their providers and setup requirements.
Each channel is configured per app from App settings → Channels or with PUT /v1/apps/{app_id}/channels/{channel} (admin); POST …/validate runs a real connection test against the provider. Secret fields (p8, service account, password, API key) are stored encrypted with envelope encryption and are never returned in any response. Without real credentials, every channel runs on the simulation (mock) provider: the delivery pipeline runs end to end, but the message never reaches a device.
Channel (channel) | Provider(s) | Requirements | Subscription endpoint | Guide |
|---|---|---|---|---|
web_push | VAPID (browser push services) | Just enable it; subject | Browser subscription (PushSubscription) | Web Push |
ios_push | APNs HTTP/2 | .p8 (or .p12), Key ID, Team ID, Bundle ID, environment | Device token | iOS Push |
android_push | FCM HTTP v1 | Firebase service account JSON | FCM token | Android Push |
hms_push | Huawei Push Kit | App ID, client secret | HMS token | Huawei HMS |
email | SMTP, Amazon SES, Resend | Server/key details, sender address (SPF/DKIM/DMARC) | Email address | |
sms | Twilio, Netgsm | Account details, sender number/header | E.164 phone number | SMS |
whatsapp | Meta Cloud API, Twilio | Business account, templates | WhatsApp number | |
rcs | Twilio RCS | RCS sender (agent) | RCS-capable number | RCS |
| In-app | — (rendered by the SDK) | None | Session/device | In-app messages |
| Notification inbox | — | None | User | Notification inbox |
| Live Activities | APNs (liveactivity) | iOS Push channel | Push-to-start / update token | Live Activities |
Channel status
GET /v1/apps/{app_id}/channels returns, for each channel, its status (unconfigured, active, invalid), the last validation time and the failure reason. The worker runs a channel health check every 6 hours; if an APNs key/certificate or a service account is rejected, the channel becomes invalid, org owners receive an email and a warning appears in the dashboard. Certificates nearing expiry trigger an advance notice.
Channel selection and content
In POST /v1/notifications, you choose channels with target.channels; if omitted, channels are inferred from the content (contents → push channels, email_* → email; SMS only when explicitly requested). Each subscription is rendered with the fields of its own channel; for channel-specific fields (ios_*, android_*, chrome_web_*, email_*, sms_*, whatsapp_*, rcs_*), see sending notifications.
Preferences and suppression
User categories and channel preferences (preferences), the suppression list, quiet hours and frequency caps (delivery policies) are applied before sending on every channel; a suppressed delivery is recorded with status suppressed and a suppression_reason.
Billing, plans and quotas (Phase 13)
Plan matrix, trial, Stripe/iyzico/mock providers, usage report, quota and feature gates, alert emails. Design decisions: ADR-0020. Shared code: packages/billing (plan matrix, provider adapters, quota…
Web Push
The VAPID-based browser push channel — setup, browser support, service worker, permission prompts, content fields and troubleshooting.