PushizoDocs
Channels

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)RequirementsSubscription endpointGuide
web_pushVAPID (browser push services)Just enable it; subjectBrowser subscription (PushSubscription)Web Push
ios_pushAPNs HTTP/2.p8 (or .p12), Key ID, Team ID, Bundle ID, environmentDevice tokeniOS Push
android_pushFCM HTTP v1Firebase service account JSONFCM tokenAndroid Push
hms_pushHuawei Push KitApp ID, client secretHMS tokenHuawei HMS
emailSMTP, Amazon SES, ResendServer/key details, sender address (SPF/DKIM/DMARC)Email addressEmail
smsTwilio, NetgsmAccount details, sender number/headerE.164 phone numberSMS
whatsappMeta Cloud API, TwilioBusiness account, templatesWhatsApp numberWhatsApp
rcsTwilio RCSRCS sender (agent)RCS-capable numberRCS
In-app— (rendered by the SDK)NoneSession/deviceIn-app messages
Notification inbox—NoneUserNotification inbox
Live ActivitiesAPNs (liveactivity)iOS Push channelPush-to-start / update tokenLive 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.

On this page