SabrTrader Documentation

Connecting an OANDA Forex Account to SabrTrader

This page documents how to connect SabrTrader to an OANDA forex account and load your first FX chart. OANDA is one of 57+ preconfigured broker and data-feed templates shipped with SabrTrader, and it is among the simplest to set up: a single REST/streaming API token authenticates both market data and account access, with no key-and-secret pair to manage. The instructions cover the Control Panel and Connections manager, generating the API token inside the OANDA Hub, saving the profile so credentials persist, and verifying the connection by creating a 15-minute USD/JPY chart with 21 days of history.

Overview: What This Page Covers

This page explains, end to end, how to create an authenticated OANDA connection inside SabrTrader and confirm it works by loading a live forex chart. OANDA is a retail forex and CFD broker; SabrTrader connects to it through OANDA's REST and streaming API using one personal API token.

Who this page is for: forex traders who already hold an OANDA live (funded) or demo (practice) account and want to chart, analyse and trade currency pairs inside SabrTrader instead of OANDA's own web or desktop platform.

Prerequisites

• An OANDA account that is already open and accessible — either a live account or a practice (demo) account. SabrTrader does not create broker accounts.
• SabrTrader installed and launched at least once, so the default workspace and default dxFeed connection exist.
• A working internet connection. All broker connections in SabrTrader are outbound network sessions to the broker's servers.
• The ability to log in to oanda.com in a browser to generate the API token.

Why FX connections are the simplest type

Broker integrations in SabrTrader fall into three broad credential patterns:

Credential pattern	What you supply	Typical providers
Single API token	One long secret string	OANDA and most retail FX brokers
API key + API secret	Two paired strings	Crypto exchanges and several data vendors
OAuth 2.0 browser login	App key, app secret and a callback URL, plus a browser consent step	Large equities brokers

OANDA uses the first pattern. There is no callback URL, no port number, no browser handshake and no client ID. You paste one token, save the profile, and connect. By contrast, a Schwab connection requires an OAuth callback flow and a Coinbase connection requires a key-and-secret pair.

What you get once connected

• Streaming bid/ask quotes for OANDA's tradable currency pairs, metals and CFD instruments.
• Historical bars for chart creation, requested in days of lookback.
• Account access for balances, positions and order routing, subject to your account type (live versus practice).
• The ability to bind charts, DOMs and panels in a order-flow layout to the OANDA connection.

How Connections Work in SabrTrader

A broker connection is an authenticated link between SabrTrader and a broker that supplies market data and, where supported, order routing plus account information. A market data feed is a real-time stream of quotes, trades and depth that SabrTrader consumes to build charts and order-flow tools; a data-only feed cannot place orders.

Preconfigured templates, user-supplied credentials

SabrTrader ships with 57+ preconfigured broker and data-feed templates. Each template already contains the provider's endpoints, symbol conventions, transport type and field requirements. The user never enters a server address or a port for OANDA — the only user-supplied values are a connection name and the API token. This design means adding a new broker is a credential-entry task, not a networking task.

Data-only feeds versus broker connections

Type	Market data	Order routing	Account balances/positions	Example
Data feed connection	Yes	No	No	dxFeed (default), Massive.com / Polygon.io
Broker connection	Yes	Yes	Yes	OANDA, Rithmic, Interactive Brokers

OANDA is a broker connection: it is both the data source and the execution route for the instruments it offers.

Multiple connections coexist

SabrTrader is a data-neutral, broker-neutral platform. Any number of connection profiles can exist in the Connections manager simultaneously, and each is connected or disconnected independently with its own Connect and Disconnect buttons. A trader can, for example, keep OANDA connected for spot FX while a futures feed supplies exchange-consolidated volume for currency futures. Each chart window is bound to one source connection, shown in the window's top-left connection label.

Profiles versus workspaces

• A profile is the saved file containing your connection definitions (including credentials), workspaces and platform settings, so they persist between sessions. It is written when you click Save Profile.
• A workspace is a saved arrangement of charts, DOMs and panels bound to specific connections. Workspaces are created, named, saved, closed, reopened and switched from the Workspaces menu.

The practical consequence: creating a connection changes the profile, arranging windows changes the workspace. Creating an OANDA connection and forgetting Save Profile means the connection is gone at next launch, even if the workspace survives.

The Default Workspace, dxFeed and the Control Panel

On first launch SabrTrader opens its default workspace: a preconfigured modular layout of charts and panels that is automatically connected to dxFeed, the market-data feed included out of the box so new users see prices immediately. dxFeed supplies prices only; it cannot route orders.

