<aside> 🧑‍💻 This documentation is part of the Technical Kick-start Collection. If you’re a developer interested in contributing to Thea, or just looking to understand how Thea works on a deeper level, then I’d highly recommend reading through this collection.
</aside>
Currently Thea has two protocols for communication:
A standard HTTP API:
An websocket-based activity API:
The bundled Svelte-based web client communicates with the Thea server using both of these protocols, using the HTTP Rest API for initial connection and state requests, and switching to using the WebSocket connection for the rest of its communication.
Here you’ll find the main categories of API that the Thea web client consumes, along with links to the technical documentation for the routes.
… TODO …