Simple example, using Python 3 and the websocket-client library.
from websocket import create_connection
ws = create_connection("wss://ws.blockchain.info/inv")
tx = ws.recv()
with open("bitcointx.json", "a") as f:
f.write(tx + "\n####\n")
If I understand this correctly, you're trying to communicate with Bitcoin Core through ZeroMQ directly from the browser.
This is not possible.
The reason why JSMQ only supports Websockets (ws://) is that browsers don't allow you to use raw TCP sockets. The only protocols you can access from within the browser are HTTP(S), Websockets, and WebRTC (which is ...
The documentation of the authenticated side of the API from where these orders are created states the following:
After a te message you receive shortly a tu message that contains
the real trade id (TRD_ID) and additional/updated fields.
These updated fields are for example fees that are charged afterwards.
Although from the public side of the API this ...
The problem might be, that the JSON data does not contain line breaks. I was facing the same issue. My 'subscribe' call had no effect until I added line breaks to the JSON data. I haven't even gotten an error message back from the API.
You could use JSON library for Java which will handle the correct formatting for you.
Please note, there are some existing ...
I am hosting a webvisualization that depends on the websocket API from blockchain.info. The API stopped working at exactly 16:40:45 GMT yesterday (march 1st) for me.
This API has gone down in the past, let's hope it goes up fast.
EDIT: for me it is working again (since 13:50:14 GMT).
EDIT: SoChain offers no-authentication, WebSockets, API to monitor Bitcoin addresses in real-time. You can use this on ...
Basically Mtgox's api sucks. It's not your fault, its theirs. It's almost impossible to programmatically get a good reading of their order book. socket.io only works about 20% of the time and the http api often gives just wrong information.
To get around this I have several server instances constantly reconnecting an disconnecting until a successful steam ...