Tracked tickers

The API works on the tickers the account tracks, and the tracked list is the account's watchlist on the site. The chart page, alerts, the API and the MCP server all read one list, so adding a ticker anywhere adds it everywhere. During the beta an account tracks up to 50.

Why tracked tickers

Pattern, history and chart calls answer only for tracked tickers. The list is the unit the account is measured on, and it keeps the nightly book from being enumerated one symbol at a time. Family track records, the universe and the demo do not depend on it.

Read the list

curl "https://api.tradingpal.io/api/v1/tickers" \
  -H "Authorization: Bearer $TRADINGPAL_API_KEY"

covered is true when the current nightly build includes the ticker. A tracked ticker that is not covered has no setups yet; the patterns route answers available: false with reason: "not_covered" rather than an error. GET /universe lists every symbol the nightly covers.

Replace the list

PUT /tickers replaces the whole list and is all-or-nothing: if any symbol is invalid, unknown or over the cap, nothing changes and the error's details names the offending symbols.

curl -X PUT "https://api.tradingpal.io/api/v1/tickers" \
  -H "Authorization: Bearer $TRADINGPAL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"symbols": ["NVDA", "AAPL", "BRK.B"]}'

To add one ticker, read the list, append, and put it back, as the Python sample does. An agent should do the same rather than sending a one-symbol list, which would drop everything else.

Symbols

Use the exchange symbol in upper case: BRK.B for a class share, BTC-USD for a crypto pair. Symbols are validated against the tickers TradingPal knows; invalid_symbol means the string is malformed, unknown_symbol means it is well formed but not a ticker we have.

The cap

cap comes back with every tickers response. Over the cap, PUT fails with ticker_cap_exceeded and changes nothing. The cap is per account, not per key: two keys on one account share the same list.

When a call says ticker_not_tracked

A pattern, history or chart call on an untracked ticker returns 403 ticker_not_tracked. The error's fix says how many slots are free and how to add the ticker. An agent that gets this error should add the ticker and retry, which is what the MCP tools' error text tells it to do.