RequestBeam Docs
DeepSeek Models
DeepSeek V4 Flash, V4 Pro, and V4.1 Flash model IDs and Chat Completions availability.
https://api.requestbeam.com/v1/chat-completionsDeepSeek models use the Common Chat Completions endpoint. To switch models, change only the model value; the endpoint and authentication stay the same.
POST https://api.requestbeam.com/v1/chat-completionsAvailable Models
model value | Positioning | Non-streaming | SSE streaming |
|---|---|---|---|
deepseek-v4-flash | Flash tier and a practical starting point for routine chat or batch evaluations | Yes | Yes |
deepseek-v4-pro | Pro tier for evaluations that prioritize complex reasoning and output quality | Yes | Yes |
deepseek-v4.1-flash | DeepSeek V4.1 Flash; a distinct model ID, not a V4 Flash alias | After deployment and enablement | After deployment and enablement |
V4.1 Flash becomes available only after its routing configuration is deployed and enabled. Use it only when GET https://api.requestbeam.com/v1/models returns deepseek-v4.1-flash for your API Key. This reference entry does not confirm a production rollout or a successful inference test. Existing V4 Flash and V4 Pro IDs remain unchanged.
This positioning helps you choose an initial model to test; it is not a latency, throughput, or quality SLA. Compare available models with your own prompts, output lengths, and concurrency before production use.
Authentication
Authorization: Bearer YOUR_API_KEY
Content-Type: application/jsonNon-streaming Request
The endpoint returns one complete Chat Completions response by default. The example includes stream: false explicitly so its behavior remains obvious when copied.
{
"model": "deepseek-v4-flash",
"messages": [
{
"role": "system",
"content": "You are a precise technical assistant."
},
{
"role": "user",
"content": "Explain three benefits of event-driven architecture."
}
],
"stream": false
}To use the Pro model, change only the model field:
{
"model": "deepseek-v4-pro"
}Streaming Request
Set stream: true explicitly for streaming and process the response as SSE events until [DONE].
{
"model": "deepseek-v4-pro",
"messages": [
{
"role": "user",
"content": "Create a checklist for a reversible database migration."
}
],
"stream": true
}Request Fields
modelstringrequiredUse deepseek-v4-flash, deepseek-v4-pro, or deepseek-v4.1-flash, as returned by GET https://api.requestbeam.com/v1/models.
messagesobject[]requiredOpenAI Chat Completions style messages. Each message contains role and content.
streambooleanDefault: falsetrue returns SSE; false returns one complete JSON response.
max_tokensintegerOptional maximum output tokens, as a positive integer. Omit this field to use the upstream default for the selected model. Depending on the model, the budget may include reasoning tokens as well as final text. A small budget can truncate the answer or be exhausted before final text; increasing it may increase cost.
max_completion_tokensintegerOptional compatibility alternative to max_tokens, with the same budget considerations. The selected model determines support; omit both fields to use the upstream default.
See Common Chat Completions for shared fields such as temperature, top_p, frequency_penalty, presence_penalty, stop, and n. Support and semantic effects may vary by model; this guide does not establish V4.1 Flash support for every optional field.
Success Response
{
"id": "chatcmpl_...",
"object": "chat.completion",
"created": 1787200000,
"model": "deepseek-v4-flash",
"choices": [
{
"index": 0,
"message": {
"role": "assistant",
"content": "1. Services can remain loosely coupled..."
},
"finish_reason": "stop"
}
],
"usage": {
"prompt_tokens": 31,
"completion_tokens": 96,
"total_tokens": 127
}
}Responses may contain additional usage details; treat them as optional.
Usage Notes
- The current public contract is Chat Completions, including non-streaming and SSE streaming.
- These models are not currently available through OpenAI Responses or Claude Messages.
- Set the request body's
modelfield to the exact ID:deepseek-v4-flash,deepseek-v4-pro, ordeepseek-v4.1-flash. - Use only model IDs returned by
GET https://api.requestbeam.com/v1/models. - Use
GET https://api.requestbeam.com/v1/modelsfor the models visible to the current API Key, and use the console for current pricing.