Integrate once. Every sample follows.
The Pulse API, webhooks and structured results connect your app and your systems to the whole collection platform: order a regulated kit, run the programme, follow custody and receive the result, without stitching together a kit vendor, a courier, a custody system and a laboratory. Opening in early access.
Pulse on screen. Pulse as an API.
Pulse is where your team runs the platform: sign in, order kits, track every sample, see the invoices and pay. The Pulse API is the same platform for your systems. Instead of stitching together a kit vendor, a courier, a custody system and a laboratory integration, your software calls one API to order a regulated kit to a patient, run the programme, follow the sample under documented custody and receive a structured result, and everything it does shows up in Pulse for the people who work there.
Four calls, one programme.
The core capabilities the API exposes, each mapping to a real step on the platform.
Request a regulated collection pack to a patient address, configured for the right device and matrix.
Drive enrolment, scheduling and repeat collection for a cohort or a single patient journey.
Read the chain of custody as the sample moves: sealed, in transit and accessioned at the lab.
Receive structured results from the accredited laboratory, ready to land in your own system.
Collection behind your app.
Identity carried by Flow.
Your product stays your product. When one of your users needs a sample, your app hands off to Flow, which verifies who is collecting, records consent, registers the kit and guides the collection; the sample travels under documented custody, and the structured result returns to your system through the API or a webhook. Digital health, insurers and programme operators put blood, saliva, stool and urine collection behind their own front door without building any of it.
Structured, where your systems read.
Results arrive as structured, ID-matched data rather than PDFs, ready for a laboratory information system, an electronic record or a data platform. Custody events and result deliveries can fire webhooks, so nothing is polled. Invoices for the work leave as structured e-invoices over Peppol, delivered into your counterparties’ own systems.
Sovereign, and clean to build on.
Versioning and a changelog arrive with general availability. For the platform your team works in, see Pulse.
Pulse today. The API in early access.
Pulse runs the platform for customers now. The API is opening in early access: request access and we set you up with credentials, reference docs and a sandbox to build against. Versioning and a changelog arrive with general availability.
Good to know.
What can the Pulse API do?
Order regulated collection kits to patients, orchestrate enrolment and repeat collection, track chain of custody as a sample moves, and receive structured results from an accredited laboratory, the whole collection platform behind one API.
Is there a sandbox and documentation?
Documentation and a sandbox are opening with the API. Request early access and we will provision credentials and reference docs so you can build against the sandbox.
Is the API generally available?
Not yet. Pulse runs the platform for customers today; the API is in early access, and we onboard integration partners directly. Request access and we set you up.
Can we put collection behind our own app?
Yes. Your app hands off to Flow for identity, consent, kit registration and the guided collection, and the result returns to your system through the API or a webhook.
Do you offer webhooks?
Yes. Custody events and result deliveries can notify your system as they happen; the event list comes with the reference docs in early access.
Where is data processed?
Pulse is EU-sovereign: data is processed within the EU and handled GDPR-natively, and it is built so the patient owns their data with verifiable provenance.
Integrate with Humans Nexus.
Tell us what you want to connect and we will set you up with a sandbox and docs.