Developer overview
How to think about the AverCare platform if you're building on or against it.
This section is the technical reference for engineers. It documents how clients talk to AverCare: the conventions every endpoint follows, how authentication works, and the API surface.
AverCare's API is the web app API — a single, session-authenticated surface that powers the product itself. The web, mobile, and watch clients all call into it. Start with conventions, then explore the surface map.
Before you start
Authentication
How sessions, identity, and access work.
API conventions
Formats, errors, validation, and streaming — read this first.
Web app API
The product's own API — chat, vitals, calendar, documents, scan, and more.
The big picture
Good to know
Because the mobile and watch apps call the same web API the website uses, "the API" and "the product" are nearly the same thing — there's very little backend that isn't reachable by a well-formed, authenticated request.