Schwab Chart Data, thinkorswim, and API Readiness

Is there a thinkorswim API?

No public external API exists for thinkorswim. ThinkScript is thinkorswim's built-in scripting language for custom indicators, scanners, and alerts. It runs inside the thinkorswim environment — there is no external endpoint that accepts ThinkScript queries from outside the platform and no alert-to-webhook integration path.

The Schwab Trader API is the correct tool for programmatic account and market data access. It operates as a separate REST layer — it is independent of thinkorswim and cannot control or query the thinkorswim platform state.

For a full API overview including authentication and fit checklist, see Schwab Trader API for Technical Traders: Workflow Fit Checklist.

What chart data does the Schwab Trader API provide?

The Schwab Trader API provides OHLCV historical bars for US equities and ETFs at six intervals: daily, 1-minute, 5-minute, 10-minute, 15-minute, and 30-minute. One-minute history is approximately 30 to 35 days deep. Options bars and futures bars are not available.

Real-time streaming via WebSocket covers Level 1 and Level 2 (NYSE/NASDAQ) quotes for equities and ETFs, options quotes, and time-of-sale data.

For split and dividend adjustment details on historical bars, check the current Schwab developer documentation before building a pipeline that depends on adjusted prices.

What does ThinkScript do, and why is it not an external API?

ThinkScript is a domain-specific language for writing custom indicators, strategies, and scanners inside thinkorswim. ThinkScript calculations render on thinkorswim charts — they do not produce output that external programs can consume directly.

ThinkScript is not an external API because it runs in thinkorswim's runtime, not as a standalone service. There is no HTTP or socket endpoint that accepts ThinkScript queries from outside the platform. No external system can read ThinkScript-calculated indicator values without a separate export or screen-capture step.

thinkorswim and the Schwab Trader API are two separate systems. The API gives you price data and account access; thinkorswim gives you charts, indicators, and order management through a GUI.

What chart context does the Schwab API not preserve?

The Schwab Trader API returns price data and account state. Everything else in a thinkorswim chart session stays inside thinkorswim.

Not accessible via the API: trendlines, channels, Fibonacci tools, and other drawing objects; text annotations and session notes; ThinkScript indicator configurations and calculated study values; chart layouts and saved scan configurations; any markup that documents analysis and trade reasoning.

The gap between what the API provides and what a chart session contains is the export layer gap. If your review workflow needs annotation context alongside price data, that requires a separate capture or export step outside the API. For a reference on what fields a structured chart export can preserve, see TradingView vs TrendSpider vs MyLinedChart: Structured Chart Exports for Real Trading Processes.

How do chart review workflows fit with the Schwab API?

A Schwab-based chart workflow typically splits into two layers. The analysis layer lives inside thinkorswim: chart markup, indicator study, notes, and level drawing. The data and execution layer runs through the Schwab Trader API: bar and quote data, order submission, and account data for journaling.

If your workflow needs the two layers to connect — for example, if you want thinkorswim chart annotations attached to API-sourced trade data — you need an explicit export step that bridges them. There is no automatic connection between thinkorswim's chart state and the Schwab Trader API.

For export capabilities and plan access, see Pricing. Planning support only — no trading advice.

What to prepare before building a Schwab chart data workflow

Resolve these before writing integration code.

• Confirm which instruments you need against Schwab's historical bar scope: equities and ETFs only; no options or futures bars.
• Define bar intervals and depth requirements. One-minute bars are limited to approximately 30 to 35 days. Daily and multi-minute bars are available with greater depth.
• Separate your thinkorswim chart context from your API price data in the workflow design. The API will not return indicator values or drawing objects.
• If your review process needs drawing annotations or session notes alongside price data, plan a separate capture step — the Schwab API does not expose them.
• Test authentication and token refresh in the sandbox before connecting to live data. The approximately 30-minute access token window requires active refresh logic.
• For structured chart export context alongside Schwab price data, see TradingView vs TrendSpider vs MyLinedChart: Structured Chart Exports for Real Trading Processes.

Is there a thinkorswim API I can use to get chart drawings?

No. There is no public external API for thinkorswim and no alert-to-webhook integration path. ThinkScript runs inside thinkorswim's environment only. The Schwab Trader API provides price bars and account data but does not expose thinkorswim chart drawings or annotations.

What bar intervals are available from the Schwab Trader API?

Daily, 1-minute, 5-minute, 10-minute, 15-minute, and 30-minute intervals for US equities and ETFs. One-minute history is approximately 30 to 35 days deep. No historical bars are available for options or futures.

Can I export my thinkorswim chart drawings via the Schwab API?

No. Chart drawings, trendlines, and annotations exist inside thinkorswim's interface and are not accessible through the Schwab Trader API. Exporting that context requires a separate step outside the API layer.

Does the Schwab API replace what TD Ameritrade's API provided for chart data?

The Schwab Trader API is the functional successor to the TDA Developer API, including its market data endpoints. The TDA API is fully retired. Check the current Schwab developer documentation at developer.schwab.com to confirm data depths and intervals against what your TDA integration used.