Skip to main content

Glossary

Simple explanations of technical terms you'll see in XeroLite documentation. If a word is unfamiliar, look it up here.

API (Application Programming Interface)​

What it is: A way for two programs to talk to each other. Think of it like a phone line between two people.

In context: XeroLite uses an API to talk to Interactive Brokers. This lets XeroLite send orders to your IB account.

Example: When you enable "API access" in TWS, you're opening a phone line so XeroLite can call IB and say "place this order."

TWS (Trader Workstation)​

What it is: Interactive Brokers' desktop program for placing and managing trades. It runs on your computer or server.

In context: XeroLite connects to TWS (or IB Gateway) to send orders. TWS must be running and configured for API access for XeroLite to work.

Example: You install TWS, turn on API settings, and leave it running. XeroLite then connects to it and submits orders when your TradingView alerts fire.

VPS (Virtual Private Server)​

What it is: A computer in a data center that you rent and use over the internet. It runs 24/7 and has its own IP address.

In context: XeroLite is often run on a VPS so TradingView can send alerts to it at any time, and so your home internet or power doesn't have to stay on.

Example: You rent a small Windows or Linux VPS, install XeroLite and TWS on it, and point your TradingView webhook to the VPS's address. Your alerts run even when your home PC is off.

Cloud Server​

What it is: A remote computer you use over the internet, usually rented from a provider. Same idea as a VPS.

In context: XeroLite documentation may say "cloud server" or "VPS"—both mean a remote machine where you run XeroLite so TradingView can reach it.

Example: "Use a cloud server so TradingView can send alerts 24/7" means run XeroLite on a VPS or similar hosted machine.

Port (Socket Port)​

What it is: A number that identifies which "door" on a computer a program uses for network traffic. Common examples are 80 (web) and 443 (secure web).

In context: XeroLite listens on a port (e.g., 80 or 443) for incoming TradingView alerts. TWS also uses a port for API connections.

Example: If your webhook URL is http://yourserver.com:8080/webhook, the port is 8080. That port must be open on your server and not blocked by a firewall.

Webhook / Webhook URL​

What it is: A web address (URL) that another service calls when something happens. When the event occurs, that service sends data to your URL.

In context: TradingView sends alert data to your XeroLite webhook URL. XeroLite receives the request and turns it into an order in IB.

Example: You set the webhook URL in TradingView to something like https://your-xerolite-server.com/webhook. When your alert triggers, TradingView "calls" that URL and XeroLite gets the alert.

JSON​

What it is: A standard format for sending data as text. It uses names and values in a structure that both humans and programs can read.

In context: XeroLite expects TradingView alerts in JSON. The Alert Request Builder and documentation show the exact JSON shape (fields like symbol, side, quantity).

Example: A simple alert might look like: {"symbol":"AAPL","side":"buy","qty":10}. That tells XeroLite to buy 10 shares of AAPL.

Localhost / 127.0.0.1​

What it is: A special address that means "this same computer." Programs use it to talk to other programs on the same machine.

In context: XeroLite connects to TWS on localhost when both run on the same machine. The TWS API port (e.g., 7497) is often set as 127.0.0.1.

Example: If TWS is on the same server as XeroLite, the API host is 127.0.0.1 and the port might be 7497 for paper or 7496 for live.

IP Address​

What it is: A unique number that identifies a device on a network or the internet, like a street address for a computer.

In context: Your XeroLite server has an IP address. TradingView uses that (or the domain name that points to it) in the webhook URL. IP whitelisting in XeroLite restricts which IPs can send alerts.

Example: If your server's public IP is 203.0.113.50, your webhook might be http://203.0.113.50/webhook. You can also use a domain name that points to that IP.

Firewall​

What it is: Software or hardware that blocks or allows network traffic. It decides what can connect to your computer or server.

In context: If your firewall blocks the port XeroLite uses, TradingView cannot send alerts to XeroLite. You may need to allow that port (e.g., 80 or 443) through the firewall.

Example: "TradingView says the alert was sent but XeroLite never received it" often means the firewall (or router) is blocking the port where XeroLite listens.

Paper Trading​

