Thank you for this summary! Agree that API should/will be a norm in the features of bio software platforms, especially with more demands for automation. There are a few more layers to this - 1) appropriate granularity for proper data mapping, 2) clear documentation, 3) more data efficient options such as web hooks and 4) ongoing maintenance to ensure reliability. These are things that not all software platforms with APIs would offer. Our development team (disclosure: I work for SciNote ELN) spent time on these to make sure we don't just have an API, but the API works effectively. There will be more demands for platforms to offer APIs, and then the question will become whose API is better in quality - something that not enough people are asking just yet, but should and will soon.
This is an awesome post--I'm trying not to subscribe to too many Techbio substacks but had to sub after reading this one 🫡
Thanks Elliot - would be great to chat!
Thank you for this summary! Agree that API should/will be a norm in the features of bio software platforms, especially with more demands for automation. There are a few more layers to this - 1) appropriate granularity for proper data mapping, 2) clear documentation, 3) more data efficient options such as web hooks and 4) ongoing maintenance to ensure reliability. These are things that not all software platforms with APIs would offer. Our development team (disclosure: I work for SciNote ELN) spent time on these to make sure we don't just have an API, but the API works effectively. There will be more demands for platforms to offer APIs, and then the question will become whose API is better in quality - something that not enough people are asking just yet, but should and will soon.
Couldn’t agree more on these points! Really appreciate you sharing the insights and would be great to speak to you more about it!
I would love to! Will be in touch via LinkedIn.