There seem to be still more issues with the web hooks. Firstly the documentation example mentions that 'trading_symbol' will be returned whereas the key is 'tradingsymbol'. Then 'filled_quantity' is also returned, the documentation is silent about this, so can we reliably use this? Then documentation for the 'status' says that there may be other values as well. The documentation should atleast state all possible values so that code at our side can handle the situations appropriately. Another issue faced while using websockets was that whenever an order is placed, the websocket returns some data that does not conform to the format of messages expected. This is most unexpected, are you also trying to send some response of the order placed via web sockets?
Have fixed checksum issue, it now returns 64 character long string (previously we were returning sha1 checksum instead of sha256).
Firstly the documentation example mentions that 'trading_symbol' will be returned whereas the key is 'tradingsymbol'.
Fixed our documentation, key now is 'tradingsymbol'
Then 'filled_quantity' is also returned, the documentation is silent about this, so can we reliably use this?
Added the field 'filled_quantity' to documentation
Then documentation for the 'status' says that there may be other values as well. The documentation should atleast state all possible values so that code at our side can handle the situations appropriately.
Currently we are sending post back for only COMPLETE, REJECTED, CANCELLED statuses, In future we may also include status OPEN.
Another issue faced while using websockets was that whenever an order is placed, the websocket returns some data that does not conform to the format of messages expected. This is most unexpected, are you also trying to send some response of the order placed via web sockets?
Websocket returns two data types text and binary, you can safely ignore text data.
thanks
Have fixed checksum issue, it now returns 64 character long string (previously we were returning sha1 checksum instead of sha256). Fixed our documentation, key now is 'tradingsymbol' Added the field 'filled_quantity' to documentation Currently we are sending post back for only COMPLETE, REJECTED, CANCELLED statuses, In future we may also include status OPEN. Websocket returns two data types text and binary, you can safely ignore text data.