Every panel in the default workspace is dockable and movable. Windows can be dragged out, re-docked, resized, tabbed and closed freely. Nothing in the default layout is fixed, and nothing in it is required for the OANDA setup.

Static prices on the weekend are normal

Market hours / session close: forex trades nearly 24 hours a day, five days a week, from the Sunday evening open to the Friday evening close (broker-specific local times). Outside those hours quotes are frozen and charts show no new bars. Flat prices on a Saturday are a closed market, not a broken connection. The same applies to the dxFeed default workspace and to any OANDA chart you create.

Why close the default workspace before setting up

The default workspace subscribes to instruments and consumes screen space that is irrelevant to credential entry. Closing it produces a clean, uncluttered view and prevents you from later confusing a dxFeed-sourced chart with an OANDA-sourced chart.

1. Open the Workspaces menu at the bottom of the platform. New installations list only Default; experienced users see every workspace they have saved.
2. Choose the close action for the active workspace. Closing a workspace does not delete it — it can be reopened from the same menu.
3. Open the Control Panel, the primary SabrTrader window that hosts platform-wide functions: the Connections manager, workspace management and the launcher for new charts and panels.

With only the Control Panel on screen, every step that follows is unambiguous.

Control Panel and Connections Manager: Element Reference

The Connections manager is the tab of the Control Panel that lists SabrTrader's preconfigured broker and data-feed templates alongside your own saved connection profiles, and exposes the controls to create, edit, delete, connect and disconnect them.

Element-by-element

Element	Function	Notes
Connection list	Shows every provider template and every profile you have created, with its current connection state	A fresh installation shows the templates plus the default dxFeed profile; the screenshots on this page show many personal profiles because the presenter has several accounts
Category filters (Forex, Futures, Crypto, Stocks, All)	Narrows the provider list to one asset class	Filtering is a display-only action; it never disconnects or deletes anything. Leaving a filter applied is a common reason a provider "disappears"
Provider rows	One row per preconfigured broker or data feed, with the credential fields that provider requires	Fields are read-only (greyed out) while a template row is selected
Add (Add Below)	Creates a new editable connection instance from the selected provider template	This is the step users most often skip. Nothing can be typed until an instance exists
Edit	Reopens an existing profile's fields for modification	Use this to replace a rotated token instead of creating a duplicate profile
Delete	Removes the selected connection profile and its stored credentials	Disconnect first; then save the profile so the deletion persists
Name field	The human-readable label for the connection instance	Defaults to new. Rename it whenever you hold more than one account with the same broker
Credential fields	Provider-specific. For OANDA: a single API token field	Other providers show API key + API secret, or OAuth app key, app secret and callback URL
Connect / Disconnect	Opens or closes the authenticated session for one profile	Independent per profile; several profiles may be connected at once
Save Profile	Writes all connection definitions, credentials and layout state to disk	Mandatory after any change. Without it, everything entered is lost at exit
Connection status panel / indicator	Reports which profiles are currently connected	Also mirrored in the top-left label of every chart window

Filtering to Forex

Selecting the Forex category reduces the list to FX-capable brokers and feeds. OANDA appears in this group. The row shows that the only credential OANDA requires is the API token — useful confirmation before you visit the broker website to generate anything.

Trading Concepts You Need for FX Connections

Market and instrument concepts

• Forex (FX) is the decentralized over-the-counter market for trading currencies. There is no single central exchange; price is formed across banks, brokers and liquidity providers, which is why quotes can differ slightly between brokers.
• A currency pair is a quote of one currency against another, written BASE/QUOTE. In USD/JPY, USD is the base and JPY the quote, and the price states how many yen buy one US dollar. Buying the pair means buying the base and selling the quote.
• The bid/ask spread is the difference between the best bid (highest price a buyer will pay) and the best ask or offer (lowest price a seller will accept). In retail forex the spread is the primary trading cost, since many FX brokers charge no separate commission. Spreads widen at session rollovers, around economic releases and into the weekend close.
• Market hours / session close: FX runs approximately 24 hours, 5 days a week. Between the Friday close and the Sunday open no new ticks arrive and charts are static.

Credential and connectivity concepts

• A REST/streaming API token is a secret credential issued by a broker that authorizes an external application to access account data, historical data and streaming quotes. REST covers request-response calls such as "give me 21 days of 15-minute bars"; streaming covers the persistent push channel that delivers new ticks.
• An API key and secret are a two-part credential pair used by some brokers instead of a single token; the key identifies the application and the secret signs the request. OANDA does not use this pattern.
• An OAuth-style personal access token is a long-lived credential tied to a user account rather than a username-and-password login. The OANDA API token behaves this way: it does not expire on a schedule, but it can be revoked or regenerated at any time, which immediately invalidates the previous value.
• Demo versus live accounts: practice environments use separate credentials and separate API endpoints from funded accounts. A practice token cannot authenticate against the live environment, and vice versa.
• Rate limiting is a broker-imposed cap on how many API requests an application may issue per period, and how many concurrent streaming subscriptions it may hold. Exceeding it produces throttling, dropped subscriptions or temporary disconnects.

