Many labs plan work in one system but book their instruments in another, which means extra work. For example: a scientist plans their experiment in an ELN, then books the instruments they need to run that experiment, and a lab manager logs a service visit in the maintenance system, but then blocks out the instrument's calendar by hand.
From today, your LIMS, ELN, maintenance system, instrument software and internal tools can create and update bookings in Calira directly through our API. Here's what's new.
Create, update, and search bookings
A connected system can now do most of what a person can do on the booking form, and it’s now possible to search through bookings.
- Book any instrument in one request. Send the instrument, a start time and an end time. The response says straight away whether the booking is confirmed or waiting for approval.
- Create recurring bookings. Create a daily, weekly, monthly or yearly series in one go, including unique patterns, e.g. "every Monday and Thursday".
- Book on behalf of a colleague. Admins and instructors can book for another lab member, so staff running samples for other teams can record the usage against the scientist who asked for the work.
- Group bookings. Add participants when you book. Calira checks they have access to the instrument and invites them as normal.
- Projects and add-ons. Assign the booking to lab projects and include add-ons such as consumables and training. Mandatory add-ons are enforced.
- Maintenance bookings. Block out time for preventative maintenance, calibration, cleaning or repairs.
- Search bookings. Filter bookings by instrument, owner, type, status, start or end time, created or updated date, and lab, with up to five conditions at once. To keep another system in step, ask for every booking created since the last sync.
Plans change, so bookings can be updated too. You can move the time, add or remove participants, or change projects and add-ons, and everyone affected will get the usual notifications.
Your booking rules still apply
When another system can write to your calendar, the obvious worry is that it will ignore your rules. It can't. Every booking made through the API goes through the same checks as one made in Calira: overlap protection, usage limits, minimum and maximum durations, advance notice and business hours. If an instrument needs approval, API bookings join the same queue as everyone else's.
When a rule blocks a booking, the API explains which rule it hit, so whoever is on the other end knows what to change.
Notes and files on bookings
Booking notes can now be added automatically:
- Post a note from another system. Instrument software could log run parameters when a session ends.
- Attach results, protocols or reports, up to 20 MB per file and 10 files per booking.
- Update notes later. New text replaces the old note text, and new files are added without overwriting existing ones.
- Notes sync to the Outlook event, the same as notes added in Calira.
Check before you book
The API allows your tooling to check a few things first:
- Free slots. See open time on an instrument across a window of up to two weeks. Booking rules are still checked when the booking is made.
- Add-ons. See which add-ons will apply to the person booking, and which are mandatory.
- Who can join. List the lab members with access to an instrument, for choosing group booking participants.
Create and update equipment
The API can also create and update instruments: name, category, manufacturer, model number, availability, booking rules, contacts, access groups, photos and documents such as SOPs. You can also manage training on equipment via dedicated training endpoints. New instruments can go from your asset register into Calira, ready to book.
You decide what each integration can do
- Reading and writing are separate permissions. A reporting integration can't make bookings unless you allow it.
- Every request runs as a real Calira user, with that user's access and nothing more.
- Integrations only work in the labs they've been authorised for.
What you could build
Few (if any) teams want the cost, commitment, and enormous workload of maintaining a single system that attempts to do absolutely everything in one go. It’s far more sensible now for teams to buy best-in-class for each tool, then integrate. For example:
- Push live updates from your asset lifecycle management system (ALM) to the Calira equipment list, excluding assets users don’t need to see or use (e.g. facilities equipment like HVAC)
- Book instrument time from your LIMS or ELN where and when the experiment is planned, against the right project code
- Link service and calibration schedules in your maintenance system so they show up in Calira, and so nobody books an instrument that's due for service
- Post run parameters and results files from the instrument software to the booking itself
Getting access
API access is included on Premium and Enterprise plans at no extra cost. To get started, follow the setup steps in our help centre, or talk to your customer success manager.
Not using Calira yet? Book a demo and we'll show you how the wider platform works.