Developer API: the essentials.
- 01
Start with the workflow and required data
Describe the user action that should trigger an integration and the minimum information needed at each step. Separate wearable data, uploaded records and derived insights. This lets the teams discuss a concrete integration instead of assuming that every source and output is available through one endpoint.
- 02
Request the actual interface specification
Ask ONU for API credentials, the current supported interface, authentication method, environments, rate limits, versioning policy and access requirements. Build against the contract you receive, not an example diagram.
- 03
Plan failure handling before launch
Clarify how the integration represents missing data, stale readings, revoked access, duplicate deliveries and partial failures. Agree retry behavior, reconciliation and ownership of support incidents. A reliable health-data experience needs to distinguish “no new reading” from “everything is normal.”
- 04
Prepare a useful technical brief
Include your platform, target workflow, data categories, expected scale, deployment regions and development timeline. Identify a technical contact and the organization responsible for data governance. Send no access tokens or identifiable health records through the general enquiry form.
Find the right way to work together.
