Dashscope API (Qwen models)
https://dashscope.console.aliyun.com/
This platform now goes by QwenCloud outside mainland China and Qianwen AI Platform in mainland China. See the QwenCloud and Qianwen AI Platform page for the qwencloud/ and qwen_ai_platform/ prefixes. The dashscope/ prefix remains fully supported as an alias
We support ALL Qwen models (from Alibaba Cloud), just set dashscope/ as a prefix when sending completion requests
API Key
# env variable
os.environ['DASHSCOPE_API_KEY']
API Base
You can optionally specify the API base URL depending on your region:
| Region | API Base |
|---|---|
| International | https://dashscope-intl.aliyuncs.com/compatible-mode/v1 |
| China/Beijing | https://dashscope.aliyuncs.com/compatible-mode/v1 |
# Set via environment variable
os.environ['DASHSCOPE_API_BASE'] = "https://dashscope-intl.aliyuncs.com/compatible-mode/v1"
# Or pass directly in the completion call
response = completion(
model="dashscope/qwen-turbo",
messages=[{"role": "user", "content": "hello"}],
api_base="https://dashscope-intl.aliyuncs.com/compatible-mode/v1"
)
Sample Usage
from litellm import completion
import os
os.environ['DASHSCOPE_API_KEY'] = ""
response = completion(
model="dashscope/qwen-turbo",
messages=[
{"role": "user", "content": "hello from litellm"}
],
)
print(response)
Sample Usage - Streaming
from litellm import completion
import os
os.environ['DASHSCOPE_API_KEY'] = ""
response = completion(
model="dashscope/qwen-turbo",
messages=[
{"role": "user", "content": "hello from litellm"}
],
stream=True
)
for chunk in response:
print(chunk)
All supported Models
| Model Name | Function Call |
|---|---|
| qwen-turbo | completion(model="dashscope/qwen-turbo", messages) |
| qwen-plus | completion(model="dashscope/qwen-plus", messages) |
| qwen-max | completion(model="dashscope/qwen-max", messages) |
| qwen-turbo-latest | completion(model="dashscope/qwen-turbo-latest", messages) |
| qwen-plus-latest | completion(model="dashscope/qwen-plus-latest", messages) |
| qwen-max-latest | completion(model="dashscope/qwen-max-latest", messages) |
| qwen-vl-plus | completion(model="dashscope/qwen-vl-plus", messages) |
| qwen-vl-max | completion(model="dashscope/qwen-vl-max", messages) |
| qwq-32b | completion(model="dashscope/qwq-32b", messages) |
| qwq-32b-preview | completion(model="dashscope/qwq-32b-preview", messages) |
| qwen3-235b-a22b | completion(model="dashscope/qwen3-235b-a22b", messages) |
| qwen3-32b | completion(model="dashscope/qwen3-32b", messages) |
| qwen3-30b-a3b | completion(model="dashscope/qwen3-30b-a3b", messages) |
Latest model aliases
Since v1.109.0dashscope/<family>-latest names follow a model family as LiteLLM moves them to newer models, so your application keeps one model string. Use them like any other DashScope model name. LiteLLM sends DashScope the current target model and bills at that model's price. See Latest model aliases for how aliases work and the full list across providers.
| Alias | Model family |
|---|---|
dashscope/qwen-max-latest | Qwen Max |
dashscope/qwen-flash-latest | Qwen Flash |