OANDA's Trading Platform

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. API endpoint for trading hours

    At the moment there is no way to gather information on trading hours via the API.
    Trading hours are pieces of information of prime importance both from a functional perspective (they allow us to place orders successfully and possibly to prepare in time to do it) and as inputs for strategies (e.g. machine learning).
    It baffles me that there is no way whatsoever to gather this data from the API.
    Please implement endpoints for the trading hours for all instruments.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Pass order comment and tag extensions from API to MT4

    When a new order is submitted through an API with comment and tag client extensions, these values don't propagate to MT4, so the order is shown in MT4 with a blank comment and magic number. This is hugely inconvenient since there's no way attribute these orders by MT4's expert advisers to an external strategy.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Openssl v 1.1.1

    Your security tokens are no longer adequate for openssl version 1.1.1, which now insists on 2024 bit keys. This results in refused connection and the following error message:

    error trying to connect: error:141A318A:SSL routines:tlsprocessskedhe:dh key too small:../ssl/statem/statemclnt.c:2149:

    Paulo from technical support suggested using --ciphers 'DEFAULT:!DH' option to curl (or wget). While this works when constructing 'manually' these requests, it is not easy to use such switches from high level programming libraries, such as the Rust crates.

    I had a lot of trouble with this and finally solved it by using Rust's own implementation of TLS 'rustls-tls'…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  4. add spread

    We need instrument spread value information in the API. I need this vital information to place my trades.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add ClientExtentions to Account

    To have a way to store on the account level meta data relevant to all account trades

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  6. fix loading of charts takes way toooooo loooong

    charts take tooo long to load.. fix TCP response

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. API connection frequently aborted

    Need your assistance to resolve this issue
    Only one of many episodes described here ,
    1. Morning before 8.00am GMT quotes by REST_V20 perfectly updating them self's
    2. Exactly 8.00am GMT Every day I am getting exactly same File (File attached)
    3.Quotes simply Stopping (full stop) to update , Not updating anymore ,(getting Empty response from a Server )
    4.In Order to"Fix" above situation , Renew flow of Quotes required (must) Full Disconnect from
    a Server followed by Re Connect

    Please assist 
    

    Sincerely yours

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  8. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  9. Include MT4 ticket number to TRANSFER_FUNDS and DAILY_FINANCING transactions.

    Presently TRANSFERFUNDS and DAILYFINANCING transactions in API lack the ticket # from MT4. This complicates transaction matching between these platforms. Please implement this through a client extension field.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  10. TRUCKING

    MI SUERTE AHORA ME PERSIGUE

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Client ID

    The client ID assigned to an order does not survive when the order gets executed and turns into a trade, hence when interacting with the exchange via API you cannot refer to the trade with your custom ID unless this is manually re-assigned to the trade following order execution. Can you please rectify this in your next release?

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  12. Faster formation of candles

    When I query instrument candles after the closing time of the timeframe (eg 10:00:00:00001) the previous candle has not been formed. So at that time, the latest candle will be for 09:30:00 if timeframe is M30. Can the latest candle be available as soon as possible after it closes?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add volatility analysis data to the forexlabs Autochartist api response

    Volatility analysis data is not available via forexlabs autochartist API - and is crucial in determining correct stop loss.

    Could you please add this data - just like how you have added the "historicalstats" in the response.

    Thanks!

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  14. Show all trading opportunities via forexlabs Autochartist api

    Currently, Autochartist API via forexlabs v1 shows only those opportunities which are "Oanda's favorite". However, there are a ton more opportunities when manually looking through the Oanda Autochartist portal.

    Can you please provide all of those opportunities via the API - and let the developer choose which ones to ignore?

    Thanks!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  15. バーチャートの改善案

    スマホ版バーチャートの色分け版もチャート選択に入れて頂きたいです。

    オアンダのPC版のチャート内のバーチャートと同じものを2つの既存のバーチャートに追加して3つ目のバーチャートとして選択画面に追加お願いします。

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  16. Built-in indicators for API v20

    Implementing the possibility to fetch built-in and possibly even custom for API v20.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  17. API connection frequently aborted and reset by peer.

    API connection frequently aborted and reset by peer.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  18. Attach `comment` to TRANSFER_FUNDS transactions

    I may make transfers in and out of accounts for various reason and would like to make a comment on why I made a transfer. Since transfers show up in the pages of Transaction Details (along with Trades, Orders, etc), it seems that transactions of type "TRANSFER_FUNDS" would have their Client Extensions updated in the same way the accounts/{}/trades/{}/clientExtensions endpoint works. This way, even if i can't initiate transfers with the API, i can use my application to go back and tag/ID/comment on the transfers for my own bookkeeping.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  19. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  20. Expose the functionality of setting the default Stop Loss and Take Profit for an account via V20 REST API

    Expose the functionality of setting the default Stop Loss and Take Profit for an account via V20 REST API. This has become extremely critical for our business and lined up clients want this functionality and trade using Market Orders.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base