# Ignition as WebSocket client

**URL:** <https://forum.inductiveautomation.com/t/ignition-as-websocket-client/112935>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [December 21, 2025, 8:43am UTC](https://forum.inductiveautomation.com/t/ignition-as-websocket-client/112935 "2025-12-21T08:43:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 21, 2025, 2:39pm UTC](https://forum.inductiveautomation.com/t/ignition-as-websocket-client/112935/2 "2025-12-21T14:39:13Z")

</div>

Possible with jython scripts.

> [@WebSocket Client](https://forum.inductiveautomation.com/t/websocket-client/44447/21):
>
> Merged at this point from here: So after clarifying some additional code that was needed and running from the correct gateway context, it works! This means we have a way to get data into Ignition from massive Kafka topics by using the lenses SQL api mentioned here: [https://api.lenses.io/branches/4.3/index.html#data-access-query-data-via-sql-get](https://api.lenses.io/branches/4.3/index.html#data-access-query-data-via-sql-get) There were a few more things required, namely encoding the text you send and conversion of the return (here I just put it to string so as…

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-as-websocket-client/112935)._
