canonical: https://jentic.com/apis/tenovi.com/tenovi

# Tenovi Hardware Integration (HWI) API

The Tenovi Hardware Integration (HWI) API allows third-party clients to interact with remote patient monitoring (RPM) devices, gateways, fulfillment workflows, supplies, and more. Clients can receive measurement data from Tenovi devices via webhooks, activate/deactivate devices, manage patients, and handle fulfillment workflows. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically activate (request) an hwi device, list hwi devices. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for iot and hardware only.

## Capabilities

- Activate (request) an HWI device
- List HWI devices
- Get a specific HWI device
- Delete/deactivate an HWI device
- Create a patient record

## Use cases

### IoT and Hardware Operations

Use the Tenovi Hardware Integration (HWI) API to perform iot operations programmatically. The API provides 9 endpoints covering core functionality including activate (request) an hwi device, list hwi devices, get a specific hwi device.

Example prompt: Call POST `/hwi/hwi-devices` to activate (request) an hwi device

### Automated Devices Management

Automate devices operations by combining multiple Tenovi Hardware Integration (HWI) API endpoints. Agents can list hwi devices and then get a specific hwi device in a single workflow.

Example prompt: Call GET `/hwi/hwi-devices` to list hwi devices, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tenovi Hardware Integration (HWI) API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'activate (request) an hwi device', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/hwi/hwi-devices` | Activate (request) an HWI device |
| GET | `/hwi/hwi-devices` | List HWI devices |
| GET | `/hwi/hwi-devices/{id}` | Get a specific HWI device |
| DELETE | `/hwi/hwi-devices/{id}` | Delete/deactivate an HWI device |
| POST | `/hwi/patients` | Create a patient record |
| GET | `/hwi/patients` | List patient records |
| GET | `/hwi/hwi-device-types` | List available device types |
| POST | `/hwi/webhooks` | Create a webhook |

## Key resources

- **Devices** — Operations related to Devices
- **Patients** — Operations related to Patients
- **Webhooks** — Operations related to Webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 88 / 100
- **View full report:** https://jentic.com/apis/tenovi.com/tenovi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Tenovi Hardware Integration API by hand means learning its X-API-Key header auth against the api2.tenovi.com host and handling device, patient, and webhook calls yourself. Through Jentic you install once, import the Tenovi Hardware Integration (HWI) API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the device id in the URL path (`/hwi/hwi-devices/{id}`), so a rule can pin your agent to one device: it can read that device and nothing else. You choose the operations it may call, so deleting a device is not included unless you add it.
- **Credential handling:** Your Tenovi API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a hardware device' or 'list patients', and Jentic returns the matching Tenovi Hardware Integration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Particle** — Alternative iot API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Tenovi Hardware Integration (HWI) API use?

The Tenovi Hardware Integration (HWI) API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I activate (request) an hwi device with the Tenovi Hardware Integration (HWI) API?

Yes. Use the POST `/hwi/hwi-devices` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tenovi Hardware Integration (HWI) API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I activate (request) an hwi device through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'activate (request) an hwi device'. Jentic returns the matching Tenovi Hardware Integration (HWI) API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tenovi Hardware Integration (HWI) API have?

The Tenovi Hardware Integration (HWI) API exposes 9 endpoints covering devices, patients, webhooks operations.

### Can I limit what my agent is allowed to do with the Tenovi Hardware Integration (HWI) API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The device id sits in the URL path (`/hwi/hwi-devices/{id}`), so you can pin the agent to a single device and let it only read that one, for example allowing GET `/hwi/hwi-devices/{id}` while excluding everything else. You choose the operations it may call, so destructive calls like DELETE `/hwi/hwi-devices/{id}` or creating patient records are off limits unless you add them.