Skip to main content

Authenticity Verification: start task

POST 

/api/technology/experimental/authenticity-verification

Experimental feature

Please note that Authenticity Verification is an experimental feature.
It is under development and may change in the future.

Start an Authenticity Verification task for a media file.

Authenticity Verification features

The Authenticity Verification endpoint supports the following independent operations:

  • Deepfake Detection
  • Audio Manipulation Detection
  • Replay Attack Detection

Be default, all operations are performed, and they are billed together as one Authenticity Verification task. It is possible to specify the list of requested operations (deepfake_detection, audio_manipulation_detection, replay_attack_detection) to save computational resources.

Features of all the operations

  • Multi-channel media files are supported.
  • For each channel an independent operation's result is produced.
  • Processing can be limited to a specific time segment in the media file with query parameters.

Deepfake Detection specific features

  • If there is less than 3 seconds of audio in a processed channel (or time segment), the score will be empty (i.e. null).

Audio Manipulation Detection specific features

  • Under the hood, the technology analyzes overlapping segments of 400 ms. By default, additional logic is applied to the raw segments, joining adjacent suspicious segments into one to improve the usability of the results. To obtain the raw segmentation instead, use the raw_segmentation=True query parameter.

Request

Query Parameters

    channel_mode Channel Mode

    Possible values: [split, mix]

    A string enumeration value representing the channel mode for conversion. This value indicates how the audio channels should be processed during conversion. Only the channels with the specified indices (channels parameter) will be processed, and others will be ignored.

    Default value: split
    channels Channels

    A string of integers separated by comma (without spaces), representing the channels that should be kept during conversion. If specified, only the channels with the specified indices will be processed, and others will be ignored. If empty, all channels in the audio data will be processed. Note that channels is 0-based.

    Default value:
    range_from Range From

    Possible values: >= 0

    Specifies the time in the input file where processing starts. If the parameter equals 0 (the default value), the recording is processed from the beginning. Time is given in seconds.

    Default value: 0
    range_to Range To

    Possible values: >= 0

    Specifies the time in the file where processing ends. If the parameter is not specified, the input file is processed to the end. Time is given in seconds.

    requested_operations string[]

    Possible values: [deepfake_detection, replay_attack_detection, audio_manipulation_detection]

    Requested operations to perform.

Header Parameters

    x-correlation-id X-Correlation-Id

    Correlation ID is a special type of request ID which is unique over a series of requests and responses, identifying a transaction in a distributed system. Correlation ID will be generated if not provided.

    Default value:
    x-request-id X-Request-Id

    In distributed system architecture (microservices architecture) it is a unique ID of request and response combination throughout all components of a distributed system. Request ID will be generated if not provided.

    Default value:

Bodyrequired

    filebinaryrequired

    Input media file.

    config object

    Configuration for Authenticity Verification.

    audio_manipulation_detection object

    Configuration for Audio Manipulation Detection operation.

    raw_segmentationRaw Segmentation (boolean)

    If set to True, the result of the operation will be raw segments. Otherwise, by default, additional logic is applied to the segmentation to produce a more user-friendly result.

    Default value: false

Responses

Authenticity Verification task was accepted. Follow the Location header to poll for the task state.

Response Headers
    X-Location

    ⚠️ Deprecated - use Location header instead.

    Example: /api/technology/authenticity-verification/123e4567-e89b-12d3-a456-426614174000
    Location

    A URL the client should poll for task state and result.

    Example: /api/technology/authenticity-verification/123e4567-e89b-12d3-a456-426614174000
Schema
    task objectrequired
    task_iduuidrequired
    stateTaskInfoState (string)required

    Possible values: [pending, running, rejected, failed, done]