This is a feedback for your Advanced Trade Api , specifically for Tickers-batch:
- This seems obviously not an progress compared to previous version. i.e. Binance provides updates in every 1000 ms, and you provide in every 5000ms. 5x more degraded performance (speed) which renders it almost useless endpoint in our apps.
Please make an additional option, so, OK KEEP 5000MS as default, but give us an option that we could get updates in 1000 ms too, if we set that option. for rest of world, if not setting that option specifically, you continue providing them at 5000 ms interval as is.
So, no breaking changes.
- in docs, there is not written a clear example, what is the response structure. it says that “same schema as ticker”, but ticker is one object per message, and batch tickers should be something like binance has:
where each item is independent ticker schema, exactly like binance provides bulk items in array in every 1000ms.
please pass this request to dev.team.
Thank you for sharing your feedback regarding the response structure in the documentation of the Ticker Batch Channel and your interest to have an additional option of getting an update from Ticker Batch Channel in 1000ms. We will communicate this with our internal teams and log this as both feedback and a feature request. Most new features and improvements to Coinbase products come directly from feedback like yours, so it’s very valuable to them. While Coinbase can’t offer any specific timeline for adding features, they are constantly working to build products that their 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
Thanks for follow up. Also, note that if the API team won’t add that feature (1000MS update interval), then people will be obliged to stress the REST api with making rest request toward Get product stats | Coinbase Cloud endpoint, once in every 1000 ms. So, it will be better for yourself too, to avoid extra unnecessary stress on your servers.
Please let us know update about this problem.
Hi @ttodua! Please be informed that this has been noted as a feedback/feature request with our internal teams and is subject for evaluation before actual implementation.
@Anonymouse I don’t ask for immediate implementation, just I want to know any of their thoughts/feedbacks, what they think - do they recognize the problem, have they read the inquiry at all, or they read and are not going to add it? just some words from them, why is that so hard?
Hi @ttodua! We understand that you want to receive updates and feedback regarding your feature request. However, please note that we are unable to disclose any of our product roadmap. Rest assured that we are constantly reviewing posts to take your input into account and will do our best to share updates when available. The internal product and engineering teams are still hard at work on this matter. While, they cannot provide direct comments, please know that we’ll share our planned product updates to the extent that is possible and will do our best to keep the community updated on which requests will be implemented when we’re ready and able to share that news.
We appreciate your understanding!
Hello guys, do we have any update?