No, use the WS API, that is why it is there.
Securifi already have implemented six (LocalWebUI, CloudWebUI, LCD,App,WS API, programming API) different ways to control your Almond and its sensors. They really shouldn't add a seventh, as they can hardly keep all features in sync as it is.
while i do appreciate WS API, i believe that HTTP RESTful API should've been prioritized as this has become the standard API for a lot of things already and it is much more simple and elegant to work with rather than dealing with persistent sockets which is a resource hog, most shared hosts wont even allow, and that it is less stable because maintaining persistent connection between two machines is less bulletproof than on demand TO and FROM http communication.
And personally for me at the moment, I just wanted to run a PHP file ever X seconds that will open and close HTTP connection to Almond and get device status . that's all and that's easily done w/ 1 php file , less dependencies, and a cronjob.
But with Web Sockets, i now need to keep a browser open and running to maintain the socket connection (HTML5 sockets) just to do this. and if the browser is accidentally closed, well you get the point.
I supposed i can take the same php + cron job approach, only this time php will open socket, authenticate, send receive message, then close it and rest.. this actually adds strain on the server having open, wait, maintain, and close sockets. rather tha just GET HTTP and wait for response.
anyway, HTTP API would've been best and more universal to start with in my opinion, and I hope Securifi would consider.