Data-quality concepts that matter for order flow

• Tick data versus aggregated bars: order-flow tools require trade-by-trade tick data including size and aggressor side. Plain candlestick charts only require aggregated OHLC bars. A feed that delivers only bars can never build a footprint.
• Order flow is the study of executed trades and resting liquidity to infer buying and selling pressure, rather than inferring it from price patterns alone.
• Delta is the net difference between volume traded at the ask (buy-aggressor) and volume traded at the bid (sell-aggressor) over a period. Positive delta means aggressive buying dominated.
• A footprint chart is a bar chart that splits traded volume by bid and ask at each individual price level inside the bar, used to read absorption and imbalance. See the Footprint Chart Indicator.
• A volume profile is a histogram of traded volume by price over a session or range, used to locate the point of control and value area. See the Volume Profile Indicator.
• A SuperDOM is a depth-of-market ladder that shows resting bid and ask liquidity at each price level and allows order entry directly from price. See Liquidity Heatmap & SuperDOM.
• Synthetic / tick volume in FX: because forex has no central exchange, there is no consolidated volume figure. "Volume" on an FX chart is either a count of price updates (tick volume) or the broker's own fill volume. It is a valid relative activity measure but is not comparable to exchange volume.

Layout and chart concepts

• A timeframe is the aggregation period of each chart bar, such as 15 minutes. Smaller intervals show more detail with more noise; larger intervals smooth price.
• Historical data lookback is the number of days of past data requested when a chart is created. Deeper lookback gives more context but increases load time, memory use and the chance of hitting a broker's history limit.

Generating an OANDA API Token

The API token is created on OANDA's own website, not in SabrTrader. SabrTrader never sees your OANDA password.

1. Open a browser and log in to your OANDA account at oanda.com.
2. After login you land on either the Trading page or the Hub. Both expose the API section. The Hub is the shortest path: open Hub and select OANDA API (sometimes labelled "Manage API Access").
3. On the API page, click Generate a new API key. The page returns a long alphanumeric token after a moment.
4. Copy the token immediately. Treat this string like a password.
5. If a token already exists, the page instead offers Revoke and Regenerate. Regenerating creates a new token and invalidates the old one.

Critical warnings

• Regeneration is destructive. Generating a new token invalidates every previously issued token on that environment. Any other application, script or platform using the old token will disconnect and must be updated.
• Demo and live tokens are separate. A token generated in the practice (fxTrade Practice) environment authenticates only against practice endpoints. A live token authenticates only against live endpoints. Confirm which environment you are logged into before generating.
• Never expose the token. Do not paste it into forums, support tickets, screenshots or screen recordings, and do not commit it to shared documents. Anyone holding a live token can read your account and, depending on permissions, act on it. If exposure is suspected, revoke and regenerate at once.
• Store it once, safely. OANDA may not display the full token again after you navigate away. Keep it in a password manager, not a plain text file on a shared drive.

Step-by-Step: Creating the OANDA Connection in SabrTrader

Follow these steps in order. Steps 1 and 2 are preparation; step 8 is the one most often forgotten.

1. Disconnect dxFeed (optional but recommended). Open the Control Panel, go to the Connections tab, select the dxFeed profile and click Disconnect. This guarantees that any chart you create afterwards is sourced from OANDA and not from the default feed. Disconnecting does not delete the dxFeed profile.
2. Close the default workspace. From the Workspaces menu, close the workspace that opened on launch, leaving only the Control Panel visible. This removes visual clutter and stops unrelated subscriptions.
3. Open the Connections manager. In the Control Panel, select the Connections tab. You will see the preconfigured provider templates plus any profiles you have already created.
4. Filter to Forex. Click the Forex category filter to reduce the list to FX-capable providers. Confirm the OANDA row states that only an API token is required.
5. Select the OANDA template row. The credential fields appear greyed out and read-only. This is expected: templates are not editable.
6. Click Add (Add Below). SabrTrader creates a new editable OANDA connection instance beneath the template. The fields are now writable.
7. Name the connection. The Name field defaults to new. Replace it with something descriptive such as OANDA-Live or OANDA-Demo. The name is what appears in the connection status panel and in the top-left source label of every chart bound to it.
8. Paste the API token. Click into the API token field and paste the value generated on the OANDA Hub. Paste, do not retype — manual transcription of a long random string is the single most common cause of authentication failure. Ensure there is no leading or trailing whitespace and no line break.
9. Click Save Profile. This writes the connection and its credential to your profile so it survives a restart. Anything created in the Connections manager and not saved must be re-entered next session.
10. Click Connect. The status indicator for the profile switches to connected. Authentication is immediate; there is no browser step and no confirmation dialog.
11. Verify only the intended connection is connected. Scan the connection status panel. The newly created OANDA profile should be the only one showing connected (unless you deliberately want others live). This eliminates ambiguity about which feed a new chart will use.

