We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Latest v20 release gices me: "Invalid JSON body, must be an object" as the error message on a 400 response to using the position.close command.
my code looks like this: req = api.position.close('account_id', 'EUR_USD')
Auth and everything else works (same API context can place orders, list orders, get account info.. etc..)
It appears to only work if I include the longUnits or shortUnits variables... but the documentation and method both suggest this should not be needed.
The text was updated successfully, but these errors were encountered:
The same happens just listening price data as well.
Sorry, something went wrong.
There are plenty of cases when the JSON loaded without try-catch blocks.... Wondering it is blind trust to oanda APIs?
No branches or pull requests
Latest v20 release gices me: "Invalid JSON body, must be an object" as the error message on a 400 response to using the position.close command.
my code looks like this:
req = api.position.close('account_id', 'EUR_USD')
Auth and everything else works (same API context can place orders, list orders, get account info.. etc..)
It appears to only work if I include the longUnits or shortUnits variables... but the documentation and method both suggest this should not be needed.
The text was updated successfully, but these errors were encountered: