Aniva is the Stripe for digital health. One REST API to order any of 2,500+ biomarkers for your patients, from a routine blood panel to whole-genome sequencing. You get structured JSON results, a live sandbox and clean docs. We run the labs, kits, couriers and the EU compliance stack (RiliBÄK, ISO 15189, GDPR) underneath. Diagnostics used to be the ugliest integration in health tech. Now it is three calls: create a profile, book a draw, read the result. Request a sandbox key and start shipping.
No reviews yetBe the first to leave a review for Aniva for Developers
Hunter
💡 Bright idea
📌
Hey Product Hunt, Robert from Aniva here.
While building our own product, we kept meeting teams who could ship a beautiful health product in weeks, then lost the better part of a year wiring up diagnostics. Labs, kits, couriers, results parsing, and a compliance stack underneath all of it.
In a way, diagnostics was the ugliest integration in health tech. So, we built the layer we wished existed.
Aniva for Developers is one REST API to order any of 2,500+ biomarkers, from a routine blood panel to whole-genome sequencing. Structured JSON results, a live sandbox, and docs you will actually read. We handle the labs, the logistics and the EU compliance (RiliBÄK, ISO 15189, GDPR, hosted in Germany). You handle the product and the patient.
If you have ever struggled with a lab integration to your digital health product, I would love to hear what made it painful and whether this would have saved you some time. Also, how we can improve our API and service in general.
- Request an API key here from our team: https://zeeg.me/aniva/developers
- Explore the API Docs here: https://docs.anivahealth.com
- Learn more here
Report
Webhooks for result delivery would save a lot of polling on our side. Could you emit an event the moment a biomarker result is ready, including the patient profile id and the specific panel code? That way our backend can reconcile and notify the clinician without us hammering the read endpoint every few seconds.
Report
Congrats on shipping this, the three-call flow sounds really nice. One thing I'd love to see in v1 is a built-in webhook + idempotency story for result delivery so my service can react the moment a lab posts structured JSON, rather than polling. Even a simple "result.updated" event with replay protection would make production rollouts way less scary for teams like ours handling PHI.
Report
Ship a small client library for at least Python or Node alongside the raw REST docs, since most teams will hit friction wiring up auth, polling for async results, and webhook signatures from scratch and a reference implementation would save a ton of time during eval.
Report
Hunter
@aleyna3zum That's really good feedback! Our team will talk it through with an open mind definitely. Because we are just getting started, let us know if you have any more thoughts or ideas on direction you would like to take this and step by step we will get there.
Robert from Aniva
Report
Three calls really does cover it. Spent a few minutes in the sandbox and the JSON came back cleaner than anything I've wrestled with from hospital lab portals, plus the EU compliance stack being already handled is huge.
Report
honestly the three-call flow sounds great, but one thing that would help us a lot is webhook subscriptions on result status changes so we don't have to poll. like basically fire a webhook when a biomarker result lands or when a draw appointment gets cancelled. would save a bunch of cron jobs on our end.
Report
The docs look genuinely clean and the sandbox-first approach is a nice move, lets you actually validate flows before wiring up real orders.
Webhooks for result delivery would save a lot of polling on our side. Could you emit an event the moment a biomarker result is ready, including the patient profile id and the specific panel code? That way our backend can reconcile and notify the clinician without us hammering the read endpoint every few seconds.
Congrats on shipping this, the three-call flow sounds really nice. One thing I'd love to see in v1 is a built-in webhook + idempotency story for result delivery so my service can react the moment a lab posts structured JSON, rather than polling. Even a simple "result.updated" event with replay protection would make production rollouts way less scary for teams like ours handling PHI.
Ship a small client library for at least Python or Node alongside the raw REST docs, since most teams will hit friction wiring up auth, polling for async results, and webhook signatures from scratch and a reference implementation would save a ton of time during eval.
@aleyna3zum That's really good feedback! Our team will talk it through with an open mind definitely. Because we are just getting started, let us know if you have any more thoughts or ideas on direction you would like to take this and step by step we will get there.
Robert from Aniva
Three calls really does cover it. Spent a few minutes in the sandbox and the JSON came back cleaner than anything I've wrestled with from hospital lab portals, plus the EU compliance stack being already handled is huge.
honestly the three-call flow sounds great, but one thing that would help us a lot is webhook subscriptions on result status changes so we don't have to poll. like basically fire a webhook when a biomarker result lands or when a draw appointment gets cancelled. would save a bunch of cron jobs on our end.
The docs look genuinely clean and the sandbox-first approach is a nice move, lets you actually validate flows before wiring up real orders.