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

Handle Binance order statuses #11

Closed
fbn-roussel opened this issue Sep 5, 2021 · 0 comments · Fixed by #19
Closed

Handle Binance order statuses #11

fbn-roussel opened this issue Sep 5, 2021 · 0 comments · Fixed by #19
Assignees
Labels
enhancement New feature or request
Projects

Comments

@fbn-roussel
Copy link
Collaborator

Below is the exhaustive list that Binance can return when sending an order :

Status Description
NEW The order has been accepted by the engine.
PARTIALLY_FILLED A part of the order has been filled.
FILLED The order has been completed.
CANCELED The order has been canceled by the user.
PENDING_CANCEL Currently unused
REJECTED The order was not accepted by the engine and not processed.
EXPIRED The order was canceled according to the order type's rules (e.g. LIMIT FOK orders with no fill, LIMIT IOC or MARKET orders that partially fill)or by the exchange, (e.g. orders canceled during liquidation, orders canceled during maintenance)

Currently the status is not check when an order is sent even if it is not FILLED (aka order has been successfully processed).

See how to handle the other statuses.

@fbn-roussel fbn-roussel added the enhancement New feature or request label Sep 5, 2021
@fbn-roussel fbn-roussel self-assigned this Sep 5, 2021
@fbn-roussel fbn-roussel added this to To do in BOT trading via automation Sep 5, 2021
@fbn-roussel fbn-roussel linked a pull request Sep 7, 2021 that will close this issue
BOT trading automation moved this from To do to Done Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant