Build with ENO
Connect patient documents, wearable data and interviews to a consistent health record through the ENO Partner API.
Contract version: 0.1.0-draft.3 · 72 operations · Draft for integration planning
This portal documents the proposed partner contract. Sandbox routes, credentials, SDK distributions and production availability have not been verified through this portal. All examples use synthetic data. The request playground is disabled while the contract is in draft.
Start your integration
| Your goal | Start here |
|---|---|
| Make your first request and upload a report | Quickstart |
| Understand credentials and patient permissions | Authentication and access |
| Upload documents and recover from delayed processing | Documents |
| Read reproducible evidence and matching results | Health data and snapshots |
| Add symptom collection to your application | Symptom assessments |
| Integrate interviews, wearables or a practitioner view | SDKs and embeds |
| Receive and verify notifications | Webhooks |
How the integration fits together
Your backend authenticates as an integration. ENO binds that integration to a verified Organisation, links the intended patient, and checks Patient Access Grants for clinical reads and uploads. Endpoint scopes identify permitted operations; grants identify permitted patient records.
Documents, wearables and reviewed interviews contribute source-owned observations. Immutable snapshots identify the evidence used for an analysis. Processing a document and making its observations available in a patient snapshot are separate milestones.
Explore the contract
Open the API reference for endpoint descriptions, parameters and schemas. Check availability before choosing a capability, and download integration resources for offline planning.
New to the design? Begin with one workflow: authenticate → link a synthetic patient → upload a document → read processing status → retrieve observations or a snapshot.