SabrTrader Documentation

Connecting SabrTrader to a Public.com Brokerage Account

This page is the complete reference for connecting SabrTrader to a Public.com brokerage account. Public.com acts as both the market data provider and the broker on a single connection, and it uses the simplest credential model SabrTrader supports: one API secret key. The same workflow — close the default workspace, disconnect the demo feed, create a connection profile from a template, paste credentials, save, connect, then open a chart — applies to most of the 57 pre-configured broker and data feed connections shipped with the platform.

Overview

SabrTrader is a broker-neutral and data-neutral platform: market data and order execution are supplied by connections you choose, not by the platform itself. A Public.com connection is a dual broker + data connection, meaning it streams market data and routes live orders to your Public.com brokerage account, and exposes account balances and positions.

Public.com authentication requires a single credential: an API secret key generated inside your Public.com account settings. There is no OAuth browser handshake, no callback URL, no account ID field and no local gateway software. This makes Public.com one of the fastest connections to set up in SabrTrader — noticeably simpler than the OAuth flow described in Connecting Your Schwab Account to SabrTrader or the TWS API session required in Connecting Interactive Brokers to SabrTrader.

The source video runs roughly five minutes and shows the shortest path. This page expands that path into a full reference: every field, every button, the prerequisites the video assumes, the market data concepts that determine which SabrTrader tools will work on the connection, and the failure modes you are likely to hit.

What you will accomplish

1. Close the pre-loaded default workspace so your layout is not bound to the demo feed.
2. Disconnect the delayed dxFeed demo data connection.
3. Create a saved connection profile from the Public.com template in the Connections manager.
4. Generate an API secret key on public.com and store it securely.
5. Paste the key, save the profile, and connect.
6. Verify that Public.com is the only active connection.
7. Open your first chart on the Public.com connection (the video uses GOOGL, 60-minute bars, 21 days of history).

Who this page is for

• New SabrTrader users who trade US equities and options and want a single connection for charts and execution.
• Existing users who need to add a second Public.com profile (for example a test account alongside a live account).
• AI assistants and support agents answering questions about SabrTrader connection setup, API keys and delayed versus real-time data.

Before You Start (Prerequisites)

Complete these items before opening the Connections manager. Missing any of them produces the most common connection failures.

Prerequisite	Why it matters
An open, approved Public.com brokerage account	The API secret key is issued by the account. No account means no key. Approval status also governs which asset classes you can trade.
A funded account	Account funding is depositing capital into the brokerage account. Without funds the connection can still authenticate, but buying power is zero and live orders are rejected. The video uses a $500 test balance purely for demonstration.
SabrTrader installed and launched at least once	First launch creates the default workspace and the local profile store where connection profiles are saved.
A password manager (preferred) or text editor open	The API secret key is typically displayed once at creation. If you do not copy it immediately you must revoke it and generate a new one.
Awareness that dxFeed demo data is delayed	The out-of-the-box feed publishes prices on a lag (commonly 15 minutes). It is for exploration and layout building, not execution.

What you do not need for Public.com

• No App Key / App Secret pair (Schwab-style OAuth credentials).
• No Callback URL or port number.
• No account ID entry — accounts are discovered automatically after authentication.
• No gateway or bridge application running locally (unlike Interactive Brokers, which needs TWS or IB Gateway).
• No separate developer portal account.

The Control Center, Connections Manager and Workspaces

Three parts of SabrTrader are involved in every connection setup. Understanding what each one owns prevents most configuration confusion.

Control Center

The Control Center is the primary SabrTrader window. It hosts platform-wide functions rather than trading tools: the Connections tab, the workspace menu, and the launchers for new charts, DOMs and panels. It is the window you return to whenever you change connections or layouts.

Connections manager

The Connections manager (Connections tab of the Control Center) has two regions:

• Pre-configured templates (upper region) — 57 broker and data feed configurations shipped with the platform. Each template already knows the vendor's endpoints, transport and required credential fields. A template is a blueprint; it holds no credentials and cannot connect on its own.
• Your saved profiles (lower region) — connection profiles you created from templates, each holding its own credentials and name. These are what you click Connect on.

The 57 templates fall into three functional categories:

