Invite-only TradingView scripts after November 1: what buyers and sellers can do

Autoview · Guide · Updated October 9, 2026

TradingView is moving paid access to invite-only scripts into its Marketplace. Its September 30 announcement says that selling access to an invite-only script, "or providing that access as part of another paid product or service, will no longer be permitted starting November 1, 2026."

This page has two halves. The first is for you if you bought access to a script and you automate its alerts. The second is for you if you wrote the script and your customers automate it. Autoview is an execution tool. It isn't a party to any of this, and nothing here is legal advice. Read TradingView's Terms of Use yourself.

If you bought a script: what happens on November 1

Here is what TradingView itself has said, quoted from its own pages:

  • Section 23 of the Terms: "Scripts available for Commercial Use are only permitted to be distributed via the Marketplace."
  • What you already paid for: customers who paid before November 1 "can keep using it for the period already purchased, including lifetime access."
  • Renewals: after that date, vendors may not take new payments outside the Marketplace to renew, extend or maintain access. Vendors who keep doing so without contacting TradingView "will have their invite-only scripts blocked."

What none of that tells you is whether your own setup keeps running. That depends on your seller, and Autoview can't see it from here. So check in with your seller, ideally before November 1.

Ask your seller these

  • Are you moving to the Marketplace? If yes, ask when, and whether your current access carries over or you buy again there.
  • If not, where does the strategy go? Some sellers plan to run their logic on their own servers or another platform. Ask how signals will reach you after the move, and in what format.
  • What does my renewal look like? If your access is monthly or yearly, find out how the next payment will be taken before the date arrives.
  • Can I get a sample of the new signal? A real message from the new setup, not a description of one. You need it to build and test your Autoview command.

The older pre-purchase checklist still applies. It's in can I automate a purchased trading strategy?, and covers source visibility, placeholders, repainting and symbol mapping.

Protect your setup in the meantime

  • Keep your keys to yourself. Your exchange keys belong in your own Autoview account, scoped to trading and reading, never withdrawal. No seller needs them. See are my API keys safe?
  • Know your command. Write down the Autoview command your alert sends today. If the signal source changes, that command is what you rebuild around.
  • Dry-run the new source first. Whatever replaces the old alert, run its first messages with d=1 before any real order goes out. More on that below.

If you sell a script: run the logic off TradingView

If your strategy stops living in an invite-only script, its signals still need a way to reach your customers' brokers. Autoview doesn't need TradingView in the middle. Any program that can make an HTTP POST can send an Autoview webhook a command, from a server you run, a cron job, a backtester or a bot. The custom webhooks page shows the request in full.

Each customer gets their own webhook

Your customers each open their own Autoview account, connect their own exchange or broker, and create their own webhook. Autoview gives every webhook its own URL, shaped like https://api.autoview.com/hook/<identifier>/. The customer sends you that URL, plus a webhook key if they set one.

Your system then sends each customer's command to that customer's URL. One request reaches one webhook. Autoview does not copy a single signal across many accounts for you, so if you have fifty customers, your system sends fifty requests.

You never hold anyone's exchange keys. The customer can also cut you off at any time by changing the key on their webhook. Autoview starts requiring the new key the moment they save it.

The command you send

The body of each request is a normal Autoview command, the same syntax every other sender uses:

curl -X POST "https://api.autoview.com/hook/<identifier>/?key=customerkey" \
  -H "Content-Type: text/plain" \
  -d "s=BTCUSDT b=buy q=1 t=market d=1"

Every parameter, including stops and take profits, is in the command reference. Agree the exact format with each customer before the switch, including the size, since it's their account the order lands in.

If your customers use an AI assistant

Autoview also runs an MCP server, so an assistant like Claude can work with a customer's Autoview account through typed tools. It can look up a webhook's URL, build the command text, and place a dry-run order. It's in early access. Read the MCP overview or trading with an AI agent for what it covers today.

Test with d=1 and a practice account first

Moving a strategy to a new signal source is exactly when a wrong symbol or a mistyped size slips in. Test in two steps.

First, dry-run. Add d=1 to a command and Autoview parses it, works out what it would have done, and writes that to the log. No order goes to the exchange. It covers only the line it's on, so put it on every command you test. The testing and debugging guide walks through reading that log.

Then, a practice account. Once the dry-run looks right, remove d=1 and point the same command at a free demo or testnet account before real money. Autoview has setup guides for several:

When the practice fills match what the dry-run showed, move to the live account at a small size and watch the log and the exchange side by side.

What this page doesn't cover

Autoview doesn't vet strategies, sellers or signals, and it makes no claim about results. It places the orders the commands tell it to. Trading carries risk of loss, and you're responsible for the strategy you choose to automate. See our disclosures.

See how a custom webhook works