Open
Conversation
Currently
```
response = api.pricing.get(
OANDA_ACCOUNT_ID,
instruments='EUR_USD',
since=latest_price_time,
includeUnitsAvailable=False)
print(response)
```
can return the following:
```Method = GET
Path = https://api-fxpractice.oanda.com:443/v3/accounts/123-456-12345678-123/pricing?instruments=EUR_USD&since=2019-10-08T21%3A38%3A14.598266Z&includeUnitsAvailable=False
Status = 200
Reason = OK
Content-Type = application/json```
As I was not familiar with v20, I clicked the link to quickly check the result.
Naturally this gave me "Insufficient authorization to perform request."
Only after digging in the source I found the (raw_)body attribute, the one I wanted to use/check in the first place.
With the proposed change, the result would be the following:
```
Method = GET
Path = https://api-fxpractice.oanda.com:443/v3/accounts/123-456-12345678-123/pricing?instruments=EUR_USD&since=2019-10-08T21%3A38%3A14.598266Z&includeUnitsAvailable=False
Status = 200
Reason = OK
Content-Type = application/json
Raw_Body = {"time":"2019-10-08T21:37:00.794720020Z","prices":[{"type":"PRICE","time":"2019-10-08T21:36:52.424438721Z","bids":[{"price":"1.09539","liquidity":10000000}],"asks":[{"price":"1.09572","liquidity":10000000}],"closeoutBid":"1.09524","closeoutAsk":"1.09587","status":"tradeable","tradeable":true,"quoteHomeConversionFactors":{"positiveUnits":"0.91264192","negativeUnits":"0.91291686"},"instrument":"EUR_USD"}]}
```
This immediately shows the response body, gives the hint to use the raw_body attribute and does not lead to believe that there is an issue with authentication
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently
can return the following:
As I was not familiar with v20, I clicked the link to quickly check the result.
Naturally this gave me "Insufficient authorization to perform request."
Only after digging in the source I found the (raw_)body attribute, the one I wanted to use/check in the first place.
With the proposed change, the result would be the following:
This immediately shows the response body, gives the hint to use the raw_body attribute and does not lead to believe that there is an issue with authentication