Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
APIError(code=-1013): Filter failure: LOT_SIZE shows after new update.
See original GitHub issueAPIError(code=-1013): Filter failure: LOT_SIZE is a new error which happens after the sell_amount = coins_bought[coin]['volume']*99.25/100 is added. Some currencies are not able to be traded with this amount as they need a integer.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:16 (6 by maintainers)
Top Results From Across the Web
Python-Binance.US api: APIError: (code=-1013): Filter failure
I found the issue. It was a result of the stepSize. Here is the code I used to fix it: quantity = str(step_size...
Read more >ERROR: -1013, Filter failure: LOT_SIZE · Issue #7 - GitHub
When I try to place an order I get this error: com.webcerebrium.binance.api.BinanceApiException: ERROR: -1013, Filter failure: LOT_SIZE How ...
Read more >XLMEUR - APIError(code=-1013): Filter failure: LOT_SIZE
A LOT_SIZE error implies that the quantity of the order does not conform with the LOT_SIZE filter. A symbol's filter can be obtained...
Read more >Errors by Number - eBay Developers Program
Error number Severity Description
335 Serious Error
12311 Warning Short error: TUV Error Long error: TUV Error
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Have pushed another update, I have tested on 3 different coins and the LOT_SIZE error seems to be gone 😃
Ok I know what’s going on here. For coins that cannot return a step size in decimals, the code will automatically convert it to one decimal point: 413618.0. I’m guessing, but I suspect that 413618 would pass. Need to figure out a way to apply this without disrupting the accurate volumes