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

Webhook order limits

Autoview · Guide · Updated November 13, 2026

Webhook order limits put a ceiling, in US dollars, on each live order your webhook alerts send. The alerts can come from TradingView, your own code, a workflow tool or anything else that posts to your webhook URL. With limits on, Autoview works out each order's size before it goes to the exchange. An order larger than your limit is held and not sent, and your event log says why.

Limits are optional and off by default. Nothing changes for your alerts until you turn them on.

This page comes from the Autoview website and server code that runs today. We read the code; we did not send these orders live for this guide.

Turn them on

Go to Account, Webhooks, Webhook order limits and open Turn on webhook order limits. Enter two amounts in USD:

  • Max order size. The largest single order an alert may send. This is the limit Autoview checks.
  • Daily total. Required to turn limits on, and saved, but not enforced yet. Autoview does not count your webhook orders across the day today, so this number does not stop anything.

Each change asks for your passphrase. If your account has no passphrase, ask for a one-time code by email and enter it in the form instead.

To turn limits off, open Turn off. That deletes your limits, including every limit per exchange, and your alerts go out without them again.

Limits per exchange and per symbol

Once limits are on, a second section, Limits per exchange, lets you set a smaller max order size for one exchange, or for one symbol on that exchange. Leave the symbol blank to cover the whole exchange. Saving the same exchange and symbol again replaces that limit, and it has to fit inside your max order size above.

For an order on a symbol with its own limit, the symbol limit is used before the exchange limit. Symbols are matched the way your alert writes them, so BTCUSD and BTC/USD count as different symbols. Write the symbol the same way your alerts send it.

How the size of an order is worked out

Autoview multiplies your q= quantity by your fp= limit price. If the order also has an fpx= trigger price above the limit, the trigger price is used. On a sell, where the exchange connection can report a current price, the current bid is used when it is higher than both. A sell limit set far below the market still counts at roughly what it would fill for.

Limits do not apply a contract size. On an exchange where a plain q= number counts contracts, such as BitMEX or KuCoin Futures (where it counts lots), q= times the price is not what the order is worth in dollars. The figure the limit checks can be far larger or far smaller than the real size, depending on what one contract holds. Look up the contract size for that market before you rely on a limit there.

What gets held while limits are on

An order is sent only if its size in dollars can be checked first. These are held and not sent, even when they would be small:

  • Market and stop orders (t=market, t=stop). Use a limit order with an fp= price.
  • Alerts with no fixed price. An order with no fp= limit price, or with a relative one such as fp=-1%, which is not a fixed number Autoview can multiply.
  • Percent and currency amounts. q=50%, or no q= at all, which means 100%. Also u=currency, where q= is an amount of money. Use a number of units, for example q=0.01.
  • Futures on Tradovate, and continuous contract symbols such as ES1!, because the contract size is not applied.
  • Markets not quoted in USD or a USD stablecoin, for example a pair quoted in EUR or BTC. The symbol is read as your alert writes it, and it has to end in USD or a USD stablecoin such as USDT or USDC. A contract name with anything after the quote, such as KuCoin Futures' XBTUSDTM, is held for that reason. On a stock broker, the symbol has to be a plain ticker such as AAPL.
  • Lines limits cannot read, such as a line with no s= symbol, or & sections that limits cannot count on that exchange.

If Autoview cannot read your limits at the moment the alert arrives, the order is held rather than sent unchecked. Send the alert again a minute later.

So if your strategy sends market orders or percent amounts, turning limits on stops those alerts from trading. Change the commands first, or leave limits off.

What is not checked

  • Lines with d=1. A dry run places no live order, so it is never counted or held.
  • Lines that manage what you already have rather than open something new: c= cancel and close lines and b=flat.
  • Alerts that run as a dry run for another reason, for example an exchange with no active subscription.

When an order is held

The exchange gets nothing for that alert. Your event log gets an entry that starts with Webhook order held and not sent, shows the line as it arrived, a code, and what to change. For an order over your limit, it gives the order's size in USD, how that size was worked out, and the largest q= that fits at that price. For a held market or percent order, it names the setting to change.

If the alert has several lines, the whole alert is held, not just the line that failed, and the entry says which line it was. See reading your log for where to find these entries.

An example

e=kraken s=BTCUSD b=buy q=0.01 fp=60000

That order is 0.01 times 60,000, or 600 USD. With a max order size of 500 USD it is held, and the log tells you that q= can be at most 0.00833333 at that price. The same line with t=market instead of fp=60000 is held whatever the size, because there is no price to check it against.

Send the line with d=1 first to see the order Autoview would place. Limits skip dry runs, so a dry run shows the order, not the limit check.

What webhook order limits are not

  • Not a daily cap. The daily total is saved but not enforced yet.
  • Not a stop loss. Limits look at the size of one order before it is sent. They do not watch your losses or close positions. For that, see stop loss, take profit and trailing stop.
  • Not the AI agent caps. Agent tokens have their own caps on the MCP tokens page, described in Autoview limits. Webhook order limits do not apply to agent orders, and the agent caps do not apply to your webhook alerts.

Open webhook order limits