Repeat for a second account. To add a practice account alongside a live one, repeat steps 5 to 10 with the practice token and a distinct name such as OANDA-Demo. Do not overwrite the existing profile.

Verifying the Connection and Loading Your First Chart

A connected status only proves authentication succeeded. Loading a chart proves data flows.

1. From the Control Panel, open the instrument browser / symbol search.
2. Type the pair you want. For this walkthrough, search the Japanese yen and select USD/JPY. OANDA lists pairs in its own symbol format; use the browser's search rather than typing a symbol blind, so you subscribe to a symbol the connection actually recognises.
3. In the chart creation dialog, set the timeframe to 15 minutes.
4. Set the history length to 21 days. Twenty-one days of 15-minute bars is roughly three weeks of FX sessions — enough context for intraday structure without a heavy request.
5. Click Create chart. Bars load from the broker's historical endpoint, then live ticks begin appending to the rightmost bar during market hours.

The connection/source label on the chart window

Each chart window carries a label at its top-left showing which connection the window is bound to and which instrument is loaded. Clicking it reveals the available instruments on that connection. Use this label whenever you are unsure whether a chart is fed by OANDA, dxFeed or another provider — it is the definitive answer, more reliable than memory.

Confirming live data

• Verify during market hours. Between the Friday close and Sunday open the chart will load history correctly but the last bar will not move.
• Check that the bid/ask spread updates. In FX the quote is a two-sided spread; a moving spread is direct evidence of a live streaming subscription.
• Compare the last price against OANDA's own web platform. Small differences are normal (bid versus mid versus ask), large differences suggest you are looking at a different source.

Building a dedicated FX workspace

Once the chart is confirmed, arrange the windows you want, then save the layout as a new workspace (for example FX-Majors) rather than modifying the default workspace. This keeps a clean fallback layout and lets you switch between FX, futures and crypto layouts from the Workspaces menu.

Using OANDA Data with SabrTrader Order-Flow Tools

Once OANDA is connected, its instruments can be loaded into the same tools as any other feed.

Tool	Works with OANDA FX?	Data requirement	Interpretation caveat
Candlestick / bar charts	Yes	Aggregated OHLC bars	None
Volume profile	Yes	Volume by price	Volume is tick/broker-side, so profile shape is meaningful, absolute volume is not
Footprint	Yes	Trade-by-trade tick data with aggressor side	Aggressor classification is derived from the broker's own fills or tick direction, not exchange-consolidated prints
Delta	Yes	Bid/ask-classified volume	Read as a relative pressure oscillator, not an absolute contract count
SuperDOM / liquidity heatmap	Partially	Level 2 depth	Retail FX depth reflects one broker's liquidity pool, not the whole market
Price-action and structure tools	Yes	OHLC bars only	None — see Market Structure and TDU Price Action

Why FX volume must be interpreted relatively

Forex is decentralized. No entity aggregates every FX transaction, so no broker can report true market volume. What a platform displays is one of two proxies:

• Tick volume — a count of price updates in the period. It correlates well with activity because busy markets update more often.
• Broker-side fill volume — the volume actually transacted through that broker. Representative of that broker's flow only.

Both are legitimate for comparing one bar to another on the same feed. Neither should be compared across brokers, nor treated as institutional participation.

When you need true exchange volume

If your method depends on genuine consolidated volume, delta and depth, use currency futures instead of or alongside spot FX: 6E (Euro FX futures), 6J (Japanese yen futures), 6B (British pound futures) all trade on CME with fully reported exchange volume. Those require a futures feed such as Rithmic or Interactive Brokers. A common professional configuration is: OANDA connected for spot execution and spread-sensitive entries, a futures feed connected for order-flow analysis on the correlated contract, both live at the same time in one workspace.

Best Practices

