Push API

Centralized push notification dispatcher for OpComm tenant fan-out

push.opcommservice.com

Service Running
1.0.0
Version
Production
Environment
296716dc7e43
Machine
PROXY
Mode

Centralized Dispatch

All tenant push fan-outs flow through this service. OneSignal credentials live in one place; tenant App Services don't carry them after the cutover soaks. Provider swaps become a single-service change.

Correlation & Forensics

Every push carries pushGroupId plus event, case, hospital, and source-host context. Triage queries pivot end-to-end across [Push.*] (tenant) and [PushSend.*] (server) log lines on a single field.

Phase 2 Ready

Designed to grow into a durable PendingPush queue + IHostedService worker without changing the client surface. The PushSendResult shape already accommodates queued 202 responses.

API ENDPOINTS

General
Push (X-Api-Key required)
POST /api/v1/push/send Forward a OneSignal request — tenant fan-out call site
Calls to /api/v1/push/* require the X-Api-Key header. Configure on tenant hosts via Services:PushApi:ApiKey.