Doubao
Doubao text, code, and character conversation model overview
Doubao text models use the OpenAI-compatible Chat Completions endpoint. This page groups common models and parameters for chat, code generation, and character conversation.
Endpoint Path
| Method | Path | Purpose |
|---|---|---|
| POST | /v1/chat/completions | Create a Doubao text, code, or character conversation request |
curl -X POST "https://api.routescope.ai/v1/chat/completions" \ -H "Content-Type: application/json" \ -d '{ "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "Hello, please introduce yourself in one sentence." } ] }'{
"id": "task_01JZ8M9Q4R7V2K8N9P0Q",
"object": "string",
"created": 1,
"model": "gpt-4o-mini",
"choices": [],
"usage": {
"prompt_tokens": 1,
"completion_tokens": 1,
"total_tokens": 1,
"input_tokens": 1,
"output_tokens": 1
}
}{
"error": null,
"message": "success"
}Authorization
BearerAuth
Model relay interface recognition. Request heading: Autoration: Bearer .
In: header
Request Body
application/json
The model name to call.
Can not open message Can not open message Scope: At least 1 message.
Sampling temperatures spread more and more. Sample temperature. Range: 0 to 2; the larger the value, the more random.
0 <= value <= 2Nuclear sampling parameters. Nuclear sampling parameters. Range: 0 to 1; usually no large adjustments with temperature.
0 <= value <= 1Maximum output number of Tokens. Maximum output number of Tokens. Scope: 1 to the maximum of the context of the model.
1 <= valueWhether to enable SSE flow output. Whether or not to enable flow output. Scope: True or false.
Stream extension options. Upstream support varied.
Whether or not to start deep thinking mode. Qwen/Ariyuncrery OpenAI compatible extension parameters: _FD_PROTECT_0 _ Start thinking, _FD_PROTECT_1 _ Close thinking; part of the thinking model is always open and does not support closure. Python OpenAI SDK can be imported through FD_PROTECT_2.
Tool definitions for which models can be called. . Scope: The length of arrays and the complexity of schema are based on upstream limits.
Tools call policies, such as _FD_PROTEC_0, FD_PROTEC_1 or visible specifying functions. Tool call policy. Scope: auto, none, required or visible tool objects.
Structured output constraints, such as JSON Schema.
End-user identification for audit and control.
Response Body
application/json
application/json
Model Selection
| Model ID | Capability | Typical Use |
|---|---|---|
doubao-seed-1-8-251228 | Chat completions | General text conversation |
doubao-seed-2-0-lite-260215 | Chat completions | Lightweight text conversation |
doubao-seed-2-0-mini-260215 | Chat completions | Lightweight text conversation |
doubao-seed-2-0-pro-260215 | Chat completions | More complex text conversation |
doubao-seed-2-0-code-preview-260215 | Code generation | Code-related tasks |
doubao-seed-code-preview-251028 | Code generation | Code-related tasks |
doubao-seed-character-251128 | Character dialogue | Role-play or persona conversation |
Common Parameters
| Field | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Doubao model ID. |
messages | array | Yes | OpenAI-style conversation message list. |
temperature | number | No | Sampling temperature. Range follows the endpoint description or backend configuration. |
top_p | number | No | Nucleus sampling parameter. |
max_tokens | integer | No | Maximum output tokens. |
stream | boolean | No | Whether to stream output. |
tools | array | No | Tool definitions. |
response_format | object | No | Structured output constraint. |
user | string | No | End-user identifier. |
Model-Specific Notes
| Field | Applicable Models | Description |
|---|---|---|
model | All Doubao text models | Use model to choose the concrete model in the request body. |
Code prompts | doubao-seed-2-0-code-preview-260215, doubao-seed-code-preview-251028 | These are code-generation models, but the endpoint and parameters remain Chat Completions-compatible. |
Character prompts | doubao-seed-character-251128 | This model is intended for character conversation, but the endpoint and parameters remain Chat Completions-compatible. |
Other dedicated fields | All | No unified model-specific fields are listed here. Follow API responses or the actual console display. |
Example Code
curl https://api.routescope.ai/v1/chat/completions \
-H "Authorization: Bearer $ROUTESCOPE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "doubao-seed-2-0-pro-260215",
"messages": [
{ "role": "user", "content": "Give me a one-sentence introduction to an API gateway." }
]
}'Response Structure
Doubao text pages use OpenAI Chat Completions-style responses, including fields such as choices and usage.
How is this guide?
Last updated on