VivaLNK

VivaLNK (Vivalink) is a connected-health company providing medical-grade wearable biosensors and a Biometrics Data Platform for remote patient monitoring (RPM), hospital-at-home, and decentralized clinical trials. Its wearable sensors capture ECG, heart rate, heart rate variability, respiratory rate, RR interval, body/axillary temperature, SpO2, blood pressure, and three-axis accelerometer data. Mobile edge clients read the sensors over Bluetooth Low Energy (BLE) and deliver data to the cloud over RESTful HTTPS services (Amazon API Gateway plus Amazon Kinesis for near-real-time ingestion). The platform exposes machine-to-machine (M2M) cloud web-service APIs, webhook push, FHIR-based integration, and bulk data-file downloads for EHR, CTMS, and clinical-application integration. The developer surface is delivered through VivaLNK's SDK and Developer Program and is partner-gated; the full API reference is provided under license rather than published openly, so the endpoints described here are modeled from VivaLNK's documented platform capabilities.

VivaLNK publishes 5 API contracts indexed on the APIs.io network, including Devices API, FHIR API, Subjects API, and 2 more. Tagged areas include Connected Health, Remote Patient Monitoring, RPM, Wearables, and Biosensors.

The VivaLNK catalog on APIs.io includes 1 Spectral governance ruleset.

VivaLNK’s developer surface includes authentication, documentation, signup flow, engineering blog, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.7/100 thin ▬ flat Agent 19/100 agent aware Front door AI 1/6 silent Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

Connected Health Remote Patient Monitoring RPM Wearables Biosensors Biometrics ECG Vital Signs Digital Health IoT Clinical Trials

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Health Information Management

BC-2900

FHIR

GET /fhir/Observation

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 31.7/100 · thin

Contract Quality 9.5 / 19

Developer Ergonomics 3.8 / 15

Access Clarity 2.6 / 15

Operational Transparency 1.2 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 0.7 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vivalink/"><img src="https://apis.io/badge/vivalink/card.svg" alt="VivaLNK on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 17.0 — up to +16.6 composite points Ask about this →
Developer Ergonomics scores 25.0 — up to +15.0 composite points Ask about this →
Contract Quality scores 50.4 — up to +12.4 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/vivalink/apis.yml: open an issue on github.com/api-evangelist/vivalink to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Health and Wellness (consumer health, fitness, wearables)	regulated	40.7 (thin)	-	-
Biometrics Testing (biometric recognition vendors, identity verification depth)	regulated	40.7 (thin)	-	-
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	regulated	40.7 (thin)	-	-
FDA Device Establishments (radiology, nuclear medicine, cardiovascular, robotic surgery)	regulated	40.7 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

VivaLNK Devices API

VivaLNK wearable biosensors and their assignment to subjects.

VivaLNK FHIR API

HL7 FHIR R4 resources for EHR/CTMS interoperability.

VivaLNK Subjects API

Subjects (patients / study participants) enrolled for monitoring.

VivaLNK Vital Signs API

Biometric measurements captured from wearables.

VivaLNK Webhooks API

Subscriptions for pushed biometric data and alert events.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

VivaLNK Biometrics Data Platform API (Modeled) Devices API

OPEN COLLECTION

VivaLNK Biometrics Data Platform API (Modeled) Devices FHIR API

OPEN COLLECTION

VivaLNK Biometrics Data Platform API (Modeled) Devices Subjects API

OPEN COLLECTION

VivaLNK Biometrics Data Platform API (Modeled) Devices Vital Signs API

OPEN COLLECTION

VivaLNK Biometrics Data Platform API (Modeled) Devices Webhooks API

OPEN COLLECTION

VivaLNK Biometrics Data Platform API (Modeled)

OPEN COLLECTION

VivaLNK API pricing

Not yet checked against VivaLNK's own pricing page. Compiled by API Evangelist on 2026-07-05 from www.vivalink.com/vivalink-sdk; confirm before you rely on a figure.

Plan	Price
Developer Program / SDK enterprise	—
Biometrics Data Platform enterprise	—
Enterprise / Clinical Trials enterprise	—

Plan details, limits and sources →

Rate limits

