AsyncAPI channel · cohere · Cohere Streaming API

`/v1/chat`

Cohere v1 Chat streaming endpoint (legacy). Sent as `POST /v1/chat` with `"stream": true`. Returns a `text/event-stream` body whose events are discriminated by the `event_type` field. Documented events: `stream-start`, `search-queries-generation`, `search-results`, `text-generation`, `citation-generation`, `tool-calls-generation`, `tool-calls-chunk`, `stream-end`, `debug`.

Open source AsyncAPI → All cohere channels cohere provider profile

Provider: cohere AsyncAPI: v2.6.0 Spec: Cohere Streaming API Operations: 1 Messages: 9

Channel address

/v1/chat

Operations

publish

receiveV1ChatStream

Receive v1 Chat streaming events

Messages

streamStart

v1 stream-start

Content-Type: application/json

searchQueriesGeneration

v1 search-queries-generation

Content-Type: application/json

searchResults

v1 search-results

Content-Type: application/json

textGeneration

v1 text-generation

Content-Type: application/json

citationGeneration

v1 citation-generation

Content-Type: application/json

toolCallsGeneration

v1 tool-calls-generation

Content-Type: application/json

toolCallsChunk

v1 tool-calls-chunk

Content-Type: application/json

streamEnd

v1 stream-end

Content-Type: application/json

chatDebug

v1 debug

Content-Type: application/json

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.