oanda / apidocs

OANDA REST API Documentation

Please refer to our API developer site developer.oanda.com for all REST API information.

apidocs's Issues

Transaction history "duration" field should be called "expiry"

This would be consistent with orders and make more sense

Also shouldn't it be sent as rfc3339 rather than unix time?

Should return error if requesting for a list of trades while using an instrument that does not exist.

http://api-sandbox.oanda.com/v1/accounts/1179804/trades?instrument=dfdf

please add 'category' field to v1/instruments

category code could be:

1 - Bond
8 - Commodity
2 - Currency
4 - Index

Historical data missing

Historical pricing data before year 2010 is missing.

When requesting for account open trades, the "nexPage" key should have an empty value when there are no unique trades on the next page

http://api-sandbox.oanda.com/v1/accounts/1179804/trades?count=50&instrument=EUR_USD&maxTradeId=176201355&tradeIds=176201356

misleading overview documentation

Found a few problems with the documentation

• docs say "/v1/instruments/:instrument/candle" when it's actually "/v1/instruments/:instrument/candles"
• POST "/v1/users/:username" doesn't do anything. (actually post "/v1/users"?). It probably should be "PUT" "/v1/users/:username" since you know the resource name ahead of time, or POST "/v1/users"

I was frustrated /v1/instruments/price wasn't working, but I didn't realize it needed a parameter and I could "drill down" on the overview for more details.

Transaction history suggestion: omit null fields

This could save a lot of bandwidth

GET /v1/accounts account information

Is there a way that this call can return accountIds with additional infos like accountType, home currency etc...
Right now it is only returning a comma separated account ids.

Inconsistent names for transaction ids

Please make the keys for the transactions ids the same. Currently the response from opening a trade is "opened" and 'id" for modifying and closing a trade. Instead, change everything to "transactionId".

This is the response when a trade is opened
{
closed = ();
instrument = "EUR_USD";
interest =();
marginUsed = "6.11";
opened = 176203144;
price = "1.2598";
side = buy;
time = "2013-05-28T15:59:18Z";
units = 97;
updated = 0;
}

This is the response when a trade is modified
{
id = 176203144;
instrument = "EUR_USD";
price = "1.2598";
side = buy;
stopLoss = 0;
takeProfit = 0;
time = "2013-05-28T15:59:18Z";
trailingStop = 0;
units = 97;
}

This is the response when a trade is closed
{
id = 176203144;
instrument = "EUR_USD";
price = "1.2598";
side = buy;
stopLoss = 0;
takeProfit = 0;
time = "2013-05-28T15:59:18Z";
trailingStop = 0;
units = 97;
}

Update documentation to correctly reflect recent changes to account creation

The Create a Test User section in Getting started is no longer valid.

The /users api has been removed and the following link to create an account no longer works.
http://developer.oanda.com/gen-account.html

The following pages need to be updated.

https://github.com/oanda/apidocs/blob/master/sections/getting_started.md
https://github.com/oanda/apidocs/blob/master/sections/trading_quick_start.md

In consistent time formats for instruments and trades

Is there a reason why the time format is different for instruments and trades?

Instrument uses UTC millisecond time and trades/orders uses UTC RFC3339 formatted time.

Can we be consistent and use the same time format everywhere?

Streaming rates instrument naming conventions

Streaming rates is great! However it currently seems to use instrument display names rather than the instrument names returned by /v1/instruments. Maybe it (and other parts of the API) could accept "EUR_USD" as well as "EUR/USD", for example.

Not returning anything when two trade Ids are specified.

When http://api-sandbox.oanda.com/v1/accounts/1179804/trades?count=4&instrument=EUR_USD&tradeId=176201454,176201356 url is request, it should return two trades but it's not returning anything.

Feature request: Streaming rates

At the moment streaming rates are only available through FIX and Java API. Would be great to have similar functionality through REST API, simple socket or MQ.

remove 'direction' field and use signed units instead

Link on README.md does not work

Clicking on http://api-sandbox.oanda.com/v1/quote?instruments=EUR_USD, returns

{
"code" : 38,
"message" : "No matching handler for the request is found",
"moreInfo" : "http://developer.oanda.com/docs/v1/troubleshooting/#errors"
}

v1/instruments: please include precision and instrument id values

v1/instruments needs update

v1/instruments does not return all data fields mentioned in the documentation.

Socket.io javascript source is not available

http://api-sandbox.oanda.com/ratestream/socket.io.js returns a 404 error.

v1/instruments does not return all symbols that are available within the platform

Full list here: https://github.com/laurinkus/oanda-java-api/blob/master/SymbolStore/symbols.txt

Transaction history returns only the latest 50 records. Count and maxTransId params have no effect.

http://api-sandbox.oanda.com/v1/accounts/5172550/transactions?count=100

Returns only the most recent 50 transaction records.
Paging has no effect, once the latest 50 transactions are returned.

