Skip to main content
GET
/
v1
/
executions
/
:operationId
/
stream
Execution Stream
curl --request GET \
  --url https://api.glider.fi/v1/executions/:operationId/stream \
  --header 'X-API-KEY: <api-key>'
Use this endpoint when you want direct HTTP streaming for a submitted execution. It emits the same canonical execution events used by v2.executions.stream, but over standard SSE for CLIs, API integrators, and future chat surfaces.

Auth

  • Wallet session cookie
  • or X-API-KEY

Resume Semantics

  • Send Last-Event-ID with the opaque stream cursor from the SSE id field (the same value is also exposed as cursor in each event payload).
  • The server replays any missed canonical events before switching to live tail.
  • v2.executions.get and v2.executions.detail remain available for snapshot hydration and explicit detail fetches.

Event Envelope

Each SSE message uses a canonical event envelope:
{
  "streamId": "execution:op_123",
  "eventId": "1743163201000-0",
  "sequence": 17,
  "ts": "2026-03-28T15:10:00.000Z",
  "kind": "execution.timeline_appended",
  "operationId": "op_123",
  "cursor": "1743163201000-0",
  "payload": {
    "message": "Swap submitted onchain"
  }
}
Current execution event kinds:
  • execution.snapshot
  • execution.state_changed
  • execution.timeline_appended
  • execution.progress
  • execution.result
  • execution.error

Example Call

curl -N \
  --request GET \
  --url 'https://api.glider.fi/v1/executions/op_123/stream' \
  --header 'X-API-KEY: <api-key>'
Resume from a previously consumed event:
curl -N \
  --request GET \
  --url 'https://api.glider.fi/v1/executions/op_123/stream' \
  --header 'X-API-KEY: <api-key>' \
  --header 'Last-Event-ID: 1743163201000-0'
Example SSE frame:
id: 1743163201000-0
event: execution.timeline_appended
data: {"streamId":"execution:op_123","eventId":"1743163201000-0","sequence":17,"ts":"2026-03-28T15:10:00.000Z","kind":"execution.timeline_appended","operationId":"op_123","cursor":"1743163201000-0","payload":{"message":"Swap submitted onchain"}}