Skip to content

Schwab connection status

When the integration is approved and enabled, TickPro will use Schwab’s official OAuth flow:

Your Schwab username and password stay on Schwab’s page. TickPro receives an authorization token instead of the login credentials.

Schwab’s developer guide describes this as a three-legged OAuth flow: the user signs in to Schwab’s Login Micro Site, reviews consent, selects accounts, and returns to the third-party app.

Charles Schwab official diagram of the three-legged OAuth authorization flow
Schwab's official OAuth overview. TickPro keeps its Client Secret on the server, never in the app; the user flow will be much shorter than this developer diagram.Schwab Developer Portal ↗

Nothing is required. Wait until the Schwab page in TickPro changes from Coming soon to an active authorization button.

TickPro support will never ask you to send:

  • Your Schwab username or password
  • A trading PIN or verification code
  • An API client secret
  • A full account statement or unredacted screenshot