Events and messages

Session creation returns three event URLs:

streamUrl for the live native event stream
turnStreamUrl for turn-oriented live delivery
replayUrl for durable event recovery

Use the live stream for responsive interfaces. Persist the latest sequence number and use the router replay endpoints after reconnecting.

Replay native events

curl "https://api.case.dev/linc/v1/sessions/$SESSION_ID/events?cursor=120&limit=500" \
  -H "Authorization: Bearer $CASEDEV_API_KEY"

cursor is exclusive: the response contains events with a sequence number greater than the cursor. afterSeq is an alias, and excludeEventTypes accepts a comma-separated list.

{
  "sessionId": "linc_123",
  "cursor": 120,
  "lastSeq": 123,
  "events": [
    {
      "seq": 121,
      "type": "message_update",
      "data": {},
      "createdAt": "2026-07-28T14:00:00.000Z"
    }
  ]
}

Replay completed messages

Use the stable message read model when you need conversation history rather than every native runtime event:

curl "https://api.case.dev/linc/v1/sessions/$SESSION_ID/messages?cursor=0&limit=5000" \
  -H "Authorization: Bearer $CASEDEV_API_KEY"

The response includes completed messages, their source sequence numbers, the native session ID, and the resumable session-file path. Both events and messages remain available after a session ends.

Reconnect safely

Track the highest processed seq.
Reconnect the live stream when possible.
Replay from the stored cursor to fill any gap.
De-duplicate by sequence number.

This keeps clients correct across network interruptions, sandbox idle stops, and process restarts.

Get Started

Platform

Resources

Events and messages

Replay native events

Replay completed messages

Reconnect safely

​Replay native events

​Replay completed messages

​Reconnect safely

Replay native events

Replay completed messages

Reconnect safely