Category	What it provides	Examples
Data-only feed	Market data (quotes, trades, history). No order routing, no account access.	dxFeed demo, Massive.com / Polygon.io
Broker + data (dual)	Market data, order routing, balances and positions on one connection.	Public.com, Charles Schwab, Interactive Brokers, Coinbase
Broker / routing-centric	Execution and futures data through a specialised infrastructure provider.	Rithmic (prop firms and futures brokers)

Credential complexity varies by vendor. Most templates need only an API key or key + secret. A minority require OAuth login in a browser, a callback URL with a port, an account or system identifier, or locally running gateway software. Public.com sits at the simple end: API Secret Key only.

Connection profile editor controls

Control	Function
Highlight (select) a template	Displays the template's field set in read-only form. Fields are greyed out because a template is not editable.
Add Below	Creates a new editable profile beneath the template, copying its field structure. This is the step that unlocks the credential fields.
Profile name field	Auto-populated (for example New Public if a profile named Public already exists). Rename it to something descriptive.
API Secret Key	The only credential Public.com requires. Paste the value generated on public.com.
Save Profile	Persists the profile and its credentials locally so you never re-fetch the key. Skipping this is the single most common setup mistake.
Connect / Disconnect	Opens or closes the live session for that specific profile. Each profile connects independently.
Delete	Removes a saved profile. Use it to clean up test or duplicate profiles.
Connection status panel	Expandable list of currently active connections. Use it to confirm exactly which feeds are live.

Workspaces

A workspace is a saved layout of charts, DOMs and panels. Charts inside a workspace are bound to the connection they were created on. The workspace menu in the Control Center lets you open, close, create, save and switch workspaces.

SabrTrader ships with a default workspace that loads on first launch and auto-connects to the delayed dxFeed demo data, so a new installation shows working charts instead of an empty Control Center. That workspace is fully functional — you can interact with order entry on it — but its prices are delayed, so it exists for exploration, not trading.

Closing a workspace and disconnecting a feed are different operations. Closing a workspace removes windows from the screen; the underlying data connection stays live. Disconnecting a feed ends the data session; any workspace referencing it will show stale or empty charts. When switching to a new broker you normally do both.

Trading and Market Data Concepts Behind the Connection Choice

Which SabrTrader tools work on a connection is determined entirely by the type and latency of data that connection delivers. These definitions apply to Public.com and to every other connection.

Brokerage feed vs data feed

• A brokerage feed streams market data and routes live orders to a broker for execution, exposing accounts, balances and positions.
• A data feed supplies market data only. It has no order routing and no account access.

Because SabrTrader is broker-neutral, these roles can be split: you may chart from one data vendor and execute at a different broker. Public.com covers both roles, which is why it is a convenient single connection for equities and options traders.

Delayed vs real-time market data

• Delayed market data is quotes and trades published on a fixed lag, commonly 15 minutes. It can be charted and is adequate for learning the platform, configuring indicators and building layouts. It must never be used for live execution decisions, because the price on screen is not the price in the market.
• Real-time market data is tick-by-tick quotes and trades delivered with no artificial delay. It is required for any decision made in the current moment and for all order-flow tooling.

Level 1 vs Level 2 data

Tier	Contents	Enables
Level 1	Best bid, best ask, last trade price and size.	Candlestick and bar charts, price indicators, basic order entry.
Level 2 (market depth)	The resting depth-of-market ladder — queued bid and ask size at multiple price levels. Market-by-order (MBO) depth exposes individual queued orders rather than only aggregate size per level.	Liquidity Heatmap and SuperDOM, iceberg detection, queue-position reading.

Order flow tooling prerequisites

SabrTrader's order-flow tools have hard data requirements that no setting can bypass:

• Footprint needs trade-by-trade tick data with aggressor side (which side initiated each trade) to split volume into buy and sell at each price.
• Liquidity Heatmap and SuperDOM need streaming Level 2 / MBO depth updates.
• Volume Profile works from traded volume at price and is usable on aggregated data, but is far more accurate with tick data.

On a delayed connection these tools will either render nothing meaningful or render a 15-minute-old picture. A delayed feed therefore limits the platform to chart study, not order-flow reading.

Market data entitlements

Market data entitlements are the permissions granted by an exchange or broker that determine whether you receive delayed or real-time data, and how much history. Two accounts on the same broker can see different data because their entitlements differ. Professional and non-professional users are also charged and entitled differently. If a connection authenticates successfully but prices lag or history is short, the cause is almost always entitlements rather than the platform.

API credentials and their lifecycle

