Skip to main content

Push Notifications

Slug: push
Provider: Firebase Cloud Messaging (FCM)
Inbound ACK: No — users must ACK via the web dashboard

How it works​

PSAPLink sends a push notification to a mobile or web app via Firebase Cloud Messaging using a server key. The notification appears on the device. Users must open the PSAPLink web dashboard to acknowledge.

Configuration schema​

FieldTypeRequiredDescription
fcm_server_keystringYesFirebase Cloud Messaging (FCM) server key from the Firebase project settings.

Get an FCM server key​

  1. Go to the Firebase Console.
  2. Select your project → Project Settings → Cloud Messaging tab.
  3. Copy the Server key under Cloud Messaging API (Legacy).

Create a channel​

POST /api/v1/transport-channels
Authorization: Bearer <token>
Content-Type: application/json

{
  "transport_type_slug": "push",
  "name": "Mobile Push Alerts",
  "config": {
    "fcm_server_key": "AAAA..."
  }
}

Device token registration​

Users register their device tokens via:

POST /api/v1/me/push-tokens
Authorization: Bearer <token>
Content-Type: application/json

{
  "token": "<device_registration_token>"
}

PSAPLink stores the token and uses it for targeted delivery when a notification is dispatched to that user.

Test the channel​

POST /api/v1/transport-channels/{id}/test
Authorization: Bearer <token>

Limitations​

  • No inbound ACK. Users must acknowledge via the PSAPLink web dashboard.
  • FCM Legacy API (/fcm/send) is used. Google plans to deprecate it; migration to FCM HTTP v1 API will require code changes.
  • Push delivery is best-effort — devices that are offline or have Do Not Disturb enabled may not receive the notification promptly.