ELN & lab-software integration

For vendors and in-house teams connecting electronic lab notebooks, sample managers, or dashboards to OpenIRIS facilities. Build once — the same integration serves every OpenIRIS member institution running your product.

Live today LIVE

With resources:read you can browse a provider's instrument and service directory — the anchor for linking experiment records to facility assets:

GET /v1/resources?filter[class]=scheduled&sort=name

{
  "data": [{
    "id": 4165,
    "guid": "1f0a…",
    "name": "Lightsheet UltraMicroscope II",
    "class": "scheduled",
    "status": "active",
    "provider_id": 1300,
    "manufacturer": "LaVision BioTec",
    "serial_number": "…",
    "timezone": "Europe/Berlin",
    "links": { "self": "…/v1/resources/4165" }
  }], …
}

• class values: scheduled (bookable instruments), application, service, scheduled_addon, event.
• guid is globally stable — prefer it over id as your foreign key if you persist references long-term.
• timezone is the facility's IANA zone — render booking times in it.

On the roadmap PROPOSED

The pieces that complete the ELN story are specified in the proposed contract and open for your feedback — vendor input directly shapes prioritisation:

• Bookings read — link an experiment to the session in which the data was acquired (GET /v1/bookings?filter[resource_id]=…).
• external_reference round-trip — a ≤35-char integrator-owned field on bookings, requests, and resources (sized for identifiers like eLabNext's externalBarcode), so your records and OpenIRIS records point at each other.
• Webhooks — booking.created / booking.cancelled push instead of polling.
• Form submissions — structured acquisition metadata attached to a booking, with typed entity-reference fields.