• An API secret key is a private credential issued by the broker that authorises a third-party platform to access your account programmatically. It functions as a password: anyone holding it can act with the permissions it grants.
• API key revocation invalidates a previously issued key so it can no longer authenticate. Revoke keys that are unused, that you failed to copy, or that may have been exposed.
• A connection profile stores the key plus settings locally so reconnecting is a single click.

Other terms used in the workflow

• Order routing is the path an order takes from SabrTrader through the broker to an exchange or market maker.
• Instrument type is the asset-class filter (stock, option, future, crypto) applied when looking up a symbol on a connection.
• Symbol lookup is searching a connection's instrument list to resolve a ticker into a tradable symbol the platform can subscribe to.
• Chart period / bar interval is the amount of time or activity each bar aggregates — 60 minutes in the video.
• Lookback / history range is how far back historical data is loaded — 21 days in the video.
• Demo / paper trading is placing simulated orders against delayed or simulated data to learn a platform without risking capital.

Step-by-Step: Connecting Public.com

Step 1 — Close the default workspace

1. In the Control Center, open the Workspace menu.
2. Select the Default workspace entry (a new installation has only this one; an experienced user will see several).
3. Choose Close.

Closing the default workspace removes the demo charts from screen. It does not disconnect dxFeed — that is Step 2. The goal is a clean layout that you will bind to the Public.com connection, so no chart is silently reading delayed prices.

Step 2 — Disconnect the dxFeed demo data connection

1. Open the Connections tab in the Control Center.
2. Locate the dxFeed (DX Feed) entry in your saved profiles.
3. Click Disconnect.

Reasons to disconnect an unused feed:

• It consumes bandwidth and CPU for symbols you are not watching.
• Two live feeds can create duplicate symbol subscriptions, making it ambiguous which feed a chart is bound to.
• A delayed feed left connected is the most common cause of traders reading 15-minute-old prices as live.

Keep dxFeed connected only if you deliberately want a delayed reference feed for symbols your broker does not carry, and you label those charts clearly.

Step 3 — Locate the Public.com template

1. Stay in the Connections tab.
2. Scroll or filter the upper region of 57 pre-configured templates to find Public.
3. Click it once to highlight it.

With the template highlighted you will see its field set — for Public.com, a single API Secret Key field — but every field is greyed out and refuses input. This is expected: templates are read-only blueprints.

Step 4 — Create the profile with Add Below

1. With Public highlighted, click Add Below.
2. A new editable profile appears beneath, named Public or, if a profile with that name already exists, auto-named New Public.
3. Rename it descriptively — for example Public - Live or Public - Test — especially if you will hold more than one Public.com profile.

The credential fields are now editable. If they are still greyed out, you highlighted the template but did not click Add Below.

Step 5 — Generate the API secret key on public.com

1. Open a browser and log in to public.com.
2. Click the settings cog in the top navigation.
3. Select API from the settings menu.
4. Click Create New.
5. Give the key a descriptive name that identifies where it will be used, for example SabrTrader desktop.
6. Copy the key immediately and paste it into a password manager (preferred) or a text editor. The secret is normally shown only once.
7. If you generated a key you will not use — for example a demonstration key — click Revoke on it so you cannot later confuse it with your active key.

Treat this string as a password. It authorises programmatic access to a funded brokerage account. Do not paste it into chat, email, screenshots or support tickets.

Key hygiene matters because a single Public.com account can hold several keys. Naming each key after its consumer, and revoking anything unused, keeps the mapping unambiguous.

Step 6 — Paste the key and save the profile

1. Return to SabrTrader and select your new Public profile.
2. Paste the secret into the API Secret Key field. Verify there is no leading or trailing whitespace and no line break — a stray space is enough to fail authentication.
3. Leave every other setting alone. Endpoints, transport and account discovery are negotiated automatically.
4. Click Save Profile.

Save Profile is not optional. If you connect without saving, the credential is not persisted; the next launch will present an empty field and you may have to revoke and regenerate the key. While you are here, Delete any stale or test profiles so the list stays unambiguous.

Step 7 — Connect and verify

1. With the saved profile selected, click Connect.
2. Expand the connection status panel in the Control Center.
3. Confirm that public.com appears as an active connection — and, if you completed Step 2, that it is the only active connection.

