Request Payload

This sub-page helps the integrator to understand various different types of request payload based on the individual task or combination of tasks in that sequence that integrator wants to do.

Audio language detection

{ 
  "pipelineTasks": [ 
      { 
        "taskType": "audio-lang-detection",
        "config": {
                  "serviceId": "{{ald_service_id}}"
                  } 
      }
],
"inputData": {
    "audio": [
        {
            "audioContent": "INSERT_BASE64_AUDIO_HERE"
          //"audioUri": "INSERT_AUDIO_URL_HERE"
        }
    ]
}
}

This request contains 2 major parameters listed below and detailed further down the section:

1. pipelineTasks

2. inputData

Parameter: pipelineTasks

Type: Array This parameter takes an array of tasks, in the form of dictionary of taskType and config, that are to be done by the integrator. In the above example, pipelineTasks takes only one dictionary (line 2-9) because integrator wants to do only Audio language detection. taskType parameter takes String that takes the value audio-lang-detection

config is a single key parameter which maps to another object called serviceId

serviceId

serviceId parameter identifies the specific service/trained model you want to use.

For serviceId as "bhashini/iitmandi/audio-lang-detection/gpu", below are the supported languages-

• Assamese

• Bengali

• English

• Hindi

• Kannada

• Gujarati

• Malayalam

• Marathi

• Odia

• Punjabi

• Tamil

• Telugu

Parameter: inputData

inputData Parameter takes the actual input from the integrator on which the individual task has to be done. in this case, the input is taken via audioUri or audioContent (base64 format).

either user can pass audioUri as input or audioContent as input.