Skip to content

Support Service

Service
URL: https://support-api.datasafe.dev

Server side of the Health Data Safe support channel. Each platform has one support group account (hds-support); HDS staff answer from the Support Console as CMC members of that group. The service holds the group’s token and does what a member cannot.

  • Reply relay: members cannot write chat, so agents post replies here; the service writes them with the group token, prefixed with the agent’s name.
  • Presence: “is someone online?”, from the console’s heartbeats.
  • Offline email: one content-free “the HDS team answered you” email at the first answer; the address lives only in the service’s SQLite and is deleted after that email, or after 30 days.
  • Close + revoke and un-join cleanup: the group’s copy of a conversation never outlives the relationship.
  • Invite publication: the group’s permanent open link (GET /public/config) and its rotation.
  • Public: GET /public/config, GET /public/presence, POST /notify, GET /status
  • Agents (membership token): POST /agent/heartbeat, GET /agent/presence, POST /agent/reply, POST /agent/close
  • Node.js 24 (native TypeScript), Express, SQLite, @pryv/cmc through hds-lib
  • Telemetry through hds-observability-js only
  • CI-built image deployed on Dokku: demo support-api.datasafe.dev, prod support-api.hds.ngo
  • Email through the Google Workspace SMTP relay, from support@healthdatasafe.org