---
title: "Streams the output of a process in real-time as it happens. This is the gRPC equivalent of a Server-Sent Events (SSE) endpoint."
method: GET
path: "/v1/{name}:streamOutput"
tags: ["ProcessService"]
---

# Streams the output of a process in real-time as it happens. This is the gRPC equivalent of a Server-Sent Events (SSE) endpoint.

`GET /v1/{name}:streamOutput`

## Request

- Base URL: `https://docs.h2o.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://docs.h2o.ai/v1/{name}:streamOutput`
- Auth: none declared
- TypeScript: <https://skmtc.dev/h2o/apis/ai-h2o-engine-sandbox-v1-filesystem-proto/docs/v1/:name:streamOutput/get.ts> (a function with typed inputs; its response is checked against the schema)

Authorization: Only the creator of the parent SandboxEngine is allowed to call this method.

## Path parameters

- `name` string, required

## Query parameters

- `skipReplay` boolean

## Response `200`

A successful response.(streaming responses)

- object
  - `result` V1StreamOutputResponse: A chunk of live process output.
    - `stream` 'OUTPUT_STREAM_UNSPECIFIED' | 'OUTPUT_STREAM_STDOUT' | 'OUTPUT_STREAM_STDERR' | 'OUTPUT_STREAM_COMBINED': Defines the output stream type for process output operations. - OUTPUT_STREAM_UNSPECIFIED: Not specified. The server may default to STDOUT. - OUTPUT_STREAM_STDOUT: The standard output stream. - OUTPUT_STREAM_STDERR: The standard error stream. - OUTPUT_STREAM_COMBINED: Both stdout and stderr combined (interleaved in order received).
    - `data` string, byte: The raw bytes of output data.
  - `error` RpcStatus
    - `code` integer
    - `message` string
    - `details` ProtobufAny[]
      - `@type` string: A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.

## Other responses

- `default`: An unexpected error response.

---

[API](https://skmtc.dev/h2o/apis/ai-h2o-engine-sandbox-v1-filesystem-proto.md) - [All operations](https://skmtc.dev/h2o/apis/ai-h2o-engine-sandbox-v1-filesystem-proto/llms.txt) - [OpenAPI document](https://skmtc.dev/h2o/apis/ai-h2o-engine-sandbox-v1-filesystem-proto/revisions/297cfadc1d39?raw)