Vital
Vital (now operating as Junction, formerly tryVital) is a health-data API platform that gives digital-health, virtual-care, diagnostics, wellness, and EHR/EMR builders a single integration to wearable-device data and nationwide lab testing. Connect 300+ wearables and health devices — Apple HealthKit, Android Health Connect, Oura, Whoop, Garmin, Fitbit, Withings, Dexcom, Freestyle Libre, Withings, Polar, and the rest — through the Vital Link Widget; ingest normalized daily summaries and per-sample timeseries for sleep, activity, body, workouts, heart rate, HRV, glucose, blood pressure, SpO2, ECG, and menstrual cycle; order at-home testkits, at-home phlebotomy, walk-in / Patient Service Center lab collection, and on-site collection across all 50 U.S. states; retrieve structured biomarker results; and run Junction Sense continuous queries to turn raw data into clinically actionable insights. Backed by SOC 2 Type 2, ISO 27001, GDPR-ready, and HIPAA-compliant infrastructure with both US and EU regional deployments.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Vital the way a machine reads it — 104 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Vital scores 66.7/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Vital
Each block below is one kind of artifact we hold for Vital. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Vital Management API
Programmatically manage all Junction regional and global resources for your organization. Authenticated with a separate x-vital-management-api-key, this API governs organization...
Vital Aggregate API
The Aggregate API from Vital — 3 operation(s) for aggregate.
Vital compendium API
The compendium API from Vital — 2 operation(s) for compendium.
Vital insurance API
The insurance API from Vital — 3 operation(s) for insurance.
Vital introspect API
The introspect API from Vital — 2 operation(s) for introspect.
Vital lab_account API
The lab_account API from Vital — 1 operation(s) for lab_account.
Vital lab_report API
The lab_report API from Vital — 2 operation(s) for lab_report.
Vital lab_tests API
The lab_tests API from Vital — 9 operation(s) for lab_tests.
Vital link API
The link API from Vital — 13 operation(s) for link.
Vital order API
The order API from Vital — 32 operation(s) for order.
Vital order_transaction API
The order_transaction API from Vital — 3 operation(s) for order_transaction.
Vital orders API
The orders API from Vital — 1 operation(s) for orders.
Vital payor API
The payor API from Vital — 1 operation(s) for payor.
Vital providers API
The providers API from Vital — 1 operation(s) for providers.
Vital summary API
The summary API from Vital — 15 operation(s) for summary.
Vital team API
The team API from Vital — 5 operation(s) for team.
Vital timeseries API
The timeseries API from Vital — 80 operation(s) for timeseries.
Vital user API
The user API from Vital — 16 operation(s) for user.
Scroll within the panel for all 18 ·
Postman Collections 7
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Vital Lab Report Parser API
POSTMANVital Lab Testing API
POSTMANVital Link API
POSTMANVital Sense API
POSTMANVital Team API
POSTMANVital Users API
POSTMANVital Wearables Data API
POSTMANScroll within the panel for all 7 ·
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Vital Lab Report Parser API
OPEN COLLECTIONVital Lab Testing API
OPEN COLLECTIONVital Link API
OPEN COLLECTIONJunction API
OPEN COLLECTIONVital Sense API
OPEN COLLECTIONVital Team API
OPEN COLLECTIONVital Users API
OPEN COLLECTIONVital Wearables Data API
OPEN COLLECTIONScroll within the panel for all 8 ·
Arazzo Workflows 10
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Vital Schedule an At-Home Phlebotomy Draw
Confirm phlebotomy coverage for an address, place an at-home order, find a slot, and book it.
ARAZZOVital Await Lab Order Completion and Retrieve Results
Poll an existing order until it completes, then pull its result metadata and raw results.
ARAZZOVital Browse Lab Tests and Inspect Markers
List your team's lab tests, fetch one in detail, and enumerate its biomarkers.
ARAZZOVital Cancel a Lab Order and Send the User a Portal Link
Cancel an order, confirm the cancellation, then mint a communications portal URL deeplinked to it.
ARAZZOVital Create a Lab Order and Poll Until Resolved
Place an order set lab order for a user and poll its lifecycle status until it completes, cancels, or fails.
ARAZZOVital Connect a Demo Provider and Verify Connected Sources
Create a user, attach a demo provider, then confirm the connection landed on the user record.
ARAZZOVital Provision a User and Hand Off a Mobile Sign-In Token
Create a Vital user, mint a mobile sign-in token, and read back the user's connected providers.
ARAZZOVital Onboard a User and Connect a Wearable
Create a Vital user, mint a Link token, and surface the available providers to connect.
ARAZZOVital Create and Register a Lab Testkit Order
Create an unregistered testkit order, register it against a sample, then read the order back.
ARAZZOVital Inventory a User's Connected Devices
Resolve a user by client_user_id, list their devices, and fetch the first device in detail.
ARAZZOScroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Vital Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Vital Io Finops
FINOPSFeatures 13
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
300+ wearable and health-device integrations
Apple HealthKit, Android Health Connect, Samsung Health, Oura, Whoop, Garmin, Fitbit, Withings, Polar, Strava, Wahoo, Cronometer, Ultrahuman, Peloton, Zwift, Hammerhead, Dexcom ...
Vital Link Widget and Connect app
Drop-in user-facing UI that handles OAuth, email/password, and mobile-SDK connection flows. Generate a one-time Link token, hand it to the widget or Connect app, and the widget ...
Nationwide lab-testing network
A single API to order at-home testkits, at-home phlebotomy, walk-in / Patient Service Center collection, and on-site collection across all 50 US states including NY, NJ, and RI ...
Normalized biomarker and timeseries schema
Every supported device, lab, and provider is mapped onto Vital's normalized schema so your app sees one Sleep, one Activity, one Heart Rate, one Glucose, one Biomarker — regardl...
Junction Sense — continuous queries
Define a continuous aggregate query once (e.g. "weekly HRV baseline", "monthly glucose time-in-range") and Junction recomputes it as new data lands. Read the materialized result...
Webhooks with Svix-backed delivery
Daily-data created/updated events for every wearable resource, historical-pull completion, lab-test orders + appointments + critical results, lab-report parser status, provider ...
ETL pipelines (BYO destination)
Pipe ingested data directly into your own infrastructure — Azure Event Hubs, Google Cloud Pub/Sub, or RabbitMQ — instead of (or in addition to) webhooks. Configurable per team.
US and EU regional deployments
Pick your data residency — production and sandbox base URLs are split into api.us.junction.com and api.eu.junction.com. Regional API key prefixes (pk_us, pk_eu, sk_us, sk_eu) pr...
Mobile SDKs for HealthKit and Health Connect
First-party Swift, Kotlin, Flutter, and React Native SDKs that wrap Apple HealthKit and Android Health Connect, plus Bluetooth Devices SDKs for direct device pairing (Accu-Chek,...
Typed server SDKs (Fern-generated)
Python, TypeScript/Node, Go, and Java SDKs are generated from a single Fern API spec — keeping the SDK surface in lockstep with the underlying OpenAPI 3.1 definition.
HIPAA, SOC 2 Type 2, ISO 27001, GDPR-ready
BAA-eligible HIPAA infrastructure, SOC 2 Type 2 and ISO 27001 attestations, plus EU-region GDPR-aligned deployment. Suitable for regulated digital-health, virtual-care, and diag...
Sandbox with synthetic data
Dedicated sandbox environment (api.sandbox.us.junction.com / .eu.) with sk_* API keys, demo providers, and synthetic user lifecycle simulation so you can build and test without ...
Lab report parser
Submit existing lab-result PDFs (from other labs, historical patient records) and Vital normalizes them into the same biomarker schema as Junction-fulfilled orders.
Scroll within the panel for all 13 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Vital Io Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Vital API Rules
SPECTRALVital API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
VitalActivitySummary
JSON SCHEMAVitalHeartRateTimeseries
JSON SCHEMAVitalLabOrder
JSON SCHEMAVitalLabResult
JSON SCHEMAVitalProvider
JSON SCHEMAVitalSleepSummary
JSON SCHEMAVitalUser
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Vital Lab Order Structure
JSON STRUCTUREVital User Structure
JSON STRUCTUREExamples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Vital Create Order Example
EXAMPLEVital Create User Example
EXAMPLEVital Lab Result Example
EXAMPLEVital Link Token Example
EXAMPLEVital Sleep Summary Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Virtual-first / digital-health clinics
Add wearable monitoring and ordering of standard lab panels to telehealth visits without integrating dozens of device APIs and lab vendors.
Consumer diagnostics and wellness platforms
White-label at-home testkits, deliver results in-app, and pair them with continuous wearable context (sleep, HRV, glucose) to drive coaching and lifestyle programs.
EHR / EMR and healthcare SaaS providers
Embed Junction as a labs-and-devices module inside an EHR/EMR product so customers get ordering, results, and wearable data without leaving the chart.
Cardiometabolic and CGM programs
Pull continuous-glucose-monitor data from Dexcom, Freestyle Libre, and Abbott LibreView; pair with lab biomarkers (HbA1c, lipid panel, fasting insulin); compute glucose-variabil...
Sleep, recovery, and performance apps
Normalized sleep, sleep-cycle, HRV, workout, and recovery data from Oura, Whoop, Garmin, Fitbit, Apple Watch, and 25+ other devices in one schema.
Women's-health and fertility platforms
Menstrual-cycle, basal-body-temperature, and hormone-panel lab data combined for cycle tracking and fertility coaching.
Population-health and research cohorts
Backfill historical wearable + lab data across thousands of users via bulk-import, bulk-pull, and historical-pull endpoints. Push to ETL pipelines for in-house analytics.
AI agents over patient health data
Expose normalized wearable + lab data to AI agents (via Naftiko capabilities or MCP) so agents can reason over a patient's biomarkers, sleep, and activity without bespoke per-so...
Scroll within the panel for all 8 ·
Integrations 12
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apple HealthKit
First-class iOS Swift SDK plus Flutter / React Native bindings stream HealthKit categories (sleep, activity, HR, HRV, workouts, ECG, glucose, blood pressure, body) into the Vita...
Android Health Connect
Kotlin / Flutter / React Native SDKs read from Android Health Connect — Samsung Health, Google Fit successor, Fitbit Android, and other Health Connect publishers — through one b...
Samsung Health
Read Samsung-Health data on Android via the Health SDK without writing Samsung-Health-specific code.
Oura, Whoop, Garmin, Fitbit, Withings, Polar
OAuth-based cloud providers, all behind one Link Widget flow and one normalized data schema.
Dexcom and Freestyle Libre (cloud + BLE)
Continuous-glucose monitoring via Dexcom cloud (v3), Freestyle Libre cloud, Abbott LibreView, and direct Bluetooth Low Energy for newer Libre models. Normalized into the glucose...
8Sleep, Peloton, Zwift, Hammerhead
Non-OAuth cloud providers covering connected mattresses and indoor-training platforms.
Strava, Wahoo, Cronometer, Ultrahuman
Additional OAuth providers covering endurance training, nutrition logging, and metabolic wearables.
Bluetooth devices via Devices SDK
Accu-Chek, Beurer BLE, Contour, Freestyle Libre BLE, Omron BLE — paired directly to the user's phone through the Vital Devices SDK and reported back through the same API.
ETL destinations (Azure / GCP / RabbitMQ)
Forward ingested data to Azure Event Hubs, Google Cloud Pub/Sub, or RabbitMQ for in-house analytics pipelines.
Anthropic Claude
Junction's normalized health-data API is a natural fit as a tool surface for Anthropic Claude agents — pair the Vital OpenAPI specs in this repo with Claude tool calling (or Naf...
Svix
Vital's webhook delivery is Svix-backed — your team can be issued a Svix management portal URL for managing webhook endpoints, signing secrets, and delivery history.
Fern
The Junction OpenAPI definition and the Python/TypeScript/Go/Java server SDKs are generated with Fern from a single source of truth (github.com/tryVital/vital-fern-api).
Scroll within the panel for all 12 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
For digital-health builders
One API for the two hardest health-data integrations — wearables and labs — so a small team can ship a clinical-grade product without negotiating individual vendor contracts.
For diagnostics companies
Add a software layer (ordering, results, patient app) over a managed nationwide lab network without building lab-vendor integrations or running a fulfillment ops team in-house.
For platforms adding wearable data
Replace per-device SDKs and OAuth flows with one Link Widget and one normalized timeseries + summary schema covering 300+ devices.
For enterprises
SOC 2 Type 2, ISO 27001, HIPAA, GDPR-ready, US/EU regional deployments, white-label app branding, uptime SLAs, prioritized integrations, ETL pipelines, and Analytics API access ...
Resources
Every other property we hold for Vital — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 20
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 20 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/vital-io · machine-readable index on apis.io