# Streaming (/docs/concepts/streaming)

Receive tokens as they are generated with server-sent events.



Set `"stream": true` and the response arrives as [server-sent events](https://developer.mozilla.org/docs/Web/API/Server-sent_events) instead of one JSON body. Each format keeps its own event shape:

| Endpoint               | Stream format                                                                |
| ---------------------- | ---------------------------------------------------------------------------- |
| `/v1/chat/completions` | `data:` lines of `chat.completion.chunk` objects, ending with `data: [DONE]` |
| `/v1/responses`        | Typed events such as `response.output_text.delta` and `response.completed`   |
| `/v1/messages`         | Anthropic events: `message_start`, `content_block_delta`, `message_stop`     |

## Token usage in streams [#token-usage-in-streams]

For chat completions, add `"stream_options": { "include_usage": true }` to get a final chunk with token counts. The Responses and Messages streams report usage in their closing events.

## Example [#example]

<Tabs items="[&#x22;Python&#x22;, &#x22;TypeScript&#x22;]">
  <Tab value="Python">
    ```python
    stream = client.chat.completions.create(
        model="deepseek-v4-1-flash",
        messages=[{"role": "user", "content": "Write a haiku about rivers."}],
        stream=True,
    )
    for chunk in stream:
        if chunk.choices and chunk.choices[0].delta.content:
            print(chunk.choices[0].delta.content, end="", flush=True)
    ```
  </Tab>

  <Tab value="TypeScript">
    ```ts
    const stream = await client.chat.completions.create({
      model: "deepseek-v4-1-flash",
      messages: [{ role: "user", content: "Write a haiku about rivers." }],
      stream: true,
    });
    for await (const chunk of stream) {
      process.stdout.write(chunk.choices[0]?.delta?.content ?? "");
    }
    ```
  </Tab>
</Tabs>