1. Use descriptive connection names. OANDA-Live and OANDA-Demo are unambiguous; two profiles both called new are a trading accident waiting to happen. The name appears in the chart source label, so it is your safeguard against sending an order to the wrong account.
2. Click Save Profile after every change. After adding a connection, renaming it, replacing a token or deleting a profile. Saving is cheap; re-entering credentials is not.
3. Test with a practice token first. Create the connection with a demo token, confirm charts load and orders behave as expected, then add the live profile. This separates "is my setup correct" from "is my strategy correct".
4. Keep only the connections you need connected. Each live connection consumes bandwidth and counts against the provider's subscription and rate limits. Disconnect idle feeds.
5. Back up your profile. Copy the saved profile file to secure storage after a major setup session so a reinstall or disk failure does not cost you every credential and layout. Because the profile contains secrets, store the backup encrypted.
6. Rotate tokens periodically. Regenerate the OANDA token on a schedule and after any suspected exposure. Immediately afterwards, edit the SabrTrader profile with the new value and re-save.
7. Build a dedicated FX workspace. Leave the default workspace intact as a known-good reference layout and create your own named workspaces for FX, futures and crypto.
8. Record which token belongs to which environment. Note in your password manager whether each token is practice or live. Tokens are opaque strings and cannot be told apart by inspection.
9. Verify during an active session. Do your first-time setup validation while London or New York is open, so the absence of movement genuinely means a fault.
10. Pair FX with futures when analysing order flow. Use OANDA for execution and a futures feed for exchange-verified volume rather than over-trusting synthetic FX volume.

Common Mistakes

Mistake	What happens	Correct action
Trying to type credentials into the template row	Fields are greyed out and refuse input; users conclude the platform is broken	Select the provider, then click Add to create an editable instance first
Forgetting Save Profile	The connection works this session and is gone after restart	Save immediately after entering the token, before clicking Connect
Pasting a token with trailing whitespace or a line break	Authentication fails with no obvious cause because the string looks correct	Re-copy the token, paste into the field, and delete any stray space at either end
Using a demo token against the live environment (or the reverse)	Authentication error, or connection succeeds but no accounts/instruments appear	Generate the token from the environment you intend to trade and label the profile accordingly
Mistaking weekend flat prices for a dead feed	Hours spent regenerating tokens that were never the problem	Check the clock and the FX session calendar before troubleshooting
Expecting exchange volume on FX pairs	Delta and volume-profile readings are misinterpreted as institutional size	Read FX volume relatively; use 6E/6J futures for consolidated volume
Leaving dxFeed connected and then creating a chart	The chart binds to the wrong source; symbols, spreads and history differ from OANDA	Disconnect unused feeds, and always check the chart window's top-left source label
Creating a duplicate profile instead of editing the existing one	Multiple OANDA entries with stale tokens, unclear which one a chart uses	Select the existing profile and use Edit to update the token
Regenerating the OANDA token to "fix" something	Every other application using the previous token disconnects	Regenerate only deliberately, then update all consumers of the token
Requesting excessive history on a fine timeframe	Chart loads slowly, partially, or empty because the request exceeds broker limits	Start with a modest lookback such as 21 days on 15-minute bars and increase gradually
Editing the default workspace instead of creating a new one	No clean layout to fall back on when something breaks	Save a new named workspace for your FX setup

Frequently Asked Questions

What credentials does SabrTrader need for OANDA?

One value: your OANDA REST/streaming API token. OANDA does not use an API key and secret pair, and there is no OAuth callback URL, port number or client ID to configure. In the Connections manager you supply a connection Name (free text, for your own identification) and paste the token into the API token field. Everything else — endpoints, symbol conventions and transport — is already contained in SabrTrader's preconfigured OANDA template.

Where do I generate an OANDA API token?

On OANDA's own website. Log in to your OANDA account, then open the Hub and select OANDA API; the same section is also reachable from the Trading page. Click Generate a new API key, wait a moment for the token to appear, and copy it immediately. If a token already exists, the page offers Revoke and Regenerate instead. Store the token in a password manager, because OANDA may not display it in full again after you leave the page.

Can I use an OANDA demo (practice) account with SabrTrader?

Yes. Practice accounts are fully supported and are the recommended way to validate your setup. Practice and live environments use separate credentials and separate API endpoints, so you must generate the token while logged into the practice environment and it will only authenticate there. Create a distinct profile named OANDA-Demo so it can never be confused with a live profile. You can keep both a demo and a live OANDA profile in the Connections manager and connect either one independently.

Why are my connection settings gone after restarting SabrTrader?

Because the profile was not saved. In SabrTrader, connection definitions and credentials live in the profile, which is written only when you click Save Profile in the Connections manager. Creating a connection and clicking Connect makes it work for the current session but does not persist it. Re-create the connection, paste the token, click Save Profile, then Connect. Save again after any later edit, rename or deletion.

