Lots vs units in cTrader: what should TradingView send?
cTrader Algo execution volume is commonly expressed in units. cTrader's Symbol API exposes conversions between quantity in lots and volume in units plus minimum, maximum and step constraints. Choose one webhook convention and normalize before execution.
What this means in practice
cTrader Algo execution volume is commonly expressed in units. cTrader's Symbol API exposes conversions between quantity in lots and volume in units plus minimum, maximum and step constraints. Choose one webhook convention and normalize before execution. This page is specifically about “Lots vs units in cTrader: what should TradingView send?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — TradingView sends lots
Compare requested size with the cTrader symbol minimum, maximum and step. Convert to one canonical internal unit, normalize once, and log requested versus submitted volume. For Scenario A — TradingView sends lots on question 71, use that evidence specifically to answer “Lots vs units in cTrader: what should TradingView send?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — TradingView sends units
Compare requested size with the cTrader symbol minimum, maximum and step. Convert to one canonical internal unit, normalize once, and log requested versus submitted volume. For Scenario B — TradingView sends units on question 71, use that evidence specifically to answer “Lots vs units in cTrader: what should TradingView send?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Risk engine calculates units
Compare requested size with the cTrader symbol minimum, maximum and step. Convert to one canonical internal unit, normalize once, and log requested versus submitted volume. For Scenario C — Risk engine calculates units on question 71, use that evidence specifically to answer “Lots vs units in cTrader: what should TradingView send?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- symbol metadata and unit conversion
- configured risk or management rule
- broker min/max/step or distance constraint
- normalized value actually sent to cTrader
Practical rule
For “Lots vs units in cTrader: what should TradingView send?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: cTrader Algo execution volume is commonly expressed in units. cTrader's Symbol API exposes conversions between quantity in lots and volume in units plus minimum, maximum and step constraints. Choose one webhook convention and normalize before execution.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.