Is the TD Ameritrade API Still Available? What Replaced It, and What to Do Now

Is the TD Ameritrade API Still Available?

It is not. The endpoints stopped serving requests after market close on May 10, 2024, at the same time the last TD Ameritrade accounts finished moving to Charles Schwab. There is no read-only mode, no grandfathering for existing keys, and no separate maintenance window that ended. The service is retired.

This catches people out because the internet did not update with it. Tutorials, Stack Overflow answers, YouTube walkthroughs and a good deal of library documentation still describe the old API in the present tense. If you followed a guide and got authentication errors or empty responses, the guide is simply older than the shutdown.

What Happened, in Order

What Replaced It: the Schwab Trader API

The successor is the Charles Schwab Trader API. It covers the same ground in broad terms: account data, market data and order submission for US markets, over a REST interface using OAuth 2.0 rather than the older scheme.

It is a different product rather than a renamed one. Endpoint paths, authentication and the registration process all differ, so porting is real work rather than a search and replace on a base URL.

Whether it is the right thing to build on is a separate question from whether it replaced TD Ameritrade. There is a fit checklist at Schwab API for Traders: Costs and Real Limits, and a cost comparison against the alternatives at Schwab Trader API Cost vs IBKR and Alpaca: What Retail Technical Traders Actually Pay.

Your Old Application Was Not Migrated

This is the part that surprises people who assumed continuity. Applications registered on the TD Ameritrade developer portal were not carried over into the Schwab Trader API. There was no automatic transfer of app registrations, client IDs or approved callback URLs.

Registering again on Schwab's developer portal is a step with its own review, so it is worth starting before you need it rather than the week you planned to ship. Treat the old credentials as gone rather than dormant.

The same applies to anything built on top. Community libraries written against the TD Ameritrade endpoints stopped working on the same day, and a library being installable is not evidence that the service behind it still answers.

What Actually Changed for a Technical Trader

If You Only Wanted Chart Data, Reconsider the Broker API

It is worth separating two jobs that the old API used to do together. One is placing and managing orders, which genuinely requires a broker connection. The other is getting price history onto a chart so you can mark it up, which does not.

A large share of people who used the TD Ameritrade API were doing the second job. If that is you, a broker application review is a lot of process to sit through for candles, and it ties your charting to whichever broker you happen to hold an account with.

A market-data account is usually the shorter path for that, and several crypto venues publish data openly with no account and no key at all, covered at Crypto Charts With No API Key: Binance, Coinbase, Kraken. The current list of what connects is at Data provider fit.

If Schwab Is Not the Answer for You

Migrating to the successor is the default, not the only option. Traders who left TD Ameritrade for reasons beyond the API often end up comparing brokers rather than porting code.

The two most common alternatives among technical traders are Interactive Brokers and Alpaca, and they differ enough that the choice is rarely close once you write down what you actually need. There is a direct comparison at IBKR vs Schwab Trader API for Technical Traders and a three-way version at IBKR vs Alpaca vs Tradier: Costs, Limits, Data Gaps.

One caution worth stating plainly, since this is the second migration in the space in a few years: whatever you pick, keep your own analysis in a form you can carry. Levels, notes and annotations that live only inside one vendor's platform are the part you cannot port when the vendor changes.

What to Do Next

• Confirm the failure you are seeing is the shutdown and not a credential problem, by checking whether any call succeeds at all.
• Decide which job you actually need: order placement, or price history for charting. They have different answers.
• If you need order placement, register a new application on Schwab's developer portal and budget for review time.
• If you need chart data, price a market-data account against the broker route before committing.
• Move your annotated analysis somewhere exportable, so the next platform change costs you a connector rather than your work.

Where MyLinedChart Fits

MyLinedChart is the charting side of that split. You connect your own broker or market-data account with your own keys, including a Schwab account using an application you register yourself, and your credentials stay on your device rather than passing through anyone else's servers. It is read-only: it reads your chart and marks it up, and it never sends an order.

The reason it is relevant to a migration article is the last point above. Every drawing, level and note is exportable as structured data, so a broker change costs you a reconnection rather than a rebuild of your own analysis.

Is the TD Ameritrade API still available?

No. It stopped serving requests after market close on May 10, 2024, when the last TD Ameritrade accounts finished migrating to Charles Schwab. It is retired rather than paused.

What replaced the TD Ameritrade API?

The Charles Schwab Trader API. It covers account data, market data and order submission for US markets over REST with OAuth 2.0, and it is a separate product rather than a rename, so porting is real work.

Do I need to register a new application with Schwab?

Yes. TD Ameritrade app registrations, client IDs and callback URLs were not transferred. You register again on Schwab's developer portal, and that registration is reviewed, so start it before you need it.

Why do TD Ameritrade API tutorials and libraries still exist?

Because the acquisition and the shutdown were about four years apart, so a great deal of material was written while the API was current and was never updated. A library being installable does not mean the service behind it still answers.

Do I need a broker API at all if I only want to chart and annotate?

Often not. Order placement needs a broker connection, but price history for charting does not. A market-data account is usually a shorter path, and several crypto venues publish data openly with no account and no key.