Can I connect OANDA and another broker or data feed at the same time?

Yes. SabrTrader is data-neutral and broker-neutral: every connection profile has its own Connect and Disconnect controls and they operate independently. A common configuration is OANDA connected for spot FX charting and execution while a futures feed such as Rithmic or Interactive Brokers supplies exchange-consolidated volume on currency futures. Each chart window is bound to a single connection, shown in its top-left source label.

Do I have to disconnect DXfeed before connecting OANDA?

No, it is not technically required — dxFeed and OANDA can be connected simultaneously. It is recommended during setup for clarity: with dxFeed disconnected, any chart you create is unambiguously sourced from OANDA, and you cannot accidentally analyse dxFeed data while believing it is broker data. dxFeed is the delayed, price-only feed SabrTrader ships with so new users see data immediately; it cannot route orders.

Why is price not moving on my OANDA chart?

Three causes, in order of likelihood. First, the market is closed: forex trades roughly 24 hours a day, 5 days a week, and quotes are frozen between the Friday close and the Sunday open. Second, the symbol is not subscribed — reload the instrument from the browser and confirm the chart's source label shows the OANDA profile. Third, the connection dropped: check the connection status panel in the Control Panel and reconnect. A chart that loaded history correctly but shows no new ticks almost always indicates a closed session, not a credential problem.

Does SabrTrader show real volume and delta on forex pairs?

It shows volume and delta, but not exchange-consolidated volume, because forex is a decentralized over-the-counter market with no central exchange to report it. What you see is either tick volume (a count of price updates) or the broker's own fill volume. Both are valid for comparing activity between bars on the same feed and for shaping a volume profile or reading a footprint, but neither is an absolute measure of market participation. If you need true reported volume, trade or analyse currency futures such as 6E or 6J through a futures feed.

How many days of historical FX data can I load on a chart?

The ceiling is set by the broker's historical data limits and interacts with the timeframe: fine intervals return fewer days than coarse ones. The demonstrated configuration — 15-minute bars with 21 days of lookback — loads reliably. If a chart comes up empty or partially populated, reduce the number of days or increase the bar interval and try again. Deeper lookback also increases load time and memory use, so request only the context your method actually needs.

Can I place orders on OANDA from SabrTrader charts and the SuperDOM?

Yes. OANDA is a broker connection, not a data-only feed, so an authenticated token gives SabrTrader access to account balances, positions and order routing in addition to market data. Orders can be placed from the chart's order-entry panel and from the SuperDOM ladder. Two caveats: a practice token routes to the practice environment only, and a live account must be funded before live orders are accepted even though authentication succeeds.

What happens if I regenerate my OANDA API token?

The previous token is invalidated immediately. Every application holding the old value — SabrTrader, any script, any other platform — will fail to authenticate and disconnect. After regenerating, open the Connections manager, select the OANDA profile, click Edit, paste the new token, click Save Profile, then Connect. Only regenerate deliberately: as a security rotation, or because the token may have been exposed. Regenerating is not a fix for a closed market or an unsaved profile.

How do I rename or delete an OANDA connection?

Select the profile in the Connections manager and click Edit to change the Name field, or click Delete to remove the profile and its stored credential. Disconnect the profile before deleting it. In both cases click Save Profile afterwards, otherwise the rename or deletion is reverted at the next launch. Renaming does not affect the token or your OANDA account in any way.

What is the difference between a workspace and a profile in SabrTrader?

A workspace is a saved arrangement of charts, DOMs and panels bound to specific connections; workspaces are created, named, closed, reopened and switched from the Workspaces menu. A profile is the saved file that holds your connection definitions and credentials, your workspaces and your platform settings, so everything persists between sessions. Closing a workspace never affects your connections; failing to save the profile loses them.

Why are the credential fields greyed out when I click OANDA?

Because you have selected the preconfigured provider template, which is read-only by design. Templates define how to talk to a provider; they never store your secrets. Click Add (Add Below) to create a new editable connection instance from that template. The new instance appears with a Name field defaulting to new and a writable API token field.

Do I need a separate market data subscription for OANDA?

No. Retail forex brokers including OANDA supply quotes for their tradable instruments as part of the account; there are no exchange market-data fees to purchase because there is no exchange involved. This differs from equities and futures, where real-time data requires an exchange entitlement. What OANDA does impose is API rate limiting — caps on request frequency and concurrent streaming subscriptions.

Which currency pairs and instruments are available on the OANDA connection?

