Built for the way labs actually work.
Nobody wants a second workflow. GenoAccel exposes a documented REST API, a command-line tool for the transfers that are too large for a browser, and a path into laboratory information systems.
01 · Integration surfaces
Four ways in.
| Surface | Use | State |
|---|---|---|
| REST API (/v1/) | Programmatic project, sample, upload and analysis management. Cursor pagination, ETag concurrency, localised problem+json errors. | In place |
| Command-line tool | The realistic way a 100 GB genome is uploaded — scriptable, resumable, checksum-verified. | Roadmap |
| Nextflow interoperability | The execution plane is Nextflow DSL2, so existing workflow knowledge transfers directly. | Roadmap |
| LIMS / LIS integration | Sample intake and result return inside an existing clinical workflow rather than alongside it. | Roadmap |
02 · What exists today
The API surface is real; the rest is specified.
The versioned REST API is built and continuously tested — projects, samples, sample-sheet import and the full multipart upload lifecycle, all organisation-scoped at the data layer with cross-tenant access covered by tests that require it to fail.
The command-line tool, Nextflow interoperability documentation and LIMS connectors are specified and scheduled. We list them as roadmap rather than as features, because a capability page that does not distinguish the two is not useful to anyone evaluating seriously.