BodyTrace

BodyTrace makes cellular-connected remote patient monitoring (RPM) devices - blood pressure monitors, body-weight scales, and pulse oximeters - that transmit readings directly over the cellular network with no phone, app, Wi-Fi, or Bluetooth pairing required. Each device encrypts measurements end-to-end and sends them to the BodyTrace platform, which exposes the data to healthcare organizations, EHRs, and RPM programs over a simple HTTP API using HTTP Basic authentication. Consumers can pull device readings (data values) on a polling loop or receive them pushed to a configured HTTP endpoint. BodyTrace sells to organizations, not individuals; API and device provisioning are arranged through BodyTrace sales.

BodyTrace publishes 5 APIs on the APIs.io network, including Alerts API, Data Messages API, Devices API, and 2 more. Tagged areas include Remote Patient Monitoring, RPM, Cellular, Medical Devices, and Digital Health.

BodyTrace’s developer surface includes authentication, documentation, and 7 more developer resources.

🌐 Visit website 📡 Source on GitHub

37.1/100 thin ▬ flat Agent 31/100 agent aware Full breakdown ↓
scored 2026-08-03 · rubric v0.9

AccessPaidSelf serve

5 APIs

Remote Patient MonitoringRPMCellularMedical DevicesDigital HealthBlood PressureConnected DevicesIoT

Kin Score

Kin Score How this is scored →
scored 2026-08-03 · rubric v0.9

Composite quality — 37.1/100 · thin

Contract Quality 15.9 / 25

Developer Ergonomics 3.9 / 20

Commercial Clarity 5.8 / 20

Operational Transparency 4.1 / 13

Governance 0.0 / 12

Discoverability 7.4 / 10

Agent readiness — 31/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

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

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/bodytrace: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 5

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

BodyTrace Alerts API

Modeled threshold and connectivity alerts.

BodyTrace Data Messages API

Modeled surface for raw per-transmission device messages.

BodyTrace Devices API

Modeled device listing and status keyed by IMEI.

BodyTrace Observations API

Confirmed pull surface for device readings (data values).

BodyTrace Provisioning API

Modeled device enrollment and delivery configuration.

Open Collections 1

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

BodyTrace RPM Data API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Bodytrace Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Bodytrace Rate Limits

3 limits

RATE LIMITS

FinOps 1

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

Bodytrace Finops

FINOPS

Security Posture 2

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

Bodytrace Authentication

http · 1 scheme

SECURITY

Bodytrace Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Bodytrace Agentic Access

6 operations · 1 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

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 2

The organization behind the API

LinkedIn

Website

Website

Source (apis.yml)

aid: bodytrace
url: https://raw.githubusercontent.com/api-evangelist/bodytrace/refs/heads/main/apis.yml
name: BodyTrace
kind: company
description: BodyTrace makes cellular-connected remote patient monitoring (RPM) devices - blood pressure monitors, body-weight
  scales, and pulse oximeters - that transmit readings directly over the cellular network with no phone, app, Wi-Fi, or Bluetooth
  pairing required. Each device encrypts measurements end-to-end and sends them to the BodyTrace platform, which exposes the
  data to healthcare organizations, EHRs, and RPM programs over a simple HTTP API using HTTP Basic authentication. Consumers
  can pull device readings (data values) on a polling loop or receive them pushed to a configured HTTP endpoint. BodyTrace
  sells to organizations, not individuals; API and device provisioning are arranged through BodyTrace sales.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/bodytrace.png
tags:
- Remote Patient Monitoring
- RPM
- Cellular
- Medical Devices
- Digital Health
- Blood Pressure
- Connected Devices
- IoT
created: '2026-07-05'
modified: '2026-07-05'
specificationVersion: '0.19'
apis:
- aid: bodytrace:bodytrace-alerts-api
  name: BodyTrace Alerts API
  description: Modeled threshold and connectivity alerts.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Alerts
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-alerts-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-data-messages-api
  name: BodyTrace Data Messages API
  description: Modeled surface for raw per-transmission device messages.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Data Messages
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-data-messages-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-devices-api
  name: BodyTrace Devices API
  description: Modeled device listing and status keyed by IMEI.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-devices-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-observations-api
  name: BodyTrace Observations API
  description: Confirmed pull surface for device readings (data values).
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Observations
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-observations-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-provisioning-api
  name: BodyTrace Provisioning API
  description: Modeled device enrollment and delivery configuration.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Provisioning
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-provisioning-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
common:
- type: AgenticAccess
  url: agentic-access/bodytrace-agentic-access.yml
- type: DomainSecurity
  url: security/bodytrace-domain-security.yml
- type: Authentication
  url: authentication/bodytrace-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/bodytrace
- type: Website
  url: https://www.bodytrace.com
- type: Documentation
  url: https://www.bodytrace.com/medical/
- type: Plans
  url: plans/bodytrace-plans-pricing.yml
- type: RateLimits
  url: rate-limits/bodytrace-rate-limits.yml
- type: FinOps
  url: finops/bodytrace-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Where this information came from

This is an independent, third-party profile of BodyTrace, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put 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.