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

action: disabled #558

Open
1 task
kamali-sina opened this issue Sep 16, 2020 · 2 comments
Open
1 task

action: disabled #558

kamali-sina opened this issue Sep 16, 2020 · 2 comments

Comments

@kamali-sina
Copy link

kamali-sina commented Sep 16, 2020

Issue type

  • performance

Brief description

I am trying to use a paper account to get used to the api, and I have generated a fully functioning api key for it. But when I try to do any sort of PaperTrading with the api I get the message:
"[BfxWebsocket] [ERROR] Notification ERROR: action: disabled"

Steps to reproduce

-Setup a paper sub account
-Get api key for it
-Try to trade in any of the paperMarkets

Additional Notes:

My code is as follows:
async def open_trade(symbol,price,amount,_type='sell',market_type='EXCHANGE LIMIT',price_trailing_amount=5):
if (_type == 'sell'):
amount = -amount
await bfx.ws.submit_order(symbol=symbol, price=price, amount=amount, market_type=market_type,leverage=1,price_trailing=price_trailing_amount)

@pro-git
Copy link

pro-git commented Feb 8, 2021

Same issue here with REST submitOrder on pair tTESTBTCTESTUSD
tAAABBB pair is working.

WS submitOrder is not working on any pair (tAAABBB ERROR: trading: invalid symbol (paper))

@MarcelWind
Copy link

Same here. Code from Examples.

submit_order_notification: Notification[Order] = bfx.rest.auth.submit_order( type="EXCHANGE LIMIT", symbol="tBTCUSD", amount=0.015, price=10000 )

Crashes with
The server replied to the request with a generic error with message: <trading (paper): invalid symbol (non-paper)>.

Question: why does this crash the program? I get that the API doesn't recognize trading pairs on paper accounts, and who cares, but this reply should just cascade upwards and be returned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants