Cool idea. You mentioned combating allergies and sleep problems, could this be utilised in future to monitor patients with other more serious medical conditions or post op recovery?
Launch HN: Vital (YC W20) – API for wearables and labs
11–20 of 31 posts
Re: Launch HN: Vital (YC W20) – API for wearables and labs
#12Re: Launch HN: Vital (YC W20) – API for wearables and labs
#13Very cool -- I'm curious how many different providers of at home testing you abstract away with your API and also if you have your own services arm or are abstracting away third party providers?
Re: Launch HN: Vital (YC W20) – API for wearables and labs
#14As one piece of feedback, the docs could be better. For example, at https://docs.tryvital.io/api-reference/data/workouts/#stream, I see "Get Daily Activity for user_id", but the endpoint seems to actually return time series data for a single workout. I see a bunch of oversights of this flavor.
Similarly, I'm not sure how pagination works or should work. In one list query, I see a result set of size 100. I'm not sure whether this is because only 100 items were pulled from the provider, or whether I can see more using pagination. Maybe this is in the docs, but I haven't seen it.
It would be good to have some provider-specific documentation to answer questions are set expectations around things like 1) how much historical data is available 2) details about the integration and its stability. For example, I assume with Peloton you are logging in with my credentials and using their internal API. Is this against their terms of service? Is there a risk of this breaking if they change their internal API, which obviously doesn't have the same governance considerations a public API would?
Nice work overall!
Re: Launch HN: Vital (YC W20) – API for wearables and labs
#15This looks cool. Congrats on the launch and progress so far! As one piece of feedback, the docs could be better. For example, at https://docs.tryvital.io/api-reference/data/workouts/#stream , I see "Get Daily Activity for user_id", but the endpoint seems to actually return time series data for a single workout. I see a bunch of oversights of this flavor. Similarly, I'm not sure how pagination works or should work. In…
This is why aggregating and standardising the data is hard, some API's are not public and in some cases we use credentials to generate access tokens which we then use to query the API, since we are aiding people in accessing their own data, we take a stance that people have a right to their own health data.
If the internal API does change there is some risk of breakage, we have built a tonne of monitoring around this to ensure that we stay up to date with this and react accordingly.
Re: Launch HN: Vital (YC W20) – API for wearables and labs
#16Re: Launch HN: Vital (YC W20) – API for wearables and labs
#17Wow Maitham, this looks amazing! We're building a similar product but it's specific to CPAP and sleep apena over at https://sleephq.com We're currently integrating with a few different CPAP manufacturers but we want to add other devices and wearables in the future and this looks like a great solution.
Re: Launch HN: Vital (YC W20) – API for wearables and labs
#18Maitham and his team have taken something that was mindbendingly painful and turned it into an API.
Patrick Collison says there's billion dollar companies wherever there's mountains of shit to deal with. That's what Maitham has done.