congratulations! clients of primal cache instance are using websocket connections to send API request messages and get back API response messages. available API requests are defined in file called app.jl but i would suggest, beside looking at that code, you take a look at live communication between primal webapp (at primal.net) and primal server. in your web browser you should be able to open devtools/network tab, and select websocket connection to wss://cache2.primal.net/v1and look at the messages that are being sent and received. there you will be able to see common structure of each API request/response that the webapp is using which is almost everything currently available from our cache instance. webapp usually is the first to use new features and then i tell the same suggestion to our mobile app developers when i want to explain new API requests. ofc sometimes i have to additionally clarify some aspects of new API requests since nobody knows all the details which are sometimes important to mention. that's it. and feel free to ask again.