You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This event includes price/volume for each individual order.
There is another event (recently added, orderbookUpdate event) that allows you to build a copy of the orderbook locally more efficiently but this has aggregate volume so no individual orders are presented. https://api.btcmarkets.net/doc/v3/#section/OrderbookUpdate-event
We have a few update for WebSocket in our roadmap and providing more order related attributes to the orderChange event (e.g. original volume/price ) can be added to it as well. At this stage I can't comment on the timeline but I understand this would be helpful.
Where possible and as a workaround, I'd suggest keeping detail of the order submitted with link to orderId returned by place order API.
Thanks,I have workarounds in place but they inevitably cause delays. Most exchanges return the entire original order plus the fill details (id, time, amount, price) - this approach seems to work best.
Activity
npomfret commentedon Jul 28, 2020
I need the original price and amount of the order in each message if possible
npomfret commentedon Aug 6, 2020
@martin-nginio
martin-nginio commentedon Aug 6, 2020
Hi @npomfret
Thanks for your feedback.
So I can better understand your request, please can you clarify
orderbookevent here: https://api.btcmarkets.net/doc/v3/#section/Orderbook-eventThis event includes price/volume for each individual order.
There is another event (recently added,
orderbookUpdateevent) that allows you to build a copy of the orderbook locally more efficiently but this has aggregate volume so no individual orders are presented.https://api.btcmarkets.net/doc/v3/#section/OrderbookUpdate-event
Thanks.
Regards,
Martin
npomfret commentedon Aug 7, 2020
No, I mean for the private websocket feed
martin-nginio commentedon Aug 13, 2020
Thanks @npomfret for your patience.
We have a few update for WebSocket in our roadmap and providing more order related attributes to the
orderChangeevent (e.g. original volume/price ) can be added to it as well. At this stage I can't comment on the timeline but I understand this would be helpful.Where possible and as a workaround, I'd suggest keeping detail of the order submitted with link to
orderIdreturned by place order API.Thanks.
Regards
Marti
npomfret commentedon Aug 13, 2020
Thanks,I have workarounds in place but they inevitably cause delays. Most exchanges return the entire original order plus the fill details (id, time, amount, price) - this approach seems to work best.