A healthy connected state shows: the profile marked connected in the Connections tab, public.com listed in the status panel, and your account with its balance and buying power discoverable by order-entry panels. If the connection reports success but no accounts or balances appear, the account is unfunded, not yet approved, or the key was issued from a different account.

Step 8 — Load a workspace and open your first chart

1. Open the Workspace menu and either open the workspace you want tied to Public.com or create and name a new one (for example Public - Equities), then Save it.
2. Launch New Chart from the Control Center.
3. In the connection selector, choose your Public.com profile. This binds the chart's data subscription to that connection.
4. Set instrument type to Stock (switch to Option for options chains).
5. Use symbol lookup to search the ticker — the video searches GOOGL — and select the resolved instrument from the results.
6. Set period / bar interval to 60 minutes.
7. Set history / lookback to 21 days.
8. Click to open the chart.

Twenty-one days of 60-minute bars gives roughly three weeks of intraday context — enough to see swing structure without a long load time. Shorten the lookback if the chart is slow to load; lengthen it if you need more historical context for indicators that require warm-up bars.

Save the workspace again once the chart is arranged. The layout, the symbol, the interval and the connection binding are all stored, so reopening the workspace after a restart requires only clicking Connect on the profile.

Best Practices

Credentials

• Name every API key after its consumer, for example SabrTrader desktop, so you always know what a key is for.
• Store keys in a password manager. A plain text file on the desktop is convenient during setup and a liability afterwards.
• Revoke any key you did not copy, no longer use, or suspect has been exposed. Revocation is instant and free; a leaked key is not.
• Never reuse one key across several machines if you can generate one per machine — revoking a single compromised machine then does not disrupt the others.

Profiles and connections

• Use descriptive profile names that state both broker and purpose: Public - Live, Public - Test.
• Always click Save Profile immediately after pasting credentials, before clicking Connect.
• Delete duplicate and abandoned profiles. Two similarly named Public profiles is how traders connect the wrong account.
• Disconnect feeds you are not using, especially delayed demo feeds.

Workspaces

• Keep one workspace per connection so no layout mixes delayed and real-time charts.
• Name workspaces after the connection they are bound to.
• Save the workspace after any layout change; unsaved changes are lost when you close it.

Live trading readiness

• Fund the account with a small balance first and place one small order to confirm end-to-end order routing before scaling size.
• Confirm which asset classes your account is approved for before building an options workflow.
• Check whether the connection delivers real-time or delayed data before relying on any intraday decision, and before expecting footprint or heatmap and SuperDOM tools to populate.
• Re-verify the connection after a platform update or a broker API change: connect, check the status panel, confirm balances, then confirm a live quote is moving.

Common Mistakes

Mistake	What happens	Correct approach
Typing into credential fields with only the template highlighted	Fields are greyed out and reject input; users conclude the platform is broken.	Highlight the template, click Add Below, then edit the new profile.
Forgetting Save Profile	The key is not persisted. On next launch the field is empty and, since the secret is shown once on public.com, you must revoke and regenerate.	Save the profile immediately after pasting, before connecting.
Leaving dxFeed delayed data connected	Charts and quotes show prices up to 15 minutes old that look live. Decisions are made on stale information.	Disconnect dxFeed once your broker connection is live, or clearly isolate delayed charts in their own workspace.
Expecting order-flow tools to populate from a delayed feed	Footprint, liquidity heatmap and SuperDOM show nothing useful or show a 15-minute-old picture.	Use a real-time tick and depth feed for order-flow work; treat delayed data as study-only.
Pasting the key with trailing whitespace or a line break	Authentication fails with a generic error even though the visible characters are correct.	Paste, then check the field ends exactly at the last character of the key.
Creating duplicate Public profiles	You connect the wrong account and see unexpected balances or routing.	Delete stale profiles; give each remaining profile a unique descriptive name.
Charting a symbol on the wrong connection	Symbol lookup fails, or the chart loads from a delayed feed while orders go to the broker.	Explicitly set the connection selector in the New Chart dialog every time.
Wrong instrument type in symbol lookup	A valid ticker returns no results because the search is filtered to a different asset class.	Set instrument type (stock, option, future, crypto) before searching.
Connecting an unfunded or unapproved account	Authentication succeeds but buying power is zero and orders are rejected.	Fund and confirm approval before live order tests.
Closing a workspace and assuming the feed is disconnected	The delayed feed keeps streaming in the background and consumes bandwidth.	Treat workspace closing and feed disconnecting as two separate steps.

