Changelog & Upgrades

Overview

Updates to the Invox Medical API — including new features, fields, or endpoints — are released under a new dated version to ensure stability and predictability. This means your integration won't be affected by these changes unless you explicitly opt into the newer version.

Version History

Version 2026-08-01

SOFT Integration

New integration model

  • Introduced SOFT Integration, which lets your EHR open an Invox Genesis consultation for a physician without the physician logging in, and retrieve the resulting clinical note.
  • New endpoint Generate signature (POST /api/v1/generate-soft-integration-signature) to authorize a single consultation for a single physician.
  • New endpoint Get consultation result (GET /api/v1/soft-integration/{requestId}/result) to retrieve the clinical note once the consultation has finished.
  • New endpoint Cancel consultation (DELETE /api/v1/soft-integration/{requestId}) to release a physician whose session was abandoned.
  • SOFT Integration consultations are notified through the existing OnMedicalReportFinished webhook event, marked with origin: "SOFT_INTEGRATION" and carrying the optional consultationMetadata. There is also a WebSocket channel for the browser.
  • Requires an API Key holding the new GENESIS-SOFT-INTEGRATION permission.
SOFT Integration is only available from 2026-08-01 onwards. Its endpoints reject earlier versions with 400 and invalidApiVersionForEndpoint, since they did not exist in 2026-03-01 or before. Existing integrations are unaffected: this release adds endpoints and never changes the behaviour of the previous ones.
requestId values are single-use. Once accepted, a requestId can never be reused, not even after the consultation is cancelled. Generate a fresh value on every attempt.

AI Services Updates

Generate Clinical Note Enhancements

  • Added a new generationMetadata field to the Generate Clinical Note response. It provides detailed information about the generation outcome, including whether the result was partial, the number of failed fields, per-field status, and a recommendation for the client.
  • Supports partial responses: when one or more fields fail to generate, the response now returns the successfully generated fields along with failedFields (each with a reasonCode and retryable flag) and a recommendation (e.g. RETRY_RECOMMENDED).
This is a backward-compatible change. All previous features from version 2026-03-01 are included and maintained; the only difference is the addition of the generationMetadata field in the Generate Clinical Note response.

Version 2026-03-01

New Features

Updates

  • All previous features from version 2025-11-01 are included and maintained.
  • Addeed new endpoints for generating pre-signed URLs for document uploads and deleting uploaded documents in the context of clinical note generation.
  • Added Consultation Summary Generation endpoint to generate summaries based on audio transcriptions.
  • Added IM Tools endpoints
  • Added support for generating clinical note in Euskera, Galician and Valencian.

Webhooks

  • Added Webhooks documentation section with full reference for all available webhook events, including credentials, signature verification algorithm, and implementation examples in TypeScript, C#, Java, and Python.
  • Supported events: OnTranscriptionFinished, OnMedicalReportFinished, OnInvoxAuraTranscriptionFinished, OnInvoxAuraClinicalNoteCreated, OnInvoxAuraClinicalNoteFinished, OnInvoxAuraAudioCreated, and OnAlertTriggered.

Version 2025-11-01

AI Services Updates

Streaming Transcription Enhancements

  • Updated input data contract: we introduce the session concept
  • Removed callbackUrl field as mandatory when opening the web socket
  • Added a new kind of message type: END_TRANSCRIPTION
  • Clarified the usage of isTranscriptionCompleted field

For more details, check the Streaming Transcription Guide and the Get Transcription endpoint.

New Translation Endpoints

  • Added endpoint for translating transcriptions: We have added a new endpoint that allows translating transcriptions generated by our AI services. Check the Translate Transcription endpoint for more details.
  • Added endpoint for translating clinical notes: We have added a new endpoint that allows translating clinical notes generated by our AI services. Check the Translate Clinical Note endpoint for more details.

Changed Generate Report Endpoint

  • New endpoint for generating medical reports: We have renamed the existing generate-report endpoint to generate-clinical-note to better reflect its purpose. Check the Generate Clinical Note endpoint for more details.

Management API Updates

  • Select account after successful authentication: After successfully authenticating, users can now select the desired account to work with, enhancing flexibility for multi-account users. For more details, refer to the Select account.
  • Search events: allow us get events or actions performed by users in the platform. Check the Search Events endpoint for more details.
  • Login endpoint: Output contracts have been updated: added accounts field to list all accounts associated with the authenticated user, added userId field to identify the user, added fullName field to provide the user's full name.

Version 2025-10-01

Initial Release

  • First version of the API
  • Core AI Services functionality
  • Management API endpoints
  • Authentication system

Upgrade Guide

Migrating to Version 2025-11-01

If you're currently using streaming transcription services, please review the following breaking changes:

Streaming Transcription Updates

  1. Session Concept: Update your integration to handle the new session-based workflow
  2. CallbackUrl Changes: The callbackUrl field is no longer mandatory when opening WebSocket connections
  3. New Message Types: Handle the new END_TRANSCRIPTION message type in your WebSocket message handlers
  4. isTranscriptionCompleted Field: Update your logic to check for the isTranscriptionCompleted field to determine when transcription is complete and retrieve the transcription using the Get Transcription endpoint.
  • Review your WebSocket implementation
  • Update message type handlers
  • Test with the new session workflow
  • Update error handling for the new message structure

Targeting a specific version

Default API Version

If we don't specify a version when making API requests, the system will automatically use the latest stable version available. This ensures that we always benefit from the most recent features and improvements without needing to adjust our integration.

Specifying a Version

To set the API version on a specific request, you can add a specific header named X-Invox-Medical-Api-Version with the value of the version you are targeting:

X-Invox-Medical-Api-Version: 2025-11-01

This approach allows us to maintain compatibility with a specific version of the API while still having the flexibility to upgrade when we're ready.

Table of Contents