BodyTrace · Rate Limits

Bodytrace Rate Limits

BodyTrace does not publish fixed numeric API rate limits. In practice the data volume is naturally bounded by the devices themselves: a cellular RPM device transmits only a handful of measurements per day (a patient weighs in or takes a blood-pressure reading a few times daily), plus periodic heartbeat messages. Consumers reading via the data values pull endpoint should poll on a modest interval rather than tight-loop, since new data only appears when a device transmits. The push (webhook) delivery model avoids polling entirely - BodyTrace POSTs each measurement to your endpoint as it arrives. Numeric per-account or per-endpoint request caps are not documented and should be confirmed with BodyTrace.

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

It captures 3 rate-limit definitions, measuring requests and messages.

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

Tagged areas include Remote Patient Monitoring, RPM, Cellular, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Remote Patient MonitoringRPMCellularRate LimitingQuotas

Limits

Data Values Pull Requests account
requests
not published
No fixed numeric request-rate limit is documented; poll on a modest interval since data is low-frequency.
Device Transmission Frequency device
messages
a few readings + heartbeats per day
Bounded by patient behavior and device firmware, not by an API quota.
Push Delivery endpoint
messages
event-driven
BodyTrace POSTs one measurement to your endpoint per transmission; you control throughput on your side.

Policies

Prefer Push Over Poll
Use the customer-hosted webhook to receive measurements as they arrive rather than polling the data values endpoint.
Backoff Strategy
When polling, implement a modest interval and exponential backoff with jitter; honor Retry-After on any 429 response.
Idempotent Ingestion
De-duplicate on deviceId + ts, since a device may re-transmit and pushed deliveries can be retried.

Sources