Bridge Mira

Bridge

Pull-model bridge: fetches hormone, cycle, and daily log data from the Mira API into HDS.

Data Synced

• Hormone readings (FSH, LH, E3G, PdG)
• Cycle information
• Daily logs (mucus, bleeding, temperature, etc.)

Flow

1. The user connects through the account app’s /connect (or the HDS webapp): the bridge runs the Mira OAuth, then returns to HDS’s own pages only, with a CMC offer that the user’s side accepts
2. Bridge calls Mira API endpoints (cycles, hormones, daily logs) and converts to HDS event types
3. Incremental sync using last-synced timestamp; a daily run on the cluster’s scheduler worker
4. The connector state (active, needs reauthorization, error, disconnected) is published as a sync-status/connector-v1 event on the user’s sync-status-mira stream
5. A user whose HDS grant was revoked is disconnected before Mira is called

Status

Production (1.10.3 as of 2026-10-05), listed in the HDS app catalog. Deploys carry a /status health check, so a crash-looping container never replaces a healthy one.

Tech Stack

• Node.js, lib-bridge-js framework
• Mira OAuth2 integration