Simple background trading bot for Oanda account (v20 REST API)

Title:

Simple background trading bot for my Oanda account (v20 REST API)

Overview

Hi, I need a simple, lightweight event based standalone trading bot that connects directly to my Oanda account using broker’s standard REST API (V20 account) via VPS

The bot just needs to look at group of 5 currency pairs (manually selectable and adjustable) in different 4 baskets, do some basic percentage math every period, and place trades based on a defined trigger. Each basket has manually selectable Ture/False toggle in background file (such as in plain English of Config.imi etc) No change in the coding. No interface is required.

It will run in the background on a small VPS Windows server alongside another script, so the code needs to be highly efficient and use very little memory. You can use whatever programming language you are fastest and most efficient with (like Python, C#, C++, etc.), as long as it runs light.

1. The Math & Rules (with on/off selectable toggle in ANY number of Seconds or Minutes (Own time frame) 

**Flip Prices:** For directionally inverted pairs (like USD/CAD), just flip the price math (1 / Price) so it aligns with the other pairs in the group. Example; (EUR_USD GBP_USD AUD_USD NZD_USD USD_CAD > CAD_USD)

**Find the Center (Median) :** For each group of 5 pairs, calculate individual Periodic percentage move (Current Price - Start Price / Start Price) x 100, sort them percentages from lowest to highest, and pick the middle one (the 3rd pair) as the center anchor (Median)

**The Trigger Rule:** Individual% - Median /SD 

For the numerator, subtract that center anchor (Median) from individual pair's percentage move to get the current residual gap value. (explained in the attached excel sheet as well) 

For the denominator, calculate the standard deviation of that same residual gap calculation in numerator over the past 100 historical periods (rollover of same calculated values)(NOT RAW data)

Divide the individual current residual by this historical residual standard deviation (over 100 periods) to get the final Z-score.

If the result is greater than >2.0 or <2.0, it triggers a trade. 

BUT……… it must validate following sub conditions: 

**The Condition of Number of Pairs that Define Silence Filter:** 

Toggle: Market Volatility Filter: True/False 

(three conditions)

If Leader SD>2 or SD<2 (SD values manually adjustable)

If Follower pairs SD<0.5 or SD>0.5 (SD values manually adjustable) 

IF This NUMBERS of followers SD move in same direction (2,3,4)(manually adjustable) 

Consider RAW data to calculate SD in an individual currency’s co-movement test of Half % in SD that decides Silence in Volatility or otherwise. 

Further explanation of Silence Filter: (To protect against a dead market (or just because of violent spike in One instrument) check link to individual volatility of remaining pairs against their averages. If at least 1 or 2 or 3 or 4 out of the 5 pairs are not moving more than half (0.5x) of their standard historical speed (in the same direction), the bot must instantly declare the group as Silent. The bot will freeze that basket and skip the cycle, ignoring fake signals on background noise. This  SD will be based on RAW data of past 100 selected periods) (deque))

## 2. Keeping the Server Safe & Light

* **Low Memory:** The bot must run quietly in the background as a simple standalone task. Do not use heavy databases or heavy charting platforms (like MetaTrader MT4/MT5), as my VPS server has very tight memory limits. Just use tiny, fast local arrays in RAM to hold the last 100 prices.

* **Timer Delays:** Don't check all currency groups at the exact same millisecond. Space them out by 2 seconds each so the server's CPU stays near 0%.

* **Auto-Reconnect:** If the internet drops for a few seconds, the bot must automatically pause, wait a bit, and reconnect itself safely without freezing up or dying silently.

---

## 3. Safe Trade Execution

* ** True/False: Limit Orders:** To protect account from bad slippage or wide spreads during news, the bot may use Limit Orders set slightly below the price (like -0.1 or -0.2 pips) (pips selection are manually adjustable)

* **15-Second Delete:** If a limit order doesn't get filled within 15 seconds, the bot must automatically cancel it so we don't leave old, stale trades hanging open.

**Timer Reset:** The Periodic countdown (whatever the time frame is selected) resets completely to zero at the start of every new block of time.

* **No Opposite Trades:** If the bot already has a buy trade open on a pair, block it from opening a sell trade on that same pair at the same time (the account runs on Netting Not Hedging) 

* **Manual Close Pause:** If I manually close a trade on my phone app, the bot must notice it, pause for 1 minute, and reset its timer before looking at that group again.

## 4. Settings File & Daily Logs

* **Settings Text File:** All settings (like risk %, max trades, trade hours, and max spread filter) must be written in a simple configuration text file so I can easily change them on my notepad without touching the main code. 

* **Daily Spreadsheet Logs:** The bot must save all its calculations and trade outcomes into a daily CSV spreadsheet file so I can review them at the end of the day.

## Project Terms & Delivery 

* **VPS Deployment:** Once the code is ready, the developer connect it to Windows VPS for deploying/installing the bot so that it runs successfully in the live background.

* **Testing Phase:** Developer can open its own demo account in Oanda to test it at their side. 

* **Warranty:** The developer provide a full 2-week post-delivery warranty. If any bugs, calculation lag, or stream reconnection errors occur during the first 14 days of running live, the developer fix them for free.