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

Tradovate OAuth app registration errors: why the form will not save

Autoview · Guide · Updated November 2, 2026

If you build software that signs people in with their Tradovate account, you register an OAuth2 application with Tradovate first. Tradovate then issues a client ID and a client secret for it. Tradovate told us this registration is self-service, with no approval step on their side.

We registered one ourselves and the form would not save. Tradovate support found the cause, and it is easy to hit. This page explains it, lists the name rules they gave us, and says what you can leave unchanged.

What the failure looks like

We opened the Tradovate web platform, went to Application Settings, then the API Access tab, then OAuth Registration. We entered an application title, one redirect URI and no logo, and clicked save. Tradovate answered with "Internal Server Error" and did not save the application.

The message says nothing about the name, which is why this one is hard to spot. Nothing else on the form was wrong.

The cause: a deleted application keeps its name

Tradovate support traced it to the application name. In their words, the login we were registering under "already has an earlier, deleted application named Autoview, and a deleted application keeps its name reserved, so saving a new one called Autoview fails."

So deleting an application does not free its name. If you deleted an earlier attempt and then tried again with the same title, this is the likely reason the save fails.

The fix: save under a different name

Give the application a name the login has never used before. Tradovate's suggestion for us was to add a word, for example "Autoview OAuth" instead of "Autoview".

Changing only the capitalization does not help. Tradovate said "any capitalization of Autoview will hit the same error", so "autoview" and "AUTOVIEW" are still reserved.

Name rules

RuleWhat Tradovate support said
Allowed charactersLetters, numbers and single spaces
LengthUp to 64 characters
Deleted namesStay reserved, in any capitalization

These rules come from Tradovate support's reply to us on November 2, 2026. We did not find them in NinjaTrader's OAuth documentation when we checked that day, and Tradovate can change them, so trust Tradovate if it ever tells you otherwise.

What you can keep as it is

Tradovate reviewed the rest of our form and accepted all of it: "Your redirect URIs, permissions, market data setting, logo and links were all accepted, so you can keep those as they are." Only the name had to change.

One more thing to keep exact: the redirect URI. NinjaTrader's OAuth documentation describes it as "A redirect URI you control, registered with your credentials." Your app then sends users to https://trader.tradovate.com/oauth and exchanges the returned code at https://live.tradovateapi.com/auth/oauthtoken. Use the same redirect URI, character for character, that you registered.

When the save works, Tradovate gives you a client ID and a client secret. NinjaTrader's documentation says to keep the secret out of client-side code and public repositories.

If the new name still fails

The reserved name is the one cause Tradovate has confirmed to us. If a fresh name that follows the rules above still fails, we cannot tell you the cause from outside. Contact Tradovate support with the time of the attempt and the error you saw, the same way we did.

If your trouble is signing in to Tradovate from TradingView's broker panel rather than registering an application, that is a different set of errors. The Tradovate login errors guide covers them.

You may not need your own application

Registering an OAuth application makes sense when you are building a product for other Tradovate users. If you only want your own alerts to place Tradovate orders, you can skip it.

Autoview connects to Tradovate with the key from your API Access tab: your Tradovate username and password, plus the CID and Secret. It takes a webhook from any system that can send one and turns it into an order. The Tradovate API key guide shows where each value comes from, and the API access requirements guide covers who Tradovate lets create a key.

FAQ

Why does Tradovate's OAuth Registration form fail to save?

One cause Tradovate support has confirmed: the application name is reserved. If the login you are registering under once had an application with that name and it was deleted, the name stays reserved and saving a new application with it fails. Choose a different name.

What names does Tradovate accept for an OAuth application?

Per Tradovate support: letters, numbers and single spaces, up to 64 characters. A name used by a deleted application on the same login stays reserved in any capitalization.

Do I have to re-enter my redirect URIs and permissions after renaming?

In the case Tradovate reviewed for Autoview, the redirect URIs, permissions, market data setting, logo and links were all accepted. Only the name had to change.

Do I need my own Tradovate OAuth application to automate orders?

Not to use Autoview. Autoview connects to Tradovate with your username, password, CID and Secret from Tradovate's API Access tab, and turns a webhook from any system that can send one into an order.

Connect Tradovate