Core concepts

This page gives you the minimum mental model needed to read the command language correctly. It does not teach workflows or syntax details; it defines the terms.

Core rule

A valid request needs both:

1. the correct token in the URL
2. the correct bot name inside the payload

Essential terms

Term	Meaning
Connection	saved exchange setup inside the app
Bot name	name used inside the payload
Token	unique value in the webhook URL that routes to one saved connection
Symbol	market identifier, for example BTCUSDT
amount=	order size to send now
position=	final position size to target

Bot name and token

The token decides which saved connection receives the request. The bot name inside the payload must still match that same saved connection.

Symbol

Use one simple, consistent symbol style in your alerts and payloads.

Examples:

• BTCUSDT
• ETHUSDT
• SOLUSDT

Amount vs position

amount= controls the size of the order you are sending now.

type=market,side=buy,amount=0.001

position= controls the final position size you want after execution.

type=market,position=0.003

position=0 means end flat.

Sizing suffixes

Form	Meaning
25% or 25%b	percent of total balance or equity
25%a or 25%%	percent of available balance
50%p	percent of current position

The most important distinction is this:

• amount=50%p means order size based on the current position
• position=50%p means final target position based on the current position

Price forms

• @68000 means an explicit fixed price
• offset=1% means a relative price offset
• offset=e1% means an entry-relative offset

Command sequences

One payload can contain one command or several commands separated by semicolons.

ALPHA(BTCUSDT){
  type=market,side=buy,amount=0.001;
  wait(3s);
  type=limit,position=0,offset=1%,reduceOnly=true
}

Use this page with Read Signal format for exact wrapper syntax, then use Common tasks for copy-ready patterns.