ComRaidA modern push notification API should feel like any other infrastructure dependency: authenticate, create a Message, move on.
POST /messages
curl https://api.comraid.app/messages \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"channel": "push",
"to": { "external_user_ids": ["customer_123"] },
"content": {
"push": {
"title": "Something good just landed",
"body": "Your next favorite feature is here.",
"platforms": ["android", "ios"]
}
}
}'Core resources
- Contacts & Endpoints
- Register people and their push Endpoints (FCM/APNs device tokens) for Android and iOS.
- Messages & Notifications
- Single send and Broadcast via
/messages; Multi-send via/campaigns. On the push Channel the dashboard and docs call them Notifications. - Segments
- Target audiences from attributes your product supplies.
- Delivery visibility
- Inspect outcomes on the notification—same model the dashboard uses.
Your backend stays in charge
Your app
Chooses when someone should hear from you and what the message means for the business.
ComRaid
Queues work, talks to FCM, retries, and keeps delivery records—plus attribution IDs for conversions you measure.
Docs at docs.comraid.app. API base https://api.comraid.app. Also see FCM push.