-
Notifications
You must be signed in to change notification settings - Fork 48
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
Error code Code: 796 while creating new positions with leverage #12
Comments
hi,
thanks for the interest to this project.
I'll investigate it and let you know.
It could be something with watchlist.json try to delete it and try again.
Best regards,
Oleh
…________________________________
От: iteddy09 <[email protected]>
Отправлено: 29 сентября 2020 г. 19:04
Кому: oleh2208/etoro-api <[email protected]>
Копия: Subscribed <[email protected]>
Тема: [oleh2208/etoro-api] Asset with id XXXXX was not found. (#12)
Hello,
Really nice work. Thank you for your time and implication.
Currently I think it is an issue with opening new positions.
{
"name": "aapl",
"type": "BUY",
"amount": 500,
"leverage": 5,
"takeProfitRate": 350,
"stopLossRate": 105
}
always return regardless of instrument used.:
{
"timestamp": "2020-09-29T17:01:44.485+0000",
"status": 500,
"error": "Internal Server Error",
"message": "Asset with id 1001 was not found.",
"path": "/etoro-api/positions/open"
}
Did you take into consideration to update it in order to create limit orders?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#12>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADHNNVVOGUB32ABYMLDA5LLSIIHRRANCNFSM4R6B3VBQ>.
|
About order API, it's relatively easy to implement,
although I have a lot to do now and I can't continue with this soon.
…________________________________
От: iteddy09 <[email protected]>
Отправлено: 29 сентября 2020 г. 19:04
Кому: oleh2208/etoro-api <[email protected]>
Копия: Subscribed <[email protected]>
Тема: [oleh2208/etoro-api] Asset with id XXXXX was not found. (#12)
Hello,
Really nice work. Thank you for your time and implication.
Currently I think it is an issue with opening new positions.
{
"name": "aapl",
"type": "BUY",
"amount": 500,
"leverage": 5,
"takeProfitRate": 350,
"stopLossRate": 105
}
always return regardless of instrument used.:
{
"timestamp": "2020-09-29T17:01:44.485+0000",
"status": 500,
"error": "Internal Server Error",
"message": "Asset with id 1001 was not found.",
"path": "/etoro-api/positions/open"
}
Did you take into consideration to update it in order to create limit orders?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#12>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADHNNVVOGUB32ABYMLDA5LLSIIHRRANCNFSM4R6B3VBQ>.
|
i can implement, sure. but currently i don't managed to find documentation for "https://www.etoro.com/sapi/" |
did you reverse engineer the requests their web ui use ? |
yes
…________________________________
От: iteddy09 <[email protected]>
Отправлено: 27 октября 2020 г. 15:16
Кому: oleh2208/etoro-api <[email protected]>
Копия: oleh2208 <[email protected]>; Comment <[email protected]>
Тема: Re: [oleh2208/etoro-api] Error code Code: 796 while creating new positions with leverage (#12)
did you reverse engineer the requests their web ui use ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#12 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADHNNVSF273FAEHUB577GQLSM3B3FANCNFSM4R6B3VBQ>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Really nice work. Thank you for your time and implication.
Currently I think it is an issue with opening new positions.
leverage on aapl works on web ui but on api level this error is prompted:
It works only with leverage 1.
Did you take into consideration to update it in order to create limit orders?
Thank you!
The text was updated successfully, but these errors were encountered: