PushizoDocs
Channels

Android Push (FCM)

The Firebase Cloud Messaging HTTP v1 channel — service account, data-only message model, Android content fields, notification channels, delivery feedback and troubleshooting.

Android push is sent through the FCM HTTP v1 API using a Firebase service account. Pushizo always sends data-only messages; the notification is built on the device by the Android SDK. This keeps click/delivery feedback, rich content and action buttons consistent even when the app is in the background. For Huawei devices, see the HMS channel. Setup: Android quickstart.

Credentials

Use the JSON file downloaded from Firebase → Project settings → Service accounts → Generate new private key. In the dashboard, go to Channels → Android Push → upload the file → Validate. API: PUT /v1/apps/{app_id}/channels/android_push { "provider": "fcm", "config": { "service_account": { …json… } } } (a multipart file upload is also accepted). Validation obtains an OAuth token from FCM and checks project access; token_uri is accepted only on Google domains (SSRF protection).

Content fields

FieldBehavior
headings, contents, urlTitle, body and click URL
android_channel_idNotification channel (Android 8+). If missing, the SDK uses the default channel (defaultChannelName)
android_groupGrouping key
android_soundSound file name in res/raw
small_icon, large_iconStatus bar icon (drawable name) and large icon (URL or drawable)
android_accent_color#RRGGBB accent color
android_visibility1 public, 0 private, -1 secret (lock screen)
big_pictureBig picture style
buttons[{ id, text, icon? }] action buttons
collapse_idFCM collapse_key (the same key replaces the previous notification)
priority (5/10)FCM normal / high priority; 10 wakes the device from Doze mode
ttlFCM ttl (seconds, up to 28 days)
dataCustom payload; the SDK exposes it via notification.additionalData

Notification channels are defined in the dashboard under Channels → Android Push → Notification channels (name, importance, sound, vibration); the SDK creates them on the device at first launch (Android SDK → notification channels).

Delivery and feedback

  • FCM response: 200 → sent; UNREGISTERED / INVALID_ARGUMENT (token) → subscription invalid + subscription.invalidated; QUOTA_EXCEEDED/UNAVAILABLE/5xx → retry schedule.
  • The SDK reports received when it displays the notification and opened when it is tapped; to comply with the Android 12+ "trampoline" restriction, the SDK uses an explicit PendingIntent.
  • Token changes (onNewToken) are written to the subscription automatically by the SDK.

Troubleshooting

SymptomCheck
Validation returns 403Is the service account's project the same as the app's google-services.json project? Is the Firebase Cloud Messaging API (V1) enabled?
Notifications not arriving (Android 13+)Has the POST_NOTIFICATIONS permission been granted (Pushizo.Notifications.permission)?
Notifications not arriving (some devices)Manufacturer battery optimization (Xiaomi, Huawei EMUI); try priority: 10; use HMS on Huawei
Icon shows as a white squaresmall_icon must be monochrome with a transparent background
Tap opens the app but there is no urlRead event.url with addClickListener; check the Activity launchMode

On this page