Skip to main content

Gender Identification from file: start task

POST 

/api/technology/gender-identification

Start Gender Identification task for a media file.

Gender Identification from file features

  • Multi-channel audio files are supported.
  • For each channel a separate Gender Identification result is produced.
  • Processing can be limited to a specific time segment in the media file with query parameters.
  • Processing can be limited to a maximum amount of speech with a 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.

    max_speech_length Max Speech Length

    Possible values: > 0

    Specifies the maximum duration of speech (in seconds) from which the gender is identified after the technology filters out non-speech segments. This parameter depends on the range_from and range_to parameters.

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.

Responses

Gender Identification from file 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/gender-identification/123e4567-e89b-12d3-a456-426614174000
    Location

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

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

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

var client = new HttpClient();
var request = new HttpRequestMessage(HttpMethod.Post, "https://docs.cloud.phonexia.com/api/technology/gender-identification");
request.Headers.Add("Accept", "application/json");
var content = new StringContent(string.Empty);
content.Headers.ContentType = new MediaTypeHeaderValue("multipart/form-data");
request.Content = content;
var response = await client.SendAsync(request);
response.EnsureSuccessStatusCode();
Console.WriteLine(await response.Content.ReadAsStringAsync());