AsyncAPI channel · TwelveLabs · TwelveLabs Analyze Streaming (HTTP + NDJSON)

/analyze

Analyze NDJSON stream. The client opens this channel by issuing `POST /analyze` with `Content-Type: application/json` and a JSON body containing `stream: true` (the default). The server responds with `Content-Type: application/x-ndjson` and emits a sequence of newline-delimited JSON objects: a single `stream_start`, one or more `text_generation` events each carrying a slice of generated text, and

Provider: TwelveLabs AsyncAPI: v2.6.0 Spec: TwelveLabs Analyze Streaming (HTTP + NDJSON) Operations: 1 Messages: 3

Channel address

/analyze

Operations

streamAnalyzeEvents
Subscribe to streamed analyze events (NDJSON).

Messages

StreamStart
First NDJSON event, signaling the beginning of the generation stream.
Content-Type: application/x-ndjson
TextGeneration
Carries a slice of generated text. Many of these are emitted in order.
Content-Type: application/x-ndjson
StreamEnd
Final NDJSON event, carrying finish reason and usage statistics.
Content-Type: application/x-ndjson

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.