Latest information on the next steps for the TD Ameritrade Trader API as we bring an updated version of our API into Schwab’s ecosystem as a product offering for retail self-directed traders.  


What is the future state of the API?

As part of the Schwab integration, a retail Trader API will be made available at Schwab.  The goal is to provide an updated version of our current API capabilities in Schwab's ecosystem using Schwab’s authentication and account support systems. 

Although we are working diligently to ensure there are as few changes as possible, legacy TDA API app owners wanting to integrate into the new Schwab Trader API endpoints WILL need to make changes to their applications for integration.  Some of the changes will include:

  • New registration of a developer account and an application when the Schwab Developer Portal is live
    • Registration with the Schwab Developer Portal is required to interact with the Schwab Trader API
  • Token based authentication flow change
  • Saved Orders and Watchlist functionality of our legacy TDA API will not be available in the Schwab Trader API offering

There will be several communications sent throughout 2023 to everyone using the legacy TDA API to provide more information on progress and next steps.

What will happen with the current API?

The existing TD Ameritrade API will remain active throughout the brokerage account migration.  While brokerage accounts remain active at TD Ameritrade, and prior to their migration to Charles Schwab, they will continue to be able to access the TD Ameritrade API as they have today. Once an account is moved to Charles Schwab brokerage, such account will no longer be able to authenticate into the TD Ameritrade API. These migrated accounts would need to authenticate into the new Schwab Trader API endpoints once they become available.

For more information around brokerage account migration, here is a link to our integration hub:

What will be changing?

As part of the Schwab integration, a retail Trader API will be made available at Schwab.  There will be differences in the new Schwab Trader API endpoint as compared to the existing TDA offering. Some of the changes specifically for the Schwab API program will include the following:

  • A new Schwab Developer Portal account and application registration will be required when the Schwab Developer Portal is live
  • Updated token-based authentication flow
  • API endpoint resource URL changes (e.g., TDA to Schwab domain)
  • Saved Orders and Watchlist endpoints will not be available

What will remain the same?

Our goal is to keep actual API related contracts as similar as possible. Some API requests/responses will be simpler than before.  Here are some things that are expected to stay the same:

  • Quotes for both snapshot and historical market data
  • Active account and transaction data monitoring
  • Ability to place orders for stocks, options, and ETFs
  • Futures, Futures options, and Forex order entry will not be available
  • Streamer WebSocket based API including the QUOTE and ACCT_ACTIVITY subscriptions

When can I start integration?

The goal is to make developer and application registration available in early 2023 through the new Schwab Developer Portal.  Use of the API program with Schwab Trader API endpoints will require a new registration within this new Schwab Developer Portal.  No existing legacy TDA API external applications will be migrated over into the Schwab environment. 

Read-only documentation for the Schwab Trader API endpoints, along with the ability to interact with these endpoints, is currently planned for further out in 2023.  Actual integration into the different endpoints can begin once available.  As mentioned previously, the Schwab Trader API endpoints will require a Schwab retail self-directed brokerage account for authentication and interaction.  It is possible that a TDA brokerage account may not be migrated to Schwab brokerage before Schwab endpoints are live.  At launch, we will not be able to provide test endpoints and test accounts for pre-conversion integration.  These types of test environments may be considered for addition post integration.