Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the new web socket api #191

Open
npomfret opened this issue Jul 28, 2020 · 6 comments
Open

the new web socket api #191

npomfret opened this issue Jul 28, 2020 · 6 comments

Comments

@npomfret
Copy link

is it possible to request some additions to the new web socket api?

@npomfret
Copy link
Author

I need the original price and amount of the order in each message if possible

@npomfret
Copy link
Author

npomfret commented Aug 6, 2020

@martin-nginio

@martin-nginio
Copy link
Contributor

Hi @npomfret

Thanks for your feedback.

So I can better understand your request, please can you clarify

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

Thanks.

Regards,
Martin

@npomfret
Copy link
Author

npomfret commented Aug 7, 2020

No, I mean for the private websocket feed

@martin-nginio
Copy link
Contributor

Thanks @npomfret for your patience.

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.

Regards
Marti

@npomfret
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants