Changelog
Signup for API Updates
This changelog lists all updates, additions, and changes to the Tenovi APIs. To receive email notifications whenever new updates are published, complete the form and we'll keep you in the loop.
Subscribe for UpdatesPatients Object
You can now create patient records in Tenovi via API. This enables you to attach patient information to devices, fulfillment requests, and measurements with more ease. See the Patients API reference for full details.
Bulk Orders API & Special Order Webhooks
Two new additions for managing bulk and special orders:
- Get Bulk Orders endpoint — retrieve shipping info, fulfillment status, and complete device manifests in a single request.
- Special/Bulk Order Webhook — receive real-time updates on supply, bulk, replacement, return label, and demo unit orders.
See the Bulk Orders docs and Special Order Webhooks docs for details.
Device Replacement API Endpoint
A new endpoint simplifies the device replacement process, providing a dedicated API pathway for requesting replacement physical devices — including Gateways — without creating a new HWI Device object or triggering a duplicate order flag.
Workflow: Create a replacement order via the endpoint specifying device, Gateway, or both → Tenovi dropships to the provided address → the original HWI Device record is maintained → if a replacement Gateway was requested, hardware_uuid is automatically updated on all corresponding devices and a Fulfillment Webhook is sent. Track all replacement orders via the Special Orders dashboard in the Tenovi WebApp.
Note: warranty replacements must still be requested through the Tenovi Web App via a support ticket. See the Replacing Devices docs.
Legacy Delivery Types Deprecated
The legacy “Priority” and “Shipping” order delivery types have been deprecated. All orders requiring proof-of-delivery must now use the require_signature flag in the Fulfillment Request object. Clients can still submit orders using the legacy names, but they will be shipped with default options (no proof-of-delivery) if the flag is not set.
New Fulfillment Webhook Events
Fulfillment Webhooks now fire for three additional events to keep you better informed on dropshipment request status:
- Client Action Required — the request needs attention (e.g. invalid address or duplicate submission).
- On Hold — the request is temporarily on hold at Tenovi (e.g. device out of stock).
- Ready to Ship — the request has passed internal validation and is queued for fulfillment.
See the Fulfillment Webhooks docs for full event details.
Device Compatibility Validation for Supply Orders
When requesting a new supply order via the request_supplies endpoint, you may now include an optional related_client_device_id field (for HWI clients, this is the HWI Device ID). When included, Tenovi will validate that the requested supply is compatible with the corresponding device before processing the order.
Glucometer Strip Tracking for Cellular Glucometers
Clients on ASR plans can now track glucometer strip quantities and request replacement strips specifically for Tenovi Cellular Glucometers. Use the device IMEI (rather than Gateway ID) when retrieving or updating glucometer supply information or creating a new supply request. Gateway-connected glucometers can continue to use the corresponding Gateway ID.
Ship Gateway Only Flag
A new ship_gateway_only flag has been added to the Fulfillment Request object on the hwi-devices endpoint. Use this flag when a patient already owns a Tenovi Gateway-compatible device but still needs a Gateway dropshipped. Only the Gateway cost is billed for these requests.
Webhook enabled_by_default Flag
Measurement Webhooks now support an enabled_by_default flag. When set to false, the webhook is added to your account without automatically receiving measurement data from all devices. Use the measurement_webhook_id Device Property to selectively enable the webhook for specific devices — useful for testing a new webhook with a small subset of devices before rolling it out broadly. The flag defaults to true.
API Access Restricted to Trusted Hosts
Browser-based calls to the Tenovi API are now restricted to trusted hosts only.
Prior hardware_uuid in Fulfillment Webhooks
“Replaced” and “Unlinked” Fulfillment Webhooks now include the hardware_uuid for the prior device (e.g. the Gateway being replaced or unlinked) in the previously deprecated device_id field. The hardware_uuid field continues to carry the current hardware UUID (i.e. the replacement Gateway, or null if unlinked).
Per-Device Measurement Webhook Routing
HWI clients can now route measurement data from a specific device to a single, user-selected Measurement Webhook instead of broadcasting to all webhooks. Set the measurement_webhook_id Device Property to the desired webhook ID to enable this, or set it to an empty string to revert to the default behavior.
You can also query all devices associated with a specific webhook using the properties__key and properties__value query parameters on the hwi-devices endpoint.
Gateway List & Info Endpoint Updates
Two updates to Gateway endpoints for HWI clients:
- New
hwi-gatewaysendpoint — returns a paginated list of all Gateways associated with your account, including useful dates for sorting and filtering. - Updated
hwi-gateway-infoendpoint — now includes explicit fields indicating when a Gateway was assigned to your account, when it was dropshipped (if applicable), and which devices (if any) are whitelisted to it.
Optional patient.external_id & Email Support
When activating a new HWI Device with patient information, the patient.external_id field is now optional. You may also include a patient email address — it is not validated and is for reference purposes only, though Tenovi Tech Support may use it when resolving service requests.
ASR Supply Types Endpoint
A new asr-supply-types endpoint is available for ASR clients, returning a list of valid supply names that can be used when ordering supplies via API. See the ASR API reference for details.
Glucometer Supplies Endpoint & Supply Request Refactor
New: A Glucometer Supplies endpoint is now available for ASR clients to query the estimated number of glucometer strips remaining for a patient (based on strips shipped minus measurements taken), or to update this estimate manually. See the ASR API reference for details.
Improvement: The “Request Supply” endpoint has been refactored to sit alongside all other ASR-specific endpoints. The original endpoint (CLIENT_DOMAIN/devices/supply-requests/) remains available temporarily for backwards compatibility, but clients should migrate to the new path (CLIENT_DOMAIN/asr/supply-requests/).
Array Webhooks, Signature Requests & API Improvements
New features:
- Array-based Webhook POST — Measurement Webhooks can now be configured to POST related measurements (e.g. blood pressure and pulse from a single BPM reading) as a single JSON array instead of individual requests.
- Simplified Signature Confirmation — Request delivery signature confirmation via a boolean field in the Fulfillment Request object instead of a separate device name (additional charges may apply).
Improvements:
- All timestamps in Webhook data are now standardized to
YYYY-MM-DDTHH:MM:SS.ssssssZformat — please verify your Webhook integrations handle this correctly. - The
hwi-devicesendpoint no longer requires a matchingsensor_code; only thedevice.namefield is required. - A
webhook_responsesfield has been added to the Measurements object, recording HTTP response codes for all webhooks that fired for a given measurement (comma-separated). - HWI Webhooks are now enabled for all measurements, including those from RPM software-based accounts.
- The
hwi-device-typesendpoint now includesimage,up_front_cost, andshipping_costfields to support custom shop integrations.
©2026 Tenovi