Quick Answer
OANDA does not publish a simple group-wide statement that all high-frequency trading (HFT) is permitted. The OANDA Corporation API License Agreement allows automated trading systems for issuing transactions, while also defining unauthorized activity to include arbitrage, scalping, pip-hunting and certain immediate cross-market resales intended to profit from a price discrepancy or price error. The developer API also has documented rate and streaming limits. Whether a particular strategy is allowed depends on the exact entity, account and current agreement; obtain written clarification from the company serving your account.
Source: OANDA Corporation API License Agreement (August 2026) · Last Checked:
What OANDA Says About Automated Trading
The OANDA Corporation API License Agreement describes the OANDA Trading System API as supporting custom interfaces, access to rates and account information, and creation of automated trading systems for issuing transactions to the OANDA Trading System or its practice environment. This is evidence that API-based automation is contemplated under that agreement, not that every algorithm or execution style is authorized.
The same agreement defines “Unauthorized Activity” to include money laundering, arbitrage, scalping or pip-hunting, as well as other activity involving purchase on one market and immediate resale on another to profit from a price discrepancy or price error. Read the complete current agreement and the customer agreement for the correct account entity. A permission in one OANDA company’s contract should not be generalized to another group company.
Source: OANDA Corporation API License Agreement · Last Checked:
OANDA API Access and Documented Limits
The OANDA REST v20 developer guide documents limits of 120 REST requests per second, 20 active streaming connections, and no more than two new connections per second, applied against the requesting IP address. Excess REST requests may receive HTTP 429; excess stream requests and connections are rejected. These are technical API limits, not an approval of a trading strategy.
The pricing-stream endpoint says it provides at most four prices per second for each requested instrument, at 250-millisecond windows, and may omit intermediate prices created within a window. Different stream connections may observe different prices during rapid movement. This is not a full tick-by-tick feed and should not be described as institutional low-latency market data.
| REST requests | 120 requests per second per requesting IP; excess requests can receive HTTP 429. |
|---|---|
| Active streaming connections | 20 active streams per requesting IP. |
| New connections | No more than 2 new connections per second. |
| Prices per instrument | At most 4 prices per second (every 250 ms) on the documented pricing stream; intermediate prices may be omitted. |
Source: OANDA developer guide — rate and connection limits · Last Checked:
Source: OANDA pricing endpoint — price-stream behavior · Last Checked:
Expert Advisors and Automated Strategies
OANDA’s Australia REST API page describes programmatic access to pricing and execution and says users can build and test custom algorithmic strategies. That provider page applies to its Australian service context and does not replace the account agreement or API terms for a different region.
Using an Expert Advisor, script or API to automate ordinary strategy decisions is not automatically the same as high-frequency trading. The relevant questions include what the algorithm does, how frequently it sends requests, whether it relies on latency or pricing errors, and whether the applicable agreement restricts that behavior. Get the current answer from the entity that holds your account.
Source: OANDA Australia — REST API platform page · Last Checked:
What Counts as HFT?
High-frequency trading has no single universal customer-facing definition across all brokers. It is often used to describe strategies that submit, modify or cancel orders rapidly and seek to exploit very short-lived price changes. Institutional HFT may depend on specialized infrastructure and data; retail algorithmic trading can be automated without meeting that description.
The label alone does not determine whether an activity is permitted. OANDA’s agreement uses specific terms such as arbitrage, scalping and pip-hunting; readers should compare the strategy’s actual behavior with the contract language rather than assume that every short holding period is prohibited or that every automated system is approved.
Prohibited Activity, Execution and Account Restrictions
The agreement’s unauthorized-activity definition focuses on specified practices, including activity seeking to profit from price discrepancies or errors. This page does not expand that language into a broader ban or offer a legal interpretation of what counts as scalping in a particular case. OANDA’s complete API agreement and customer terms control.
API request caps, price-stream behavior, execution policies and account terms should be considered together. A platform rate limit does not guarantee fill speed, prevent slippage or establish a safe order cadence. Do not attempt to circumvent rate limits or account controls; repeated excess requests may be rejected and can disrupt the connection.
Before automating, verify account eligibility, API permission, order types, rate limits, data handling, disconnection behavior, margin controls and the procedure for stopping the system. Ask OANDA to confirm the proposed strategy in writing if its classification is unclear.
Questions to Check Before Automating OANDA
- Which OANDA legal entity is named in my customer agreement and API license?
- Does that entity permit my specific automated strategy and holding pattern?
- Do the agreement’s definitions of arbitrage, scalping or pip-hunting apply to the strategy?
- What are the current REST, streaming, connection and order limits for my API access?
- How are rejects, partial fills, stale prices and disconnected sessions handled?
- What controls stop new orders, and how are open positions managed if automation pauses?
- Are the data, products and account permissions suitable for this use under local rules?
Sources and Research Scope
OANDA’s official API agreement, developer guide and pricing endpoint were reviewed on 20 October 2026. The agreement is for OANDA Corporation and is not presented as the contract for every OANDA company. Regional platform pages are attributed to their named service context. No trading account, high-speed strategy or live order was tested.
Source: OANDA Corporation API License Agreement · Last Checked:
Source: OANDA v20 REST API development guide · Last Checked:
Source: OANDA v20 pricing endpoint · Last Checked:
Source: OANDA Australia REST API page · Last Checked:
FAQ
OANDA does not provide a single group-wide HFT permission. Its API agreement permits automated systems for defined purposes but identifies certain activity, including arbitrage, scalping and pip-hunting, as unauthorized. The exact account entity and current contract matter.