How does algo trading software execute trades automatically?

1. The signal fires

Your own code checks prices, or a charting tool such as TradingView evaluates an alert condition on each bar. Nothing is ordered yet.

2. The message

The signal becomes text. A webhook is an HTTP POST of that text to a URL. The fields that matter are the ticker, the side, and open or close; options add expiry, strike and call or put.

3. The receiver

A program is listening on that URL. It reads the message, checks your rules such as the symbols you allow, and builds a broker order.

4. The broker's API

The order goes to the broker over HTTPS with your account's access token. Charles Schwab, Tradier, tastytrade and Alpaca each publish an API, and each answers with an order id.

5. Fill tracking

The receiver watches the order until it fills, is canceled or is refused, and records the result. The exit later needs to know what is open.

A misread message

A sell that was meant to close a position is read as a new short, or the wording names no trade at all. Test the exact message before real money depends on it.

An expired login

Broker access expires. Schwab ends Nyria's access every 7 days, and you reconnect with the same sign-in. A receiver that ignores this fails on the day the token lapses.

A receiver that was not listening

Most senders post once and do not retry, so an alert that arrives while the receiver is down is gone.

A repeat

A sender that retries after a timeout can deliver the same alert twice. A receiver needs a rule for duplicates.

An order that rests

A limit order below the market can sit unfilled. The receiver has to track it rather than assume it filled.

Nyria covers links three to five. It listens on a webhook URL per strategy, or reads a Discord server or Telegram chat that you run, and it reads any alert wording or JSON. A bot then places the order at Charles Schwab, Tradier, tastytrade or Alpaca, and the Logs tab records each alert and what happened to it.

A reply of 200 from the webhook means Nyria read the alert and handed it to your bots. It does not mean the broker filled anything. The bot's Logs tab shows what the broker did, and the broker's own order history is the final check. An identical body sent twice in quick succession is treated as a duplicate and trades once.

An alert cannot set the order size. The bot sets it from the budget per entry you choose, and Nyria attaches no stop order to an entry, so an exit alert or your own action closes the position. Paste a message into the alert tester to see how it will be read.

Nyria Paper simulates the broker, so links one to four can be checked with no account connected. Run real alerts for a week or two, read the Logs tab, and look for the failures above. Paper fills pay the quoted spread and never slip, so live fills can differ. Then deploy a bot on a broker account and reconcile against its order history.

Does the software watch the market all day?

The signal side does: a chart evaluates the condition and fires the alert. The receiver only acts when a message arrives.

How do I know an order really filled?

Open the broker's own order history. A 200 from the webhook only shows the alert was received and handed to a bot.

What does it cost?

Paper is free. Live trading from $15 a month.