Do I need a specific Content-Type header to send Autoview a command?

Set Content-Type explicitly rather than relying on a client's default. Plain text (or an unrecognized type) and application/json both work; form-encoded and multipart bodies, which some HTTP clients send by default, are rejected.

Can I send the command as JSON?

Yes. POST with Content-Type: application/json and a body that's either a bare JSON string or an object with a string "alert" field, for example {"alert": "s=BTCUSDT b=buy q=1 t=market"}. Any other JSON shape returns a 400.

How do I keep my webhook from being triggered by a stray request?

Set a webhook key. Send it as ?key=yourkey on the URL, or as the first characters of the body, which Autoview strips before reading the rest of the command. See the webhook key guide for both methods in full.

Can I dry-run a command sent from my own code?

Yes. Append d=1 to the command and Autoview logs the order it would have placed without sending anything to the exchange, the same as any other alert source.

Send custom webhooks to Autoview

Autoview · Signal source · Updated September 12, 2026

If you already have code that decides when to trade, a backtester, a custom indicator, a cron job, a bot running on your own server, it doesn't need TradingView, n8n, or Zapier in the middle. Anything that can make an HTTP POST can send Autoview a command directly.

What this is and who reaches for it

This is for developers and quants who want full control: no third-party workflow tool, no charting-platform alert engine, just your own program deciding what to trade and posting the result. If your signal already lives in a script or service you maintain, this is the shortest path from that code to a live order.

How to POST a command to Autoview

Every Autoview webhook has its own URL, shaped like https://api.autoview.com/hook/<identifier>/. POST your command as the request body, and set Content-Type explicitly, plain text or JSON both work, but a client's default (often form-encoded) is rejected:

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

# JSON body works too, if that's what your client sends by default
curl -X POST "https://api.autoview.com/hook/<identifier>/?key=yourkey" \
  -H "Content-Type: application/json" \
  -d '{"alert": "s=BTCUSDT b=buy q=1 t=market"}'

Both requests place the same order. JSON is there for a client that serializes bodies as JSON by default -- send the command wrapped in {"alert": "..."} instead of switching to a raw/text body.

The same call works from any language: Python's requests.post(), Node's fetch(), PowerShell's Invoke-WebRequest, or a plain socket if that's what your bot already uses. Autoview doesn't care what sent the request, only that the command arrives in the body.

If you set a webhook key, add it as ?key=yourkey on the URL, or as the first characters of the body instead, useful if your client can't easily add query parameters. See the webhook key guide for both methods. Test with d=1 appended to the command before you point real capital at it. Autoview logs the order it would have placed without sending it to the exchange.

What you can trade once connected

A custom POST can drive any exchange Autoview supports: forex through OANDA, futures through Tradovate, US stocks through Alpaca, TradeStation, or Schwab, and more than a dozen crypto exchanges including Kraken, Bybit, OKX, Coinbase, and Crypto.com. See the full list on the guides hub, and every command parameter on the command reference.

Other ways to send Autoview a signal

The same webhook accepts the same command format from TradingView, n8n, Zapier, or an AI agent talking to Autoview directly. See every intake surface on the signal sources page.

Create your free Autoview account