VivaLNK · Rate Limits

Vivalink Rate Limits

VivaLNK does not publish fixed numeric rate limits for its Biometrics Data Platform / cloud web-service (M2M) APIs; the licensed API reference and any quota terms are provided under the partner-gated Developer Program. The platform runs on AWS (Amazon API Gateway plus Amazon Kinesis Data Streams), so ingestion and near-real-time access throughput are governed by the provisioned capacity and account agreement rather than a published per-minute cap. Data-plane delivery to webhook subscribers is push-based and paced by the volume of measurements and alerts produced by the enrolled wearables.

Vivalink Rate Limits is the machine-readable rate-limit profile for VivaLNK on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, records, events, and jobs.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Connected Health, Remote Patient Monitoring, Wearables, Biometrics, and Rate Limiting.

5 Limits Throttle: 429
Connected HealthRemote Patient MonitoringWearablesBiometricsRate LimitingQuotas

Limits

Cloud API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the M2M cloud APIs.
Ingestion Throughput account
records
provisioned
Sensor-to-cloud ingestion runs through Amazon API Gateway and Amazon Kinesis; throughput is governed by provisioned capacity and the account agreement.
Near-Real-Time Read account
requests
not published
Near-real-time measurement reads are served over REST; no public cap is documented.
Webhook Delivery subscription
events
event-driven
Webhook events are pushed as measurements and alerts are produced; volume depends on the number of enrolled subjects and devices.
Bulk Export account
jobs
not published
Bulk data-file export is asynchronous; concurrency limits are not documented publicly.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.
Provisioned Capacity
Platform throughput is scaled to the account's deployment (subjects, devices, data volume) rather than a fixed global limit.

Sources