Cloud API Requests: not published requests
Ingestion Throughput: provisioned records
Near-Real-Time Read: not published requests

Compiled by API Evangelist, not yet checked against VivaLNK's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

VivaLNK Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

VivaLNK Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

VivaLNK Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

VivaLNK API Rules

58 rules · 55 error-severity 1 warn-severity 2 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

VivaLNK Authentication

http · 1 scheme

SECURITY

VivaLNK Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

VivaLNK Agentic Access

16 operations · 8 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: vivalink
url: https://raw.githubusercontent.com/api-evangelist/vivalink/refs/heads/main/apis.yml
name: VivaLNK
kind: company
description: VivaLNK (Vivalink) is a connected-health company providing medical-grade wearable biosensors and a Biometrics
  Data Platform for remote patient monitoring (RPM), hospital-at-home, and decentralized clinical trials. Its wearable sensors
  capture ECG, heart rate, heart rate variability, respiratory rate, RR interval, body/axillary temperature, SpO2, blood pressure,
  and three-axis accelerometer data. Mobile edge clients read the sensors over Bluetooth Low Energy (BLE) and deliver data
  to the cloud over RESTful HTTPS services (Amazon API Gateway plus Amazon Kinesis for near-real-time ingestion). The platform
  exposes machine-to-machine (M2M) cloud web-service APIs, webhook push, FHIR-based integration, and bulk data-file downloads
  for EHR, CTMS, and clinical-application integration. The developer surface is delivered through VivaLNK's SDK and Developer
  Program and is partner-gated; the full API reference is provided under license rather than published openly, so the endpoints
  described here are modeled from VivaLNK's documented platform capabilities.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/vivalink.png
tags:
- Connected Health
- Remote Patient Monitoring
- RPM
- Wearables
- Biosensors
- Biometrics
- ECG
- Vital Signs
- Digital Health
- IoT
- Clinical Trials
created: '2026-07-05'
modified: '2026-07-05'
specificationVersion: '0.23'
apis:
- aid: vivalink:vivalink-devices-api
  name: VivaLNK Devices API
  description: VivaLNK wearable biosensors and their assignment to subjects.
  humanURL: https://www.vivalink.com/vitals-data-services
  baseURL: https://api.vivalink.com
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/vivalink-devices-api-openapi.yml
  - type: Documentation
    url: https://www.vivalink.com/vivalink-sdk
  - type: Documentation
    url: https://www.vivalink.com/vitals-data-services
  - type: PostmanCollection
    url: collections/vivalink.postman_collection.json
  - type: OpenCollection
    url: collections/vivalink.opencollection.json
  - type: Documentation
    url: https://www.vivalink.com/wearable-products
  - type: Documentation
    url: https://aws.amazon.com/blogs/apn/next-gen-patient-monitoring-with-vivalinks-intelligent-biometrics-platform-and-aws/
- aid: vivalink:vivalink-fhir-api
  name: VivaLNK FHIR API
  description: HL7 FHIR R4 resources for EHR/CTMS interoperability.
  humanURL: https://www.vivalink.com/vitals-data-services
  baseURL: https://api.vivalink.com
  tags:
  - FHIR
  properties:
  - type: OpenAPI
    url: openapi/vivalink-fhir-api-openapi.yml
  - type: Documentation
    url: https://www.vivalink.com/vivalink-sdk
  - type: Documentation
    url: https://www.vivalink.com/vitals-data-services
  - type: PostmanCollection
    url: collections/vivalink.postman_collection.json
  - type: OpenCollection
    url: collections/vivalink.opencollection.json
  - type: Documentation
    url: https://www.vivalink.com/wearable-products
  - type: Documentation
    url: https://aws.amazon.com/blogs/apn/next-gen-patient-monitoring-with-vivalinks-intelligent-biometrics-platform-and-aws/
