BLACK FRIDAY IS BACKNov 24 to 30. Join the list and get in a day early.Join the list

Getting started with Charles Schwab

Autoview · Guide · Updated October 22, 2026

By the end of this guide your Charles Schwab account is connected to Autoview and you have placed one small order and cancelled it. That order is real. Schwab's API has no paper trading mode, so every order Autoview sends to Schwab goes to your real account, whichever Schwab subscription you use. Keep it to one share, parked below the market, and cancel it right away. Ten minutes, start to finish. (Want to practice without real money? See does Schwab support paper trading for the paper and demo connections you can use instead.)

Autoview turns an incoming alert into an order on your broker. Most people fire those alerts from TradingView, but the webhook platform does not care where the request originates. A script, another charting tool, your own backend, anything that can send a POST works the same way. The Chrome extension is the piece built specifically to read TradingView alerts in your browser.

Step 1: pick how Autoview runs

Autoview executes through two surfaces, and your Schwab connection lives on whichever one you choose.

  • Chrome extension. Runs in your browser. Chrome and your computer need to stay open for an order to fire, and it reads TradingView alerts directly.
  • Webhook platform. Runs on Autoview's servers. Your laptop can be closed and orders still go out, and it accepts a POST from any source, TradingView included.

Not sure which one? Start with the webhook platform. It does not care whether your machine is awake. Compare both on the platforms page.

Step 2: connect Schwab, no API key involved

Most exchanges hand you a key and secret to paste in. Schwab does not work that way. You connect by signing in through Schwab's own secure login screen and approving the access Autoview requests. Autoview never sees or stores your Schwab password, it only holds the token that sign-in produces, and that token is what places orders on your behalf afterward.

  • On the extension: open the extension options, find Charles Schwab in the left menu, and start the connection. It opens Schwab's sign-in page. Log in, approve access, and you land back in the extension, connected.
  • On the webhook platform: log in to Autoview, open the Schwab configuration, and start the connection the same way. Schwab's sign-in page opens, you approve access, and the platform shows the account as connected.

You will see two Autoview subscriptions for Schwab: Charles Schwab - Broker and Charles Schwab - Broker - Test. They are not a live account and a practice account. Both use the same Schwab OAuth sign-in, and both send orders to the same Schwab API and the same Schwab account you sign in with. An order sent through the Test subscription is a real order. Give your connection a name, something like my-schwab. Naming matters once you have more than one Schwab connection. On the webhook platform, you pick one by linking it to the webhook. On the extension, you pick one with a= in the command.

Step 3: place one small order, then cancel it

This is the step that proves the connection, so do not skip it. The order goes to your real Schwab account, so keep the size as small as you can afford and cancel it as soon as you see it.

One habit first. Add d=1 to any command and Autoview parses it and logs exactly what it would have sent, but nothing reaches Schwab. Run a clean dry run before you send anything real.

Place a limit buy

Send this as an alert (extension) or as a webhook body (platform):

  • Extension: e=schwab a=my-schwab s=intc b=buy p=-5% q=1
  • Webhook: s=intc b=buy p=-5% q=1

Reading it left to right: trade on your named Schwab connection, symbol INTC, buy side, limit price five percent below the current price, quantity one share. That p=-5% offset is deliberate. It parks the order well under market so it sits open instead of filling on the spot, which is what you want while you are still confirming the connection. Schwab equity symbols are plain tickers, intc or aapl, with no separator, the same as most US stock and ETF brokers on Autoview.

Check the Autoview log and your Schwab order screen. You should see one open limit order for a single INTC share.

Cancel it

Now clear it back out:

  • Extension: e=schwab a=my-schwab s=intc c=order
  • Webhook: s=intc c=order

Confirm the order disappears from both the Autoview log and your Schwab account. Placed, then cancelled, both confirmed. That is the full round trip, and your connection is sound.

If something goes wrong

  • Order rejected on syntax. Re-run with d=1 and read the log line by line. It tells you exactly how Autoview interpreted every parameter you sent.
  • Unknown symbol. Confirm the ticker is a plain Schwab symbol with no slash, dash, or exchange prefix attached.
  • Nothing happens at all. On the extension, Chrome has to stay open and the alert has to actually reach Autoview. On the platform, confirm the webhook is pointed at your own Autoview URL and, if you named your connection, that the webhook references it.
  • Connection shows expired or disconnected. OAuth2 tokens lapse. Reconnect through the same sign-in flow and approve access again.
  • Auth or account errors. Double check the command went to the Schwab connection you meant, by its name in a= on the extension or by the connection linked to the webhook. Whichever Schwab subscription you used, the order went to the Schwab account you signed in with.

Next steps

Connection tested and working? From here you can build out the commands that make automation worth running: limit and market orders sized off your account balance, order cancellation tied to a signal, and chained order legs sent from one alert. Build each one the same way you built the test, write it, dry-run it with d=1, then let it fire for real.

Set up Autoview