Frequently Asked Questions

Do I need anything besides an API secret key to connect SabrTrader to Public.com?

No. The Public.com connection template requires only the API Secret Key. Endpoints, transport and account discovery are negotiated automatically. You do not need an App Key, a Callback URL, a port number, an account ID or any locally installed gateway software. What you do need outside the platform is an open, approved and funded Public.com account.

Is the data that loads on first launch of SabrTrader real-time or delayed?

Delayed. SabrTrader ships with a default workspace that auto-connects to the dxFeed demo data connection so a new installation shows working charts instead of an empty Control Center. That feed publishes prices on a lag (commonly 15 minutes). It is suitable for exploring the interface, building layouts and configuring indicators — not for live execution decisions.

Can I place orders on the default dxFeed connection?

The default demo environment is fully functional in the sense that the order-entry interface works and you can practise the mechanics of buying and selling. Because the underlying prices are delayed, this is demo / paper trading only: simulated orders against lagged data, used to learn the platform without risking capital. Any decision you make there is based on prices that are already 15 minutes old.

Where do I generate a Public.com API key?

Log in to public.com, click the settings cog in the top navigation, choose API, then click Create New. Give the key a descriptive name, then copy the secret immediately — it is normally displayed only once. Paste it into a password manager before returning to SabrTrader.

What happens if I lose my API secret key?

You cannot retrieve it. Broker API secrets are shown once at creation. Go back to the API section of your Public.com settings, revoke the lost key so it can no longer authenticate, create a new one, and paste the new value into your SabrTrader profile. Then click Save Profile so you do not repeat the process.

Why are the credential fields greyed out when I select a connection template?

Because the 57 entries in the upper region of the Connections manager are read-only templates, not profiles. A template is a blueprint describing which fields a vendor needs. To enter credentials you must highlight the template and click Add Below, which creates an editable profile underneath. The new profile's fields accept input; the template's never will.

Do I have to re-enter my API key every time I start SabrTrader?

No, provided you clicked Save Profile. A saved connection profile stores the credential and settings locally, so reconnecting on a later session is a single click on Connect. If you connected without saving, the credential is not persisted and you will need to paste it again — or regenerate it if you did not keep a copy.

Can I connect more than one Public.com account at the same time?

Yes. Create a separate profile from the Public template for each account, paste that account's own API secret key into each, and give each a distinct descriptive name such as Public - Live and Public - Test. SabrTrader auto-names the second one New Public if a profile called Public already exists; rename it so you never connect the wrong account. Each profile connects and disconnects independently.

Should I disconnect dxFeed after connecting my broker?

Yes, in almost all cases. Leaving an unused feed connected consumes bandwidth, can create duplicate symbol subscriptions, and makes it ambiguous which feed a chart is bound to. Worst of all, it leaves delayed prices on screen that can be mistaken for live prices. Keep it connected only if you deliberately want a delayed reference feed and you keep those charts clearly separated.

Can I use footprint charts and the liquidity heatmap on a delayed connection?

Not meaningfully. Footprint requires trade-by-trade tick data with aggressor side, and Liquidity Heatmap and SuperDOM require streaming Level 2 / market-by-order depth. A delayed feed either does not carry that granularity or delivers it 15 minutes late, so the tools show nothing actionable. Order-flow reading requires a real-time tick and depth feed.

How many brokers and data feeds does SabrTrader support out of the box?

57 pre-configured broker and data feed templates ship with the platform. They fall into three groups: data-only feeds (market data with no routing), dual broker + data connections such as Public.com, and routing-centric broker connections such as Rithmic for futures and prop firm accounts. Most templates need only an API key; a minority require OAuth login, an account or system identifier, or locally running gateway software.

Does my Public.com account need to be funded before connecting?

Authentication itself does not require a balance, but a funded account is required before live orders can be accepted. An unfunded account typically connects successfully yet shows zero buying power, and any live order is rejected. The demonstration used a $500 test balance, which is enough to validate end-to-end order routing without meaningful risk.

How do I revoke an API key I no longer use?

In your Public.com account, open settings cog → API, find the key in the list, and choose Revoke. Revocation invalidates the credential immediately so it can no longer authenticate. Revoke keys that you failed to copy, keys created for demonstration, keys tied to machines you no longer use, and any key you suspect has been exposed.

Why can't I find my symbol in the New Chart dialog?