- aid: vivalink:vivalink-subjects-api
  name: VivaLNK Subjects API
  description: Subjects (patients / study participants) enrolled for monitoring.
  humanURL: https://www.vivalink.com/vitals-data-services
  baseURL: https://api.vivalink.com
  tags:
  - Subjects
  properties:
  - type: OpenAPI
    url: openapi/vivalink-subjects-api-openapi.yml
  - type: Documentation
    url: https://www.vivalink.com/vivalink-sdk
  - type: Documentation
    url: https://www.vivalink.com/vitals-data-services
  - type: PostmanCollection
    url: collections/vivalink.postman_collection.json
  - type: OpenCollection
    url: collections/vivalink.opencollection.json
  - type: Documentation
    url: https://www.vivalink.com/wearable-products
  - type: Documentation
    url: https://aws.amazon.com/blogs/apn/next-gen-patient-monitoring-with-vivalinks-intelligent-biometrics-platform-and-aws/
- aid: vivalink:vivalink-vital-signs-api
  name: VivaLNK Vital Signs API
  description: Biometric measurements captured from wearables.
  humanURL: https://www.vivalink.com/vitals-data-services
  baseURL: https://api.vivalink.com
  tags:
  - Vital Signs
  properties:
  - type: OpenAPI
    url: openapi/vivalink-vital-signs-api-openapi.yml
  - type: Documentation
    url: https://www.vivalink.com/vivalink-sdk
  - type: Documentation
    url: https://www.vivalink.com/vitals-data-services
  - type: PostmanCollection
    url: collections/vivalink.postman_collection.json
  - type: OpenCollection
    url: collections/vivalink.opencollection.json
  - type: Documentation
    url: https://www.vivalink.com/wearable-products
  - type: Documentation
    url: https://aws.amazon.com/blogs/apn/next-gen-patient-monitoring-with-vivalinks-intelligent-biometrics-platform-and-aws/
- aid: vivalink:vivalink-webhooks-api
  name: VivaLNK Webhooks API
  description: Subscriptions for pushed biometric data and alert events.
  humanURL: https://www.vivalink.com/vitals-data-services
  baseURL: https://api.vivalink.com
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/vivalink-webhooks-api-openapi.yml
  - type: Documentation
    url: https://www.vivalink.com/vivalink-sdk
  - type: Documentation
    url: https://www.vivalink.com/vitals-data-services
  - type: PostmanCollection
    url: collections/vivalink.postman_collection.json
  - type: OpenCollection
    url: collections/vivalink.opencollection.json
  - type: Documentation
    url: https://www.vivalink.com/wearable-products
  - type: Documentation
    url: https://aws.amazon.com/blogs/apn/next-gen-patient-monitoring-with-vivalinks-intelligent-biometrics-platform-and-aws/
common:
- type: CapabilityMap
  url: capabilities/vivalink-capability-edges.yml
  name: VivaLNK Business Capability Map
- type: AgenticAccess
  url: agentic-access/vivalink-agentic-access.yml
- type: DomainSecurity
  url: security/vivalink-domain-security.yml
- type: Authentication
  url: authentication/vivalink-authentication.yml
- type: GitHubOrganization
  url: https://github.com/VivaLnk
- type: LinkedIn
  url: https://www.linkedin.com/company/vivalnk-inc-
- type: Website
  url: https://www.vivalink.com
- type: Documentation
  url: https://www.vivalink.com/vivalink-sdk
- type: SignUp
  url: https://www.vivalink.com/contact
- type: Plans
  url: plans/vivalink-plans-pricing.yml
- type: RateLimits
  url: rate-limits/vivalink-rate-limits.yml
- type: FinOps
  url: finops/vivalink-finops.yml
- url: https://www.vivalink.com/blog
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

VivaLNK API — frequently asked questions

Does VivaLNK have an API?

Yes. APIs.io lists 5 APIs from VivaLNK, including VivaLNK Devices API, VivaLNK FHIR API and VivaLNK Subjects API, and 2 more.

Is there an OpenAPI specification for the VivaLNK API?

Yes. APIs.io indexes 5 OpenAPI specifications for VivaLNK, each linked for download from this page.

How do I authenticate with the VivaLNK API?

VivaLNK uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as VivaLNK Authentication.

How much does the VivaLNK API cost?

APIs.io lists 3 pricing plans for VivaLNK, with each plan's price, limits and inclusions under Pricing on this page.

Is the VivaLNK API ready for AI agents?

VivaLNK has a Kin Score of 31.7 out of 100 (thin) and an Agent Readiness score of 19.0 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/vivalink"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/vivalink/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/vivalink/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.