REST API
API reference
A thin HTTP face over the diagnos SDK: one process, one service account, one live session. Every route requires a client certificate signed by the CA this deplo
On this page
A thin HTTP face over the diagnos SDK: one process, one service account, one live session. Every route requires a client certificate signed by the CA this deployment trusts — there is no other credential. Every non-2xx response is `{"error": {"code", "message", "trace_id"}}`; branch on `code`.
Endpoints #
patients #
Encrypted patient records: sealed in this process, versioned, never readable by the vault.
- GET
/v1/patientsList patients - POST
/v1/patientsCreate a patient - GET
/v1/patients/{patient_id}Get one patient - PUT
/v1/patients/{patient_id}Update a patient - DEL
/v1/patients/{patient_id}Move a patient to the trash - POST
/v1/patients/{patient_id}/archiveArchive a patient - POST
/v1/patients/{patient_id}/unarchiveUnarchive a patient - POST
/v1/patients/{patient_id}/restoreRestore a patient from the trash
exams #
Encrypted exams and their reports, each linked to one patient.
- GET
/v1/examsList exams - POST
/v1/examsCreate an exam - GET
/v1/exams/{exam_id}Get one exam - PUT
/v1/exams/{exam_id}Update an exam - DEL
/v1/exams/{exam_id}Move an exam to the trash - POST
/v1/exams/{exam_id}/archiveArchive an exam - POST
/v1/exams/{exam_id}/unarchiveUnarchive an exam - POST
/v1/exams/{exam_id}/restoreRestore an exam from the trash
drives #
Files and folders of one security group (`{sg}`), each file under its own key.
session #
The one SDK session this process holds, and the caller's mTLS identity.
health #
Liveness, behind mTLS like everything else.