Four causes account for nearly all cases: (1) the connection selector points at the wrong connection, so you are searching a different vendor's instrument list; (2) the instrument type filter is set to the wrong asset class — a stock ticker will not appear under Option or Future; (3) the ticker syntax differs on that provider; (4) the instrument is not carried by the connection at all. Set connection and instrument type first, then search.

What is the difference between closing a workspace and disconnecting a connection?

Closing a workspace removes charts, DOMs and panels from the screen; the data session behind them stays live and keeps streaming. Disconnecting a connection ends the data and order session; workspaces referencing it remain open but their charts stop updating. When switching from the demo feed to a broker you should do both: close the default workspace, then disconnect dxFeed.

Is Public.com a broker, a data feed, or both?

Both. Public.com is a dual broker + data connection: the same connection supplies market data for charts and routes live orders to your brokerage account, and exposes balances and positions. That is why one credential covers charting and execution. By contrast, a data-only connection such as Massive.com / Polygon.io provides prices with no routing.

Can I chart from one connection and execute on another?

Yes. SabrTrader is data-neutral and broker-neutral, so market data and execution can come from independently chosen vendors. A common pattern is a premium real-time data feed for charts and order-flow tools plus a separate broker for routing. If you do this, be deliberate about which connection each chart is bound to, and use separate workspaces to avoid confusion.

What chart period and history should I use for my first chart?

The demonstration uses 60-minute bars with 21 days of history, which gives roughly three weeks of intraday context at a fast load time. Smaller intervals reveal more detail with more noise; larger intervals smooth price at the cost of granularity. Increase the lookback if an indicator needs more warm-up bars; reduce it if the chart is slow to load.

How is the Public.com setup different from connecting Schwab or Interactive Brokers?

Public.com needs one API secret key and nothing else. Schwab uses OAuth 2.0: a developer application with an App Key and App Secret, an exactly matching Callback URL with a four-digit port above 4000, and a browser login with account selection. Interactive Brokers requires Trader Workstation or IB Gateway running locally with API access enabled and a socket port configured. Public.com is the simplest of the three.

Troubleshooting

Connect fails immediately or the connection drops seconds after connecting

This is nearly always a credential problem. Check in order:

1. The key was revoked on public.com — generate a new one.
2. The key was pasted with leading or trailing whitespace or a line break. Re-copy and re-paste, verifying the field ends at the last character.
3. The key belongs to a different Public.com account than the one you expect.
4. Only part of the key was copied because it was truncated in the display.

After correcting the value, click Save Profile again before reconnecting.

Connection shows as active but no accounts, balances or buying power appear

Authentication succeeded, so the key is valid. The account itself is the issue:

• The account is not funded — deposit capital, then reconnect.
• The account is not yet fully approved, or is not approved for the asset class you are looking at.
• The key was generated on a different account than the one holding funds.

Disconnect, reconnect, and re-expand the connection status panel after resolving the account state.

Symbol not found in the New Chart dialog

Verify three settings before assuming the instrument is unavailable:

1. Connection selector — you may be searching a different vendor's instrument list.
2. Instrument type — a stock ticker returns nothing when the filter is set to Option, Future or Crypto.
3. Ticker syntax — symbol mapping differs by provider and asset class.

If all three are correct, the instrument is not carried on that connection; chart it on a data feed that covers it.

Chart opens but is blank or shows very few bars

• The market is closed and the chosen interval has produced no new bars — expected outside session hours.
• The lookback is too short for the interval. Increase the history range (for example from a few days to 21 days).
• The connection has limited historical entitlement for that interval or symbol. Reduce the interval granularity or use a data feed with deeper history.
• You are charting on a disconnected profile. Confirm the profile is connected in the status panel.

Quotes look duplicated, flicker, or two charts of the same symbol disagree

Two feeds are connected simultaneously and each chart is bound to a different one — commonly the delayed dxFeed demo plus your broker. Open the Connections tab, disconnect every feed you are not using, expand the connection status panel and confirm only the intended connection is active. Then rebuild or re-bind any chart that was created on the wrong connection.

Orders are rejected by the broker

• Insufficient funds or buying power — the account is unfunded or the position size exceeds available capital.
• The order type is not supported for that venue or instrument.
• The account is not approved for that asset class (for example options).
• The market is closed for the order type submitted.

Test with the smallest possible size on a liquid symbol during regular hours to isolate which of these applies.

