What's new Multimedia Ingestion API v3 change history

Learn what changed in the API.

Version

Description of change

April 2026

API Reference: Updated to v 3.0.2, in metadataUploadV3, under Body parameters, added "wrapup_time: integer (int32)".

API Guide: In General Information, Metadata document format, added contacts[].sessions[].wrapup_time.

February 2026

API Guide: In General Information, added Base Paths.

API Reference: Added separate API references for Verint Cloud and for Verint on-premises.

August 2025

API Guide: In General Information, added the channel JSON schema element.

April 2025

API Guide: In General Information, added the swap_audio_channels and original_filename JSON elements schema.

October 2024

Updated the audio WAV codecs, such as, GSM 6.10, IMBE, AMBE2, AMBE.

June 2024

API Guide: Added Prerequisites.

October 2023

API Reference: Support for redaction, morphing, and personal tags.

API Guide: Added three use cases.

Ingestion API V3

  • An optional <<api_object>> is now supported for handling cases where the agent_id is missing.

    While v2 only warns about a missing agent_id in the metadata of the POST request, v3 does not allow a missing agent_id. By default, the response is HTTP 400 Bad Request.

    It is still possible to send a metadata POST without an agent by including the <<api_object>>. To keep the existing behavior of creating sessions even if the employee cannot be resolved, the following must be added to the request body:

    Copy
    {
      "api": {
       "allow_missing_agent": true,
              }
    ...
    }

    If the session Agent ID is not missing or the PBX login ID-based lookup fails, a default Agent ID can be provided.

  • The organization is resolved by the organization of the employee mapped to the session. If no employee is mapped to the session, then the organization of the tenant is used.

Ingestion API v2

New API Reference for version 2. The initial version of Multimedia Ingestion API (Recorder Ingestion v1) was not widely used. The initial version had limitations on speed and performance and the maximum file size.

The Recorder Ingestion v1 API is officially deprecated as of 15.2 HFR5.

Prerequisites for Multimedia Ingestion API

General information

API object in Metadata (v3)