How to implement durable streaming with Electric HTTP API

[lekhnath]

I'm implementing a durable stream consumer in Python (Django) using the Electric HTTP API, and I’m stuck .

Issues I'm facing

1. Handle → durable response
   I don’t understand how the handle from the Electric HTTP API is supposed to be passed back or reused for durable responses. I also didn’t see any mention of a handle in the durable protocol documentation, which adds to the confusion.

   • Is the handle persistent or session-scoped?
   • Should it be stored?
   • How is it used when reconnecting?

2. LSN vs offset
   From SSE events I only receive an LSN, not an offset.

   • Is the LSN intended to act as the offset?
   • If so, what’s the correct way to store and resend it?
   • How do you resume safely without reprocessing or skipping events?

Any clarification, examples, or guidance would help. Thanks!

[KyleAMathews]

Electric doesn't yet run on the durable streams protocol. We made some slight modifications to the electric protocol based on things we've learned and to make it truly generic. Electric 2.0 will speak durable streams. In the meantime, check out this doc https://electric-sql.com/docs/guides/client-development

[lekhnath]

@KyleAMathews Got it. Thanks for the clarification.