Ingest a notification event
Creates one Notification per recipient and dispatches it to the resolved delivery channels (websocket, email, sms, push). Called by other backend services, not directly by frontends.
Authorizations
Enter your JWT token in the format: Bearer
Body
Inbound payload from other services posting a notification event.
Example: { "source_service": "assignment-service", "notification_type": "task.assigned", "actor_id": "uuid", "recipient_ids": ["uuid-1"], "title": "New task assigned to you", "body": "STORY-123 has been assigned to you", "data": {"task_id": "uuid", "entity_reference": "STORY-123"}, "entity_type": "task", "entity_id": "uuid", "channels": ["websocket", "email"], "recipient_meta_map": { "uuid-1": {"email": "user@example.com", "phone": "+254700000000"} } }
Example (Vibe47 content, push): { "source_service": "digi-content", "notification_type": "episode.published", "actor_id": "uuid", "recipient_ids": ["uuid-1"], "title": "New episode of Nairobi Nights", "body": "S2E4", "data": {"show_id": "uuid"}, "entity_type": "episode", "entity_id": "uuid", "channels": ["push"] }
For "push", entity_type/entity_id are mapped to content_ref/content_id in the FCM data payload (see notifications.services.channels.push.PushChannel) and delivered to the recipient's registered device tokens.
1 - 641 - 6411 - 25564websocket- websocketemail- emailsms- smspush- push
websocket, email, sms, push Maps recipient_id (str) → {email, phone}. Required for email/SMS channel delivery.