What it is: Trading with fake money in a broker's test environment. No real cash or real market impact.

In context: XeroLite can connect to IB's paper trading account. You use it to test alerts and orders without risking real funds.

Example: You create an IB paper account, connect XeroLite to it, and run TradingView alerts. Orders show up in TWS paper account but don't use real money.

Live Trading​

What it is: Trading with real money in your real broker account. Orders go to the real market.

In context: When XeroLite is connected to your live IB account, every order it sends is real. Use paper trading first to verify everything works.

Example: After testing on paper, you switch TWS to your live account and point XeroLite to it. From then on, alerts result in real trades.

Interactive Brokers / IB​

What it is: A brokerage firm. IB provides the trading platform (TWS/IB Gateway) and the API that XeroLite uses to place orders.

In context: XeroLite only works with Interactive Brokers. You need an IB account (paper or live) and TWS or IB Gateway with API enabled.

Example: "You need an Interactive Brokers account" means you must sign up at interactivebrokers.com and have TWS or IB Gateway set up for API access.

Order Execution​

What it is: The process of sending an order to the market and (if filled) turning it into an actual trade.

In context: XeroLite takes your alert, builds an order, and sends it to IB for execution. The Transactions page in XeroLite shows execution status.

Example: When your TradingView alert fires, XeroLite executes a market order—IB receives it and fills it (or tries to) according to market conditions.

Market Order​

What it is: An order to buy or sell at the best available price right now. It prioritizes speed over price.

In context: XeroLite often sends market orders from TradingView alerts so trades happen immediately at current market prices.

Example: Alert says "buy 10 AAPL." XeroLite sends a market order for 10 shares; IB fills it at whatever price the market is offering at that moment.

Limit Order​

What it is: An order to buy or sell only at a specific price or better. It won't fill unless that price (or better) is available.

In context: XeroLite can send limit orders when your alert format specifies a limit price. The order waits until the market reaches that price.

Example: You send "buy 10 AAPL at $150." That's a limit order. It only fills when AAPL is at $150 or lower.

Stop Order​

What it is: An order that becomes active (turns into a market or limit order) when the price reaches a certain level. Used for stop-losses or breakout entries.

In context: XeroLite supports stop orders when the alert format includes the right fields. Once the stop price is hit, the order is submitted.

Example: "Sell 10 AAPL if price drops to $145" is a stop order. When AAPL hits $145, the sell order is sent.

Combo Order​

What it is: A group of related orders that are submitted together (e.g., a main order plus a stop-loss and take-profit). Often called bracket orders.

In context: XeroLite can send combo (bracket) orders so one alert creates the main order and its protective legs (stop, target).

Example: One alert creates "buy 10 AAPL, stop at $140, target at $160." All three are linked as a combo order in IB.

TradingView​

What it is: A web-based platform for charts, indicators, and alerts. Many traders use it to build strategies and trigger alerts when conditions are met.

In context: XeroLite receives alerts from TradingView via webhook. You design your strategy and alert in TradingView; XeroLite turns those alerts into IB orders.

Example: You create an alert in TradingView that fires when price crosses a moving average, and set the message to JSON. That message is sent to XeroLite's webhook URL.

Alert​

What it is: A notification that fires when something you defined happens—e.g., price hits a level or an indicator condition is true.

In context: In XeroLite, "alert" usually means a TradingView alert. When it fires, TradingView sends a webhook request to XeroLite with the alert message (often JSON).

Example: Your TradingView alert is set to "Once Per Bar Close" with a message like {"symbol":"AAPL","side":"buy","qty":10}. When the bar closes and the condition is true, TradingView sends that to XeroLite.

Pine Script​

What it is: TradingView's programming language for writing custom indicators and strategies. You can use it to build the logic that triggers alerts.

In context: You can create alerts with or without Pine Script. Alerts "with Pine" use a script to format the message; "without Pine" use manual message templates.

Example: A Pine Script strategy can create an alert message that includes symbol, side, and quantity so XeroLite receives a ready-to-use JSON payload.

Account Number (acc_no)​

What it is: The identifier for your trading account at the broker. In XeroLite and alert JSON it's often called acc_no.

