-
Notifications
You must be signed in to change notification settings - Fork 385
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
Implement submit multiple orders for Binance #1198
Comments
This issue is now being actively worked on. We're introducing enhancements to how orders are handled in the system, particularly focusing on batch commands. Here's a rundown of the changes and new features being implemented. Batch submit Batch modify and cancel Intended behavior is described in the initial version of the docstrings:
Excerpt from docstring:
@objectin any thoughts/feedback on the above? |
Seems nice, it will extremely helpful for handling multiple orders in a batch. And also for ratelimit problems when handling a bunch of orders. |
So I decided to go a different way for the case of the batch cancel, simply call this from the strategy now (passing a list of orders): self.cancel_orders(orders) This will create a Now implemented for backtesting and Binance Futures on |
Next up I'll implement the batch modify, which will probably follow the API which was first proposed ^. |
The batch modify involves larger changes to the core platform -- moving this to the backlog for now. |
Feature Request
Description
Implement the functionality to support multiple orders execution for Binance as per their official API documentation:
Requirements
1. Placing Multiple Orders (TRADE)
/fapi/v1/batchOrders
.2. Modifying Multiple Orders (TRADE)
/fapi/v1/batchOrders
.The text was updated successfully, but these errors were encountered: