Partners

We want to integrate Oxynet. What happens next?

The first three steps are self-service and need no conversation. Technical access can begin with a representative CPET file; commercial terms depend on the deployment model, the scope and the partnership structure, and come later.

API v1 · docs 1.0 · updated 2026-09-22

From first look to production

01Self-service
Check compatibility
Find your export on the formats page.
02Self-service
Download the sample
Synthetic data, so nothing of yours is needed yet.
03Self-service
Test the API
Request a key and run the quick start.
04With Oxynet
Send a representative file
One de-identified export from your system.
05With Oxynet
Feasibility assessment
What parsed, what the format needed, what was refused and why.
06With Oxynet
Integration prototype
Against the hosted API, on your side.
07With Oxynet
Validation
Your cohort, your acceptance criteria, your regulatory position.
08With Oxynet
Production deployment
Hosted, local or embedded.

Phase one needs one file and no commitment

Send a de-identified export with the device, software version and what you want back. Send a representative file. Remove names and dates of birth from the file and its name before sending.

Run a test yourself

There is deliberately no public, unauthenticated upload for your own files: a CPET export is health data. With a trial key you can upload a de-identified export and read the upload summary, which answers most compatibility questions on its own: the detected format, every channel present and absent with the reason, and the sampling. The web application also accepts files for a quick look.

Request sandbox access Quick start

Deployment options

Hosted API

Production

Your software calls app.oxynet.net over HTTPS. Fastest route to a working integration; model updates are central.

Recordings leave the local environment, and connectivity becomes a dependency.

Local engine

By arrangement

The engine on your infrastructure. Recordings never leave the institution.

You own deployment and updates, and models have to be shipped to you. Scoped per partner.

Embedded

By arrangement

Interpretation inside the product, during the test rather than after it.

The tightest coupling and the longest conversation about versioning and support. A joint scoping exercise, not a shipping product.

The engine is the same in all three. A partnership can start on the hosted API and move inward without the interpretation changing underneath the customer.

Four routes

Integrate

Call Oxynet from software you already ship. Your interface, your reporting, your customer relationship; our physiology, kept current.

Embed

Make it part of the product itself, on your infrastructure or on the device, for interpretation during the test rather than after it.

Validate

Run cohorts through the engine to establish new capabilities and the evidence behind them. Oscillation analysis needs a second population before it can leave research, and that would be a collaboration.

Partner

A broader commercial relationship around distribution, licensing or joint product development.

Commercial and licensing structure follows from the route, the deployment and the scope of rights, so it is not fixed here and no price list is published.

When to get in touch

An API key

A sentence on what you want to build.

A feasibility check

One de-identified file from your system.

A partnership

Licensing, embedding, validation, distribution.

andrea.zignoli@unitn.it

Sharing a dataset? Our data transfer agreement template (fillable PDF) shows every choice with its alternatives. If your institution has its own template, we will work from yours.