This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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, HL7 FHIR integration, and bulk data-file downloads for EHR, CTMS, and clinical-application integration.
Partner-gated / modeled entry. VivaLNK's developer surface is delivered through its SDK and Developer Program and is provided under license rather than published openly. There is no public base URL, OpenAPI document, or endpoint reference. The APIs, OpenAPI, and collections in this repository are modeled from VivaLNK's documented platform capabilities (M2M cloud web services, webhook support, FHIR support, bulk export) and are labeled as such; the base URL
https://api.vivalink.comis a placeholder to confirm under the Developer Program.
APIs.json: https://raw.githubusercontent.com/api-evangelist/vivalink/refs/heads/main/apis.yml
- 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
Enroll and manage the subjects (patients / study participants) whose biometric data is captured by VivaLNK wearables - create, list, retrieve, update, and deactivate subjects, and associate them with a project, study, or care program. Endpoints are modeled from VivaLNK's documented M2M cloud web-service platform.
- Human URL: https://www.vivalink.com/vitals-data-services
- Base URL (modeled):
https://api.vivalink.com
- Subjects
- Patients
- Enrollment
- Documentation
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Register and manage VivaLNK wearable biosensors - the Multi-Vital ECG patch, temperature patch, SpO2 sensor, and BP cuff - list devices, retrieve a device's status and firmware, and assign or unassign a device to a subject. Endpoints are modeled from VivaLNK's documented device-management capabilities.
- Human URL: https://www.vivalink.com/wearable-products
- Base URL (modeled):
https://api.vivalink.com
- Devices
- Sensors
- Wearables
- Documentation
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Retrieve continuous and summary biometric measurements collected from subjects' wearables - ECG waveform, heart rate, heart rate variability, RR interval, respiratory rate, body/axillary temperature, SpO2, blood pressure, and accelerometer/activity data - as time-ranged time series or aggregated summaries, plus bulk data-file exports for retrospective analysis. Near-real-time access is served over REST (backed by Amazon Kinesis) rather than a public streaming socket. Endpoints are modeled from VivaLNK's documented cloud data services.
- Human URL: https://www.vivalink.com/vitals-data-services
- Base URL (modeled):
https://api.vivalink.com
- Vital Signs
- ECG
- Heart Rate
- Temperature
- SpO2
- Documentation
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Register webhook subscriptions so VivaLNK's platform pushes biometric data and alert events (for example threshold or arrhythmia notifications) to your HTTPS endpoint as they are produced - create, list, retrieve, update, and delete subscriptions. Webhook push is a documented VivaLNK Biometrics Data Platform capability; the endpoint shapes here are modeled.
- Human URL: https://www.vivalink.com/vitals-data-services
- Base URL (modeled):
https://api.vivalink.com
- Webhooks
- Subscriptions
- Events
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Access VivaLNK biometric data as HL7 FHIR resources (Patient, Device, Observation) for interoperability with EHR systems, CTMS, and clinical applications. FHIR support is a documented VivaLNK Biometrics Data Platform capability; the resource paths here are modeled on standard FHIR R4.
- Human URL: https://www.vivalink.com/vitals-data-services
- Base URL (modeled):
https://api.vivalink.com/fhir
- FHIR
- Interoperability
- EHR
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Does VivaLNK expose a documented public WebSocket API? No. VivaLNK's documented cloud surface is request/response REST over HTTPS (Amazon API Gateway) plus server-to-endpoint webhook push, with HL7 FHIR and bulk file export. Near-real-time delivery is handled internally by Amazon Kinesis Data Streams and read back over REST - there is no documented client-facing WebSocket (or SSE) stream. See review.yml.
FN: Kin Lane Email: kin@apievangelist.com