SDKs, wearable connections and practitioner embeds

Availability: draft. The SDK names, package coordinates, platform minima and delivery dates in the design are proposals. No downloadable ENO SDK distribution has been verified for this portal.

Interviewer integration

The intended flow is a backend call to POST /users/{userId}/sdk-tokens, followed by a short-lived user token supplied to the mobile SDK through a token-provider callback. Request only the approved interviewer capability. The application never holds partner credentials.

Discover enabled interview types through GET /interview-types. Backend reads use GET /interviews/{interviewId}; results can be announced by interview.results_ready. Transcript access remains separately governed by the patient's interview grant.

Before distributing an SDK, confirm artifact coordinates, supported OS versions, microphone declarations, consent behavior, resume semantics, SDK-facing routes and token audience/revocation policy. These items require verified release documentation.

Wearable collection

On-device collection and cloud provider connections use different flows. Cloud connections start with POST /users/{userId}/connections and a hosted authorization URL. Bind callback state to the intended patient and restrict redirect destinations to registered origins.

Use GET /providers and, once implemented, GET /integration/capabilities to identify enabled providers and metrics. Do not advertise a provider solely because its name occurs in the draft enum. Garmin and platform SDK readiness require explicit verification.

Wearable disconnection stops future access. Purging historical data is a separate operation requiring its own authorization and cleanup semantics.

Practitioner view

POST /embed-sessions is intended to issue a one-time bootstrap URL for a patient-scoped practitioner session. Requested permissions are bounded by server policy. Practitioner identity is verified or audited as a trusted partner assertion, not accepted as an unrestricted role claim.

Register the exact allowed embedding origin. Recheck patient access during the session, validate postMessage origins and sources, and expire sessions on revocation or erasure. The draft's eight-hour session duration does not promise eight hours of continuing patient access.

Planning consumer screens

For each screen, define the API resource, patient access category, pending state and insufficient-evidence state before adding the SDK or embed. Use the availability matrix to keep planned capabilities distinct from verified releases.

Partner API 0.1.0-draft.3 · Draft contract · Sandbox and SDK availability require confirmation.