Skip to main content

Alpaca tradable assets and shortable stocks for AlgoWay webhook automation

Alpaca Tradable Assets and Shortable Stocks for AlgoWay Webhook Automation

Before you route a TradingView alert to Alpaca through AlgoWay, you should know whether the symbol is actually tradable, shortable, marginable or fractionable on Alpaca. A ticker can exist in a market data universe but still be blocked for trading, short selling, margin use or fractional sizing.

This page explains how to use an Alpaca instruments reference together with AlgoWay webhook automation. It is designed for traders searching for Alpaca tradable assets, Alpaca shortable stocks, Alpaca assets API, Alpaca fractionable stocks, TradingView to Alpaca webhook symbols, and AlgoWay Alpaca automation.

The practical workflow is:

TradingView alert → AlgoWay webhook → Alpaca symbol check → Alpaca order routing

Dataset snapshot: 2025-09-01 • Source noted in original page: Alpaca Paper API active assets • Author: AlgoWay

Open the Full Alpaca Instruments Reference​

The full reference table is here:

Open the Alpaca instruments table

The table was generated as a searchable reference for Alpaca symbols and key automation flags. Use it as a fast starting point when building AlgoWay filters, but refresh the data before relying on it for production trading.

Why Alpaca Asset Flags Matter for Webhook Trading​

In automated trading, a symbol must pass more than one check. A TradingView alert can be valid, the AlgoWay webhook JSON can be valid, and your Alpaca API credentials can be correct — but the final order can still fail if the asset is not allowed for the action you send.

Examples:

  • a symbol may be active but not tradable;
  • a stock may be tradable for buying but not shortable;
  • a symbol may not allow fractional shares;
  • margin rules can differ by asset and account type;
  • paper and live environments can behave differently;
  • borrowing availability for shorts can change.

That is why Alpaca asset flags should be part of the pre-trade validation layer for TradingView-to-Alpaca automation.

Key Fields in the Alpaca Instruments File​

The linked file contains one row per instrument with key fields that are useful for AlgoWay automation:

FieldMeaning for automation
SymbolThe Alpaca symbol, for example AAPL.
ExchangeThe exchange or venue tag, such as NASDAQ, NYSE or OTC.
NameThe security name returned by the asset source.
StatusLifecycle status, often active.
TradableWhether orders can be submitted for the symbol through Alpaca.
ShortableWhether the asset is eligible for short selling.
MarginableWhether margin trading is allowed for the asset/account conditions.
FractionableWhether fractional share orders are supported.
Min SizeThe minimum order size value available in the dataset.

Tradable Does Not Mean Shortable​

A common automation mistake is assuming that if a stock is tradable, it can also be shorted. That is not safe. A long-only strategy may only need tradable = true. A short-selling strategy must check shortable = true before sending a sell/short-style command.

For AlgoWay automation, a practical rule is:

BUY signal  → require tradable = true
SHORT signal → require tradable = true and shortable = true

Even then, shortable = true should be treated as eligibility, not a real-time borrow guarantee. Live conditions can still change.

Fractionable Assets and Micro-Sizing​

Fractional shares are important when using small accounts, testing small signals, or routing many low-size alerts from TradingView. If a symbol is not fractionable, a fractional order can be rejected even if the symbol is otherwise tradable.

For AlgoWay webhook automation, check fractionable = true before sending fractional share quantity or notional-style sizing. If the asset is not fractionable, use whole-share sizing or block the alert before it reaches Alpaca.

Marginable Assets and Risk Filters​

The marginable flag helps decide whether a symbol should be allowed in margin-based strategies. This does not mean a strategy should use margin automatically. It only tells you whether the asset may be eligible under Alpaca and account conditions.

Before routing margin-based signals, check:

  • account equity;
  • buying power;
  • margin eligibility;
  • asset marginable flag;
  • day trading restrictions;
  • risk limits inside AlgoWay or your own backend.

How to Use Alpaca Asset Flags with AlgoWay​

Use the instruments reference as a pre-trade filter for AlgoWay alerts. The exact implementation depends on your workflow, but the logic is straightforward.

1. Build a Tradable Symbol Whitelist​

Only allow TradingView alerts for symbols where tradable = true.

if symbol.tradable != true:
    block alert before order routing

2. Build a Shortable Symbol Filter​

If the strategy can send short signals, check shortable before routing the order.

if order_action in ["sell", "short"] and symbol.shortable != true:
    block short order

3. Use Fractionable for Small Accounts​

If your strategy sends fractional order sizes, verify that fractionable = true.

if order_contracts is fractional and symbol.fractionable != true:
    block or round quantity

4. Use Exchange and Symbol Groups for Risk Rules​

You can group symbols by exchange or asset type. For example, you may set different risk limits for NASDAQ, NYSE, OTC and ETF symbols.

Example TradingView to Alpaca JSON​

After symbol validation, a basic TradingView strategy alert for Alpaca can look like this:

{
  "platform_name": "alpaca",
  "ticker": "{{ticker}}",
  "order_contracts": "{{strategy.order.contracts}}",
  "order_action": "{{strategy.market_position}}",
  "price": "{{close}}"
}

For fixed testing, use a direct ticker first:

{
  "platform_name": "alpaca",
  "ticker": "AAPL",
  "order_contracts": 1,
  "order_action": "buy"
}

Full setup guide: How to connect TradingView alerts to Alpaca with AlgoWay.

Why a Symbol Can Fail Even If It Appears in a List​

Do not treat any static symbol list as a permission guarantee. A symbol can fail for several reasons:

  • the asset flag changed since the snapshot was generated;
  • the asset is active but not tradable;
  • the asset is tradable but not shortable;
  • the order uses fractional size on a non-fractionable asset;
  • the account is not eligible for margin or short selling;
  • the market is closed;
  • the symbol is halted or restricted;
  • paper and live behavior differ;
  • your TradingView ticker does not match the Alpaca symbol.

Common Mistakes in Alpaca Symbol Automation​

Mistake 1: Using TradingView Ticker Without Checking Alpaca Symbol​

TradingView tickers and broker/API symbols are not always identical. Always test the exact value that will be sent in ticker.

Mistake 2: Shorting Without Checking Shortable Flag​

Do not let a strategy send short commands just because the asset is visible. Check shortable first.

Mistake 3: Sending Fractional Size to Non-Fractionable Assets​

If fractionable is false, use whole-share size or block the alert.

Mistake 4: Using an Old Snapshot for Live Routing​

The dataset is useful for research and filtering, but live order routing should refresh current Alpaca asset flags.

Mistake 5: Ignoring Paper vs Live Differences​

Paper trading is useful for testing, but production logic should be verified against live permissions before live orders.

To keep the instruments reference useful:

  1. Refresh Alpaca assets periodically from the Alpaca Assets API.
  2. Store symbol, tradable, shortable, marginable, fractionable and status.
  3. Use the latest table as a whitelist before routing AlgoWay webhook orders.
  4. Log every rejected Alpaca order.
  5. Update your filters when Alpaca rejects a symbol due to status or permission changes.

Final Summary​

Alpaca instruments data is a practical safety layer for TradingView-to-Alpaca automation. Before routing webhook orders through AlgoWay, check whether the symbol is tradable, shortable, marginable and fractionable. Use the linked instruments table as a reference, but refresh the live flags before production trading.

Good automation is not only about sending alerts. It is about blocking the wrong alerts before they become rejected orders.