Whatever your OANDA account is entitled to trade: major, minor and exotic currency pairs, precious metals such as XAU/USD, and depending on jurisdiction, index and commodity CFDs. The definitive list is the instrument browser on the connected OANDA profile — click the source label at the top-left of a chart window to see the instruments available on that connection. Always resolve symbols through the browser rather than typing a ticker, because each provider uses its own symbol format.

Is my API token stored securely by SabrTrader?

The token is stored locally in your SabrTrader profile on your own computer and is transmitted only to OANDA when the connection authenticates. Treat the profile file as sensitive: encrypt any backups, do not share the file, and do not display the token on screen recordings. If a machine holding the profile is lost or compromised, revoke and regenerate the token in the OANDA Hub immediately.

Troubleshooting

Authentication error when clicking Connect

The token is wrong, revoked or belongs to the other environment. Work through this list in order:

• Re-copy the token from the OANDA Hub and paste it again — do not retype.
• Check for leading or trailing whitespace, or a line break captured with the paste.
• Confirm the environment matches: a practice token cannot authenticate a live connection, and a live token cannot authenticate a practice one.
• Confirm the token has not been revoked or superseded by a later regeneration.
• If in doubt, regenerate the token in the OANDA Hub, then Edit the SabrTrader profile, paste the new value and Save Profile.

Connection shows connected but no instruments appear

Two usual causes. First, a category filter is still applied in the Connections manager or instrument browser, hiding results — clear the filter or switch to All. Second, the token authenticates against an environment with no accessible trading account (for example a live token on an account with no sub-account provisioned). Verify in the OANDA web platform that the account is active and, for live trading, funded. Then disconnect and reconnect the profile in SabrTrader.

Price is frozen and no new bars form

Check the day and time first. Forex trades approximately 24 hours a day, 5 days a week; between the Friday evening close and the Sunday evening open quotes are static and this is normal, not a fault. If the market is open: confirm the chart's top-left source label points at the OANDA profile and not at dxFeed or another feed; re-select the symbol from the instrument browser to re-subscribe; and check the connection status panel for a silent disconnect.

Chart is created but comes up empty or with missing history

The historical request exceeded what the broker will serve for that timeframe. Reduce the lookback (for example from 90 days to 21 days), or increase the bar interval (from 1 minute to 15 minutes), and create the chart again. Also confirm the instrument was resolved through the symbol browser rather than typed, since an unrecognised symbol returns no bars on an otherwise healthy connection.

Connection drops repeatedly after a few minutes

Likely causes, in order:

• Network instability — test general connectivity and any VPN or firewall that may be interrupting the persistent streaming session.
• Rate limiting — you may be exceeding OANDA's cap on requests per period or concurrent streaming subscriptions. Close unused charts and reduce the number of subscribed instruments.
• Token shared across applications — the same token used simultaneously by other platforms or scripts can trigger session conflicts. Generate a dedicated token for SabrTrader where possible.
• Too many connections live at once — disconnect feeds you are not using.

All my settings disappeared after restarting SabrTrader

The profile was never saved. Re-create the connection: select OANDA, click Add, name it, paste the token, then click Save Profile before doing anything else. Make saving the profile a reflex after every change in the Connections manager, including renames and deletions. Once saved, copy the profile file to secure encrypted storage as a backup.

I cannot type into the Name or API token fields

You have a preconfigured provider template selected, and templates are read-only. Click Add (Add Below) with OANDA selected. SabrTrader creates a new editable connection instance whose Name defaults to new and whose API token field accepts input. If you intended to modify an existing profile instead, select that profile and click Edit.

My chart shows different prices than the OANDA web platform

First check the chart's source label — if it says dxFeed or another provider, the chart is not bound to OANDA at all. Disconnect the unwanted feed, then re-create the chart from the OANDA connection. If the source is correct, small differences are expected: charts may be built from bid, ask or mid prices, and the bid/ask spread widens around news and the session rollover. Large persistent differences indicate a wrong source or a stale, disconnected subscription.

Volume and delta look implausibly small or inconsistent across brokers

This is expected behaviour in forex, not a data fault. Because FX is decentralized, the displayed volume is tick volume or the broker's own fill volume rather than exchange-consolidated volume, so magnitudes differ between providers. Interpret FX volume and footprint readings relatively within one feed. For absolute, reported volume use CME currency futures (6E, 6J, 6B) via a futures connection.

Orders are rejected even though the connection is authenticated

Authentication and trading permission are separate. Confirm the profile is pointed at the intended environment (a practice token can only trade the practice account), that a live account is funded, that the instrument is one your jurisdiction permits, and that position size respects the broker's minimum and maximum. Check the platform's order log or message panel for the broker's rejection reason, which is more specific than a generic failure notice.

Two OANDA entries both named 'new' and I cannot tell them apart