Credential fields will not accept typing or pasting

You have a template highlighted rather than a profile. Templates are read-only. Highlight the Public entry in the upper region, click Add Below to create an editable profile beneath it, select that new profile, and enter the key there.

After restarting SabrTrader the API Secret Key field is empty

The profile was never saved. Paste the key again and click Save Profile before clicking Connect. If you no longer have a copy of the key, revoke it on public.com and generate a replacement — secrets cannot be retrieved after creation.

Footprint, liquidity heatmap or SuperDOM show no data

These tools have hard data requirements. Footprint needs trade-by-trade tick data with aggressor side; heatmap and SuperDOM need streaming Level 2 / market-by-order depth. A delayed or Level 1-only connection cannot supply them. Confirm the connection delivers real-time tick and depth data, and that your market data entitlements include depth for that market.

You connected the wrong Public.com account

Duplicate or ambiguously named profiles are the cause. Disconnect, then rename each profile to state the account explicitly (Public - Live, Public - Test), delete any profile you no longer need with Delete, and reconnect the correct one. Verify the account balance in the status panel before placing any order.

Charts show delayed prices even though the broker connection is live

The chart is bound to the delayed feed, not the broker. A chart keeps the connection it was created on. Disconnect dxFeed, then recreate the chart with the Public.com profile selected in the New Chart dialog's connection selector, and save the workspace so the correct binding persists.

Glossary

Account funding

Depositing capital into a brokerage account. Funding is required before live orders can be accepted, even though API authentication may succeed on an unfunded account.

API key revocation

Invalidating a previously issued API key so it can no longer authenticate, used when a key is unused, misplaced or compromised.

API secret key

A private credential issued by a broker that authorises a third-party platform to access your account programmatically. It functions as a password and must never be shared.

Brokerage feed

A connection that both streams market data and routes live orders to a broker for execution, and exposes account balances and positions.

Chart period / bar interval

The amount of time or activity each bar on a chart aggregates, such as a 60-minute bar. Smaller intervals reveal more detail with more noise; larger intervals smooth price at the cost of granularity.

Connection profile

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

Connections manager

The area of the SabrTrader Control Center containing the 57 pre-configured broker and data feed templates, the user's saved connection profiles, and the Add Below, Save Profile, Delete, Connect and Disconnect controls plus the connection status panel.

Control Center

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

Data feed connection

A connection that supplies market data only, with no order routing and no account access.

Data-neutral / broker-neutral platform

A platform design in which market data and order execution come from independently chosen vendors, so a trader can combine any supported data feed with any supported broker.

Delayed market data

Quotes and trades published on a fixed lag, commonly 15 minutes, that can be charted but must not be used for live execution decisions.

Demo / paper trading

Placing simulated orders against delayed or simulated data to learn a platform's mechanics without risking capital.

DOM

Depth of Market — a price ladder showing resting bid and ask liquidity at each price level, used for order-flow reading and precise order entry. It requires a depth-enabled feed rather than a trades-only feed.

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

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.

Instrument type

The asset-class filter — stock, option, future or crypto — applied when looking up a symbol on a connection.

Level 1 data

Market data showing the best bid, best ask and last trade price and size. Sufficient for bar and candlestick charts and basic order entry.

Level 2 data

Market data showing the resting depth-of-market ladder — queued bid and ask size at multiple price levels — required for DOM and liquidity heatmap tools.

Lookback / history range

How far back historical data is loaded into a chart when it is created, expressed in days or bars. Greater depth gives more context but increases load time and memory use.

Market data entitlements

Permissions granted by an exchange or broker that determine whether an account receives delayed or real-time data, which symbols it may see, and how much history is available.

Market depth (MBO)

The visible resting bid and offer liquidity at each price level. Market-by-order data exposes individual queued orders rather than only aggregated size per level.

Order routing

The path an order takes from the trading platform through the broker to an exchange or market maker for execution.

Real-time market data

Tick-by-tick quotes and trades delivered with no artificial delay, required for live execution decisions and for order-flow tools such as footprint and DOM.

Symbol lookup

Searching a connection's instrument list to resolve a ticker into a tradable symbol the platform can subscribe to.

Tick data granularity

Whether a feed carries individual trades with size and aggressor side rather than only pre-aggregated bars. It determines whether footprint and delta tools can be built.

Workspace

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

Related Documentation