Monitoring Payer Health

Payer Health is a high-level view of how reliably each Payer Group is responding when Bridge sends eligibility requests to them. The status reflects how that payer’s system is behaving - response quality, errors, and availability - so you can see when a payer is degrading and decide when to rely on real-time eligibility vs. when to adjust flows (e.g. pause paid acquisition until a payer is healthy again).

For each Payer Group, Bridge exposes:

• Current status: HEALTHY, WARNING, or UNHEALTHY, based on recent eligibility request volume and error rates observed from those downstream calls.
• History: A timeline of status changes (health events) so you can see when a payer degraded or recovered.

Status is derived from the traffic Bridge sends to payers and the responses (or failures) returned. It is not a guarantee of future behavior, but is a reliable signal you can use for operational and product decisions.

Use cases

• Internal monitoring - Dashboards and alerts when a payer group moves to Warning or Unhealthy so ops or support can anticipate eligibility issues and communicate with members or providers.
• Marketing automation - Integrate health status into your marketing stack (e.g. CRM, ad platforms). For example: when a payer is Unhealthy, pause or reduce paid campaigns that drive traffic for that payer until status returns to Healthy, to avoid signups that cannot be verified in real time.

Dashboard

The Payer Network Status page in the Bridge Dashboard shows the current health status for each payer group and a summary of recent eligibility success rates. Use it for at-a-glance monitoring without calling the API.

API

• Current status - The Payer Group resource includes a health field with status and lastUpdatedAt. Use Get PayerGroup to request a payer group by ID or slug and read its current health.
• History - The Health Events endpoint for a payer group returns past status changes (e.g. HEALTHY → WARNING → UNHEALTHY and back). Use List Health Events to fetch the status transition timeline.

Poll these as needed for internal tools, dashboards, or data pipelines. See the API Reference for Payer Groups and related endpoints.

Webhooks

Subscribe to webhooks to react in real time when payer health changes:

• payer_group.health.updated - Fired when the current health status for a payer group changes (e.g. Healthy → Warning). Use the event to fetch the latest Payer Group (including health) and run your automation (e.g. pause ads, update internal status).
• payer_group.health_event.created - Fired when a new health event is recorded (status transition). Useful for building your own event log or analytics.

As with other Bridge webhooks, the payload is thin; use the Get Event API to retrieve full event details, then call the API for current state if needed.

Summary