Price Field in User Websocket

Hi all,

I’m in the process of testing a client, and realized that the actual order price (what the order was created with), isn’t included in the User websocket channel updates. Is this something that can be added? Having avg_price is great, so we don’t have to re-compute it on our end, but having the original order price would be a good addition, since avg_price is often 0 if the order has had no fills yet and this makes having matching order data between the REST and websocket APIs difficult.

Thanks,
Brendan

1 Like

Hello @brendano257! Thank you for bringing this up to our attention. For the details regarding your concern, we will check on this for you with our team to ensure this is addressed accurately for you. We will get back to you once we have more information. Keep in touch!

1 Like

Hi @brendano257!

Regarding your request to add the actual price in the user websocket channel , we’ve logged this feature request with our internal teams so we can continue improving our user experience. Most new features and improvements to our products come directly from feedback like yours, so it’s very valuable to us. While we can’t offer any specific timeline for adding features, we are constantly working to build products our customers will love.

If you want to stay up to date on the latest from Coinbase Cloud, you can also bookmark the following webpage and subscribe to email updates at the bottom of the page: https://www.coinbase.com/cloud/discover

We hope this is helpful, and please let us know if you have any other questions.

Thank you!

1 Like

Thanks @Mamoshi27! It’s great to see our feedback come to life in the product. Have a great day!

2 Likes

I second this. Having the order description without the basic info about the order makes it useless. Need to have original Quantity, Limit and/or stop price, etc. basically the full description at least in the initial order sent.

Hello @jmedved! Thank you for your enthusiasm and interest with Coinbase APIs. We appreciate you for bringing this up to our attention. We’ve also logged your feature request about having the original quantity, limit and/or stop price, etc. in the initial order sent in the user websocket channel with our internal teams so we can continue improving our user experience.

Like what we mentioned, most new features and improvements to our products come directly from feedback like yours, so it’s very valuable to us. While we can’t offer any specific timeline for adding features, we are constantly working to build products our customers will love.

If you want to stay up to date on the latest from Coinbase Cloud, you can also bookmark the following webpage and subscribe to email updates at the bottom of the page: https://www.coinbase.com/cloud/discover

Thank you!

Yes this is a necessity. I’m currently spamming the REST API for OPEN Orders because of the lack of this pertinent data coming from the User WS feed. Can you please get to this soon?
Thanks for your time.

The way Im getting this to work until it gets updated is to put the price and size in the client_order_id field when making the limit order. Then pulling it out of the client_order_id when the order is filled or when its sent from the User WS feed.
Hope this helps
Bomes