In context: XeroLite uses acc_no in the alert to know which IB account should receive the order. This matters if you have multiple IB accounts.

Example: Your alert JSON might include "acc_no":"DU1234567". XeroLite sends the order to that IB account.

Webhook URL (in XeroLite)​

What it is: The full address in XeroLite where TradingView should send alert requests. You copy this from XeroLite and paste it into TradingView's webhook URL field.

In context: You find the webhook URL in XeroLite under Webhook & Settings. It must be reachable from the internet (and often from TradingView's servers).

Example: Your XeroLite webhook URL might be https://your-server.com:443/webhook. Every TradingView alert that you want to use with XeroLite points to this URL.

IP Whitelisting​

What it is: A security feature that only allows requests from a list of approved IP addresses. Others are rejected.

In context: XeroLite can restrict incoming alerts to specific IPs (e.g., TradingView's). That way only trusted sources can trigger orders.

Example: You add TradingView's outbound IP ranges to the whitelist. If someone else discovers your webhook URL, their requests are blocked because their IP isn't on the list.

Rounding (Pricing Context)​

What it is: Adjusting a number to a allowed increment (e.g., to the nearest cent or tick). Exchanges and brokers require prices in specific steps.

In context: XeroLite rounds prices according to IB and exchange rules so orders are valid. The Price Rounding Rules doc describes how this works.

Example: You send a limit price of 150.1234. XeroLite rounds it to the allowed tick size (e.g., 150.12) before sending the order to IB.

Trailing Stop​

What it is: A stop order whose trigger price moves with the market in your favor (e.g., for a long, the stop trails below the current price). It locks in profit as price moves.

In context: If XeroLite and your alert format support trailing stops, you can send orders that include a trailing stop distance or percentage.

Example: "Buy AAPL with a trailing stop 2% below the high" means the stop price updates as the stock makes new highs, always 2% below that high.

Database Migration​

What it is: Moving or upgrading the data stored by a program (e.g., from an old version to a new one) so the new version can read it.

In context: When you upgrade XeroLite to a new major version, a migration may run to convert your existing data (settings, history) into the new format.

Example: The Migration Guide explains how to upgrade from an older XeroLite version and what happens to your data during the migration.

Read-Only Mode (API)​

What it is: A setting in the broker API that allows reading data (positions, account info) but blocks sending orders. Used for safety when testing or monitoring.

In context: In TWS/IB Gateway you can enable "Read-Only API." XeroLite could connect and read, but any attempt to place orders would be rejected.

Example: You turn on read-only in TWS to verify XeroLite can connect and see your account without risking any trades.

Socket / Socket Clients​

What it is: A way for programs to send and receive data over a network. A "socket client" is a program that connects to another program using such a connection.

In context: XeroLite uses socket connections to talk to TWS/IB Gateway. The API is built on top of sockets.

Example: When documentation says "socket clients must be allowed," it means TWS must be configured to accept API (socket) connections from XeroLite.

Order Replication​

What it is: Sending the same order (or same signal) to more than one account or destination.

In context: XeroLite does not replicate one alert to multiple IB accounts. Each alert targets one account (one acc_no). To trade the same signal in multiple accounts, you create separate alerts, each with its own acc_no.

Example: To trade the same strategy in two IB accounts, you set up two TradingView alerts with the same logic but different acc_no values; each alert goes to one account.

License Key​

What it is: A code (often a string of characters) that proves you're allowed to use the software. You enter it during activation.

In context: XeroLite requires a valid license key. You get a trial or purchase a license, then activate it in XeroLite using that key.

Example: After installing XeroLite, you go to the license/activation page, paste your license key, and click Activate. The software then runs in licensed mode.

Troubleshooting​

What it is: The process of finding and fixing problems—checking steps, settings, and logs to see why something isn't working.

In context: The XeroLite Troubleshooting guide walks you through common issues (alerts not received, orders not placed, connection errors) and what to check.

Example: If alerts aren't reaching XeroLite, troubleshooting steps might include: Is the webhook URL correct? Is the port open? Is the firewall blocking it?