Alibaba Cloud Model Studio:Non-real-time speech recognition (Qwen-Audio-3.0-ASR-Flash/Fun-ASR-Flash) Android SDK

Yes

Service endpoints:

• wss://dashscope.aliyuncs.com/api/v1/services/aigc/multimodal-generation/generation
• China (Beijing): wss://{WorkspaceId}.cn-beijing.maas.aliyuncs.com/api/v1/services/aigc/multimodal-generation/generation
• Singapore: wss://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/api/v1/services/aigc/multimodal-generation/generation

Yes

API Key.

Yes

The operating mode. For non-real-time speech recognition, set this parameter to "1".

Yes

A unique string that identifies the end user. You can use an in-app user ID or a client-generated unique device identifier. This ID is mainly used for log tracing and troubleshooting.

No

The path for log files. This parameter takes effect only when you call initialize with save_log set to true. In this case, you must specify the log file path. Otherwise, an error occurs. Up to two log files are retained locally.

No

The maximum log file size in bytes. This parameter takes effect only when you call initialize with save_log set to true. Default: 104857600 (100 * 1024 * 1024 bytes, or 100 MiB).

No

The filtering level for logs sent through the logging callback (onFileTransLogTrackCallback). Default: 2. Valid values: - 0: LOG_LEVEL_VERBOSE - 1: LOG_LEVEL_DEBUG - 2: LOG_LEVEL_INFO - 3: LOG_LEVEL_WARNING - 4: LOG_LEVEL_ERROR - 5: LOG_LEVEL_NONE (disables this feature). Note: log_track_level and level (configured through initialize method) jointly determine which logs are delivered. The numeric level of a log must be greater than or equal to both log_track_level and level for the log to be delivered. For example, if log_track_level is set to 2 (INFO) and level is set to 3 (WARNING), only WARNING and higher-severity logs (numeric level >= 3) are delivered.

No

If Connection and control parameters apikey uses temporary API key, you can update it here to prevent expiration.

Yes

The core speech recognition configuration object, including the model and parameters that control recognition.

Yes

The model name. Qwen-Audio-3.0-ASR-Flash and Fun-ASR-Flash models are supported. For details, see Supported models and regions.

Yes

The audio format. Set this parameter to the actual format. Supported formats include wav, mp3, opus. For details, see Audio specifications.

No

The audio sample rate in Hz. For example, 16000 indicates a sample rate of 16 kHz. For details, see Audio specifications.

No

The precompiled vocabulary ID. Create a vocabulary in advance and pass its ID during recognition to use its hotwords. Use this option when the vocabulary is known, relatively stable, and reused across requests. For usage instructions, see Precompiled hotwords.

No

Instant hotwords.
Pass key-value pairs. The key is the hotword text (string) and the value is its weight (integer). You do not need to create a vocabulary in advance. Valid weights are [1, 5] or 50. Within [1, 5], a higher weight makes the model more likely to output the word. A weight of 50 specifies a super hotword and significantly increases recall. You can specify up to 50 super hotwords.
Use this option for temporary, session-level hotword optimization.
When both instant and precompiled hotwords are configured, the system merges them. If the merged list exceeds 2000 entries, it randomly selects 2000 entries. For usage instructions, see Instant hotwords.

{
  "张三": 5,
  "李四": 5
}

No

The language codes for recognition. If the language is unknown in advance, omit this parameter to let the model detect it automatically.
For Qwen-Audio-3.0-ASR-Flash models, up to four values are supported. If more are specified, only the first four take effect. For Fun-ASR-Flash models, only one value is supported. If multiple values are specified, only the first takes effect.

• qwen-audio-3.0-asr-flash, fun-asr-flash-2026-06-15:
• zh: Chinese
• en: English
• ja: Japanese
• ko: Korean
• vi: Vietnamese
• th: Thai
• id: Indonesian
• ms: Malay
• tl: Filipino
• hi: Hindi
• ar: Arabic
• fr: French
• de: German
• es: Spanish
• pt: Portuguese
• ru: Russian
• it: Italian
• nl: Dutch
• sv: Swedish
• da: Danish
• fi: Finnish
• no: Norwegian
• el: Greek
• pl: Polish
• cs: Czech
• hu: Hungarian
• ro: Romanian
• bg: Bulgarian
• hr: Croatian
• sk: Slovak

messages

Yes

The list of messages. It contains the audio to recognize and optional conversation context to improve recognition.
See the following descriptions.

role

Yes

The message role. Valid values:

• user (required): A user message. When type is input_audio, it represents the audio to recognize. When type is input_text, it represents recognition results from previous turns or a domain-specific vocabulary (optional context).
• assistant (optional context): Large language model responses from previous turns.

content

Yes

The list of message content. See the following descriptions.

type

Yes

The content type. Each request requires at least one input_audio message. Valid values:

• input_audio (required): The audio input to recognize (role is user). You must also provide the input_audio object.
• input_text (optional context): Recognition results of user speech from previous turns or a domain-specific vocabulary (role is user). You must also provide the text field.
• text (optional context): Large language model responses from previous turns (role is assistant). You must also provide the text field.

input_audio

No

Required when type is input_audio.

input_audio.data

string

Yes

The audio data to recognize. For supported audio formats, file size limits, duration limits, and other input requirements, see Audio specifications. The following two input methods are supported:

• Audio file URL: Pass a publicly accessible audio file URL.
• Base64 Data URI: Pass Base64-encoded audio as a Data URI. Concatenate the data:{MIME_TYPE};base64, prefix with the Base64-encoded audio data. Supported MIME types include audio/wav, audio/mp3.

text

No

Required when type is input_text, provide recognition results of user speech from previous turns or a domain-specific vocabulary. When type is text, provide large language model responses from previous turns. Text length is counted in characters, with each character counting as one. The total length of all messages' text fields in each context turn must not exceed 400 characters. Excess characters are truncated from the end.

The implementation of the event and data callback interface.

A JSON string containing authentication, connection, and debugging parameters. See Connection and control parameters.

The level of logs printed by the SDK.

Whether to save logs locally. If set to true, use Connection and control parameters to set debug_path to specify the path, and use max_log_file_size to set the file size.

Recognition parameters in nls_config and messages parameters.
Example:

{
  "messages": [
    {
      "content": [
        {
          "input_audio": {
            "data": "{YOUR_AUDIO_URL}"
          },
          "type": "input_audio"
        }
      ],
      "role": "user"
    }
  ],
  "nls_config": {
    "format": "mp3",
    "model": "qwen-audio-3.0-asr-flash"
  }
}

Recognition parameters. Example:

{
  "apikey": "st-****",
  "messages": [
    {
      "content": [
        {
          "input_audio": {
            "data": "{YOUR_AUDIO_URL}"
          },
          "type": "input_audio"
        }
      ],
      "role": "user"
    }
  ],
  "nls_config": {
    "format": "mp3",
    "model": "qwen-audio-3.0-asr-flash"
  }
}

You can ignore this parameter and pass null.

The ID of the task to cancel, obtained from EVENT_FILE_TRANS_UPLOADED.

The callback event.

Error code, valid when an EVENT_ASR_ERROR event occurs.

The speech recognition result.

The task ID.

Reserved.

EVENT_FILE_TRANS_CONNECTED

Successfully connected to the service.

EVENT_FILE_TRANS_UPLOADED

The audio file was uploaded successfully. You can obtain the current task_id at this point.

EVENT_FILE_TRANS_RESULT

The final recognition result.

EVENT_ASR_ERROR

An error occurred during speech recognition.