Select each in turn, click Edit and rename them to something descriptive such as OANDA-Live and OANDA-Demo, then Save Profile. If one is a duplicate created by mistake, disconnect it, click Delete and save again. Descriptive names matter because the profile name is what appears in each chart's source label and therefore identifies which account an order will reach.

Glossary

API key and secret

A two-part credential pair used by some brokers instead of a single token: the key identifies the application and the secret signs or authorizes the request.

Bid/ask spread

The difference between the best bid (highest price a buyer will pay) and the best ask (lowest price a seller will accept). In retail forex it is the primary trading cost, since many FX brokers charge no separate commission.

Broker connection

An authenticated link between SabrTrader and a broker that supplies market data and order routing, plus account balances and positions.

Connection profile

A saved set of credentials and settings for one broker or data feed, created from a preconfigured template, so the connection can be re-established with a single click.

Connections manager

The Control Panel area containing SabrTrader's 57+ preconfigured broker and data-feed templates, the user's saved connection profiles, and the Add, Edit, Delete, Connect, Disconnect and Save Profile controls plus the connection status panel.

Control Panel

The primary SabrTrader window hosting platform-wide functions: the Connections manager, workspace management and the launcher for new charts and panels.

Currency pair

A quote of one currency against another, written BASE/QUOTE, where price expresses how much quote currency buys one unit of base currency.

Delta

The net difference between volume traded at the ask (buy-aggressor) and volume traded at the bid (sell-aggressor) over a given period.

Demo vs live account

Practice environments use separate credentials and separate API endpoints from funded trading accounts. A practice token cannot authenticate against the live environment and vice versa.

dxFeed

The market-data feed SabrTrader is connected to out of the box, providing delayed prices across supported markets so new users see data immediately. It supplies prices only and cannot route orders.

Footprint chart

A chart type that displays traded volume split by buy and sell aggressor at each individual price level within each bar, used to read absorption, imbalance and delta. It requires trade-by-trade tick data.

Forex (FX)

The decentralized over-the-counter market for trading currencies. There is no central exchange, so price and volume are formed across banks, brokers and liquidity providers.

Historical data lookback

The number of days of past data requested when a chart is created. Greater depth gives more context but increases load time, memory use and the risk of exceeding broker history limits.

Market data feed

A real-time or delayed stream of quotes, trades and depth that a platform consumes to build charts and order-flow tools. A data-only feed cannot route orders.

Market hours / session close

Forex trades approximately 24 hours a day, 5 days a week. Between the Friday evening close and the Sunday evening open no new ticks arrive, so quotes and charts are static.

Modular window layout

SabrTrader's design principle that panels can be moved, docked, resized and closed freely so each trader can build a personal layout.

OAuth-style personal access token

A long-lived credential tied to a user account rather than a username-and-password login. It does not expire on a fixed schedule but can be revoked or regenerated, which immediately invalidates the prior value.

Order flow

The study of executed trades and resting liquidity to infer buying and selling pressure, rather than inferring it from price patterns alone.

Profile

The saved file containing your connection definitions and credentials, workspaces and platform settings, so they persist between sessions. It is written when you click Save Profile.

Rate limiting

Broker-imposed caps on how many API requests an application may make per period and how many concurrent streaming subscriptions it may hold. Exceeding the cap causes throttling, dropped subscriptions or disconnects.

REST/streaming API token

A secret credential issued by a broker that authorizes an external application to access account and market data. REST covers request-response calls such as historical bars; streaming covers the persistent push channel of live ticks.

Save Profile

The Connections manager control that writes all connection definitions, credentials and layout state to the profile file on disk so they survive a restart.

SuperDOM

A depth-of-market ladder that displays resting bid and ask liquidity at each price level and allows orders to be placed, modified and cancelled directly from price.

Synthetic/tick volume in FX

Because forex has no central exchange, the volume displayed on an FX chart is a count of price updates (tick volume) or the broker's own fill volume rather than true consolidated market volume.

Tick data vs aggregated bars

Tick data is the individual trade-by-trade stream including size and aggressor side; aggregated bars are pre-summarised OHLC values. Order-flow tools require tick data, plain candles do not.

Timeframe

The aggregation period of each chart bar, such as 15 minutes. Smaller intervals reveal more detail with more noise; larger intervals smooth price at the cost of granularity.

Volume profile

A histogram of volume traded at each price over a chosen session or range, used to locate high-activity price areas such as the point of control and value area.

Workspace

A saved SabrTrader layout containing charts, DOMs and panels bound to specific connections. Workspaces can be created, named, saved, closed, reopened and switched.

Related Documentation