http://api-sandbox.oanda.com/v1/accounts/5172550/transactions?count=40&maxTransId=178692345

v1/instruments missing fields

Please add precision and symbol id fields

Pagination problem

GET /v1/accounts/:account_id/orders
GET /v1/accounts/:account_id/trades
GET /v1/accounts/:account_id/transactions

Each of these is currently including "nextPage" even when there are no further items to retrieve. "nextPage" is only omitted from a response with zero items

This results in having to do a redundant query to get a final page with no items.

"nav" value missing from account details responses

Despite being documented the "nav" value is currently missing from server responses:

GET /v1/accounts/8139117

{
"accountId" : 8139117,
"accountName" : "Primary",
"balance" : 100000,
"unrealizedPl" : 0,
"realizedPl" : 0,
"marginUsed" : 0,
"marginAvail" : 100000,
"openTrades" : 0,
"openOrders" : 0,
"marginRate" : 0.05,
"homecurr" : "GBP"
}

Also, shouldn't "homecurr" be "homeCurr"?

Creating more that 26 open trades is not permitted

If there are 26 open trades any additional attempts to open another trade generates a 403 error:
HTTP error code : 403 Msg: Forbidden Request

This trading limit is not present on the current Oanda API.

missing fields in response to trade request

Hello,

this is the server response to a trade (POST /v1/accounts/:account_id/trades):

{
"ids" : [
178471630
],
"instrument" : "EUR_USD",
"units" : 654127,
"price" : 1.31661,
"marginUsed" : 43061.5075,
"direction" : "short"
}

The following fields are missing:

"time" : ,
"takeProfit" : ,
"stopLoss" : ,
"trailingStop" : ,

thanks

Price data not accurate in the sandbox?

If you visit http://api-sandbox.oanda.com/v1/instruments/EUR_USD/price right now, it returns:

{
    "instrument": "EUR_USD",
    "time": 1371124431.220175,
    "bid": 1.25971,
    "ask": 1.2598
}

However, the current spot rate is definitely not that. It is around ~1.332 currently.

Inconsistent naming for high and low limit prices

In orders, trades and transactions these are variously named "highLimit", "highPrice" and "highOrderLimit" and "lowLimit", "lowPrice" and "lowOrderLimit". Some consistency might be helpful to a developer.

Improper order url should return an error

This should return an error, but it does not

http://api-sandbox.oanda.com/v1/accounts/1179804/orders?instruments=EUR_USD&sdfsdf

Instead it returns this
{
"orders":[
]
}

please add 'id' field to v1/instruments

1 EUR/USD
2 EUR/GBP
3 EUR/JPY
4 EUR/CHF
5 USD/JPY
6 USD/CHF
7 USD/CAD
8 GBP/USD
9 GBP/JPY
10 GBP/CHF
11 AUD/USD
12 AUD/CZK
13 AUD/DKK
14 AUD/HKD
15 AUD/HUF
16 AUD/JPY
17 AUD/MXN
18 AUD/NOK
19 AUD/NZD
20 AUD/PLN

... and etc.

quoteHomeConversionFactors Deprecated

In V20 REST API, quoteHomeConversionFactors is an important figure for trader to decide how many unit to trade in their account currency. I hope this will not be deprecated.

source: http://developer.oanda.com/rest-live-v20/pricing-df/#Price

v1/accounts/:account_id/trades odd implementation

It is very odd to submit trade direction in a separate field like 'direction'. Please add support for signed units.

Transaction history needs time based retrieval

This may be an oversight but time based retrieval is supported by the website but not here. While minTransId and maxTransId are useful for pagination most operations on transaction history are based on time - today, yesterday, last week, this week, etc. The proposed implementation without minTime and maxTime requires a developer to maintain a local database of transaction history for typical analyses and is not much use for ad hoc queries.

Account creation returns a 502 Bad Gateway error

Creating a new account via
POST http://api-sandbox.oanda.com/v1/accounts

Returns a 502 Bad Gateway error.

Test using:
https://apigee.com/oandapoc/embed/console/oanda?req=%7B%22resource%22%3A%22accounts%22%2C%22params%22%3A%7B%22query%22%3A%7B%7D%2C%22template%22%3A%7B%7D%2C%22headers%22%3A%7B%7D%2C%22body%22%3A%7B%22attachmentParamName%22%3A%22file%20attachment%22%2C%22attachmentFormat%22%3A%22mime%22%2C%22attachmentContentDisposition%22%3A%22form-data%22%7D%7D%2C%22verb%22%3A%22post%22%7D

Also, the new method of creating an account does not allow the ability to set the currency The Account controller no longer has a Currency parameter as there was previously with:

-#### Request

• curl -X POST -d 'currency=AUD' http://api-sandbox.oanda.com/v1/users

Streaming rates missing

Streaming rates is one of the core functions.