AsyncAPI 2.6 description of Greptile's **query streaming** surface. Greptile does not publish a WebSocket API. The only asynchronous / event-style transport documented at https://docs.greptile.com/quickstart and https://docs.greptile.com/api-reference/query is **HTTP Server-Sent Events (SSE)** delivered over the same REST endpoint (`POST /query`) when the request body sets `stream: true`. The `POST /search` endpoint accepts the same `stream` flag. SSE is a one-way, server-to-client HTTP streaming channel; it is **not** WebSocket. This AsyncAPI document models only the streamed events emitted by Greptile's SSE response. The request body itself (messages, repositories, sessionId, genius) is modeled in the companion OpenAPI document at `openapi/greptile-openapi.yml`.
View SpecView on GitHubArtificial IntelligenceCodebase UnderstandingCode ReviewCode SearchDeveloper ToolsAsyncAPIEventsWebhooks
Channels
/v2/query
subscribereceiveQueryStream
Receive streamed answer and source chunks.
Server-Sent Events stream returned by POST /v2/query when stream=true. Chunks carry incremental answer text and source references.
Messages
✉
QueryStreamChunk
Query Stream Chunk
A single data-only Server-Sent Event chunk in the streamed query response. Chunks incrementally deliver answer text and source references; the stream terminates per the SSE protocol.
Servers
https
productionapi.greptile.com
Greptile REST API host. The streaming channel is the SSE response of POST /v2/query (and POST /v2/search) when stream=true. This is HTTP SSE, not WebSocket.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.