Check the namespace before changing code
When I see cAlgo.API in a current C# sample, I keep it. That is still the official namespace for the cTrader Algo API.
cTrader API guide
cTrader API: Algo, Open API, and FIX explained
The phrase cTrader API can mean three different interfaces. This guide separates the Algo API used by cBots and indicators from Open API for external apps and FIX API for trading connections.
Direct answer
Use the cTrader Algo API when you are writing a cBot or custom indicator that runs in cTrader. Current documentation calls the environment cTrader Algo, while older material may say cAlgo or cTrader Automate and current C# code still imports cAlgo.API. Open API and FIX API solve different integration problems.
What to know first
- cTrader Algo is the current product name. cAlgo and cTrader Automate are older names that still appear in searches and code.
- The C# namespace is still cAlgo.API, so that import does not mean the sample is for a separate API.
- Open API connects an external application to the cTrader backend through JSON or Protobuf messages.
- FIX API uses the FIX 4.4 protocol for live market data and trading operations, with a deliberately limited message scope.
cTrader Algo API vs Open API vs FIX API
| Question | Algo API | Open API or FIX API |
|---|---|---|
| Where does the code run? | Inside the cTrader algorithm environment as a cBot, indicator, or plugin. | Open API code runs in an external app or service. FIX clients connect through the FIX protocol. |
| What interface does it use? | C# or Python objects documented in the Algo API reference. C# uses the cAlgo.API namespace. | Open API sends JSON or Protobuf messages. FIX API sends FIX 4.4 messages. |
| What is it best for? | Trading robots, technical indicators, and code that uses cTrader lifecycle and chart APIs. | Open API suits external trading apps and services. FIX API suits defined live price and order workflows. |
| Does Pineify generate it? | Yes, for one C# cBot or indicator source file compatible with cTrader.Automate 1.0.19. | No. Pineify does not currently generate Open API or FIX API clients. |
What the cTrader Algo API is
The cTrader Algo API is the library available to algorithms built for cTrader. A cBot derives from Robot, while a custom indicator derives from Indicator. The API supplies lifecycle methods, market data, order methods, chart objects, and account collections such as Positions and History.
Official cTrader Algo documentation now covers C# and Python, plus cBots, indicators, and plugins. Pineify has a narrower scope: it generates one C# source file for a cBot or indicator against cTrader.Automate 1.0.19.
How cAlgo, Automate, and Algo relate
These terms do not describe three separate coding APIs. Older tutorials commonly use cAlgo, later material uses cTrader Automate, and the current cTrader interface and help center use cTrader Algo.
The old name remains visible in C# code. Official current examples still use the cAlgo.API import and namespaces such as cAlgo.Robots. When reviewing an older sample, check the members against the current API reference instead of replacing the namespace name.
History and Positions in the Automate API
Positions is the collection of open positions available to an algorithm. It has search methods and events for opened, modified, and closed positions. A cBot can filter by label, symbol name, and trade type before it acts.
History is the collection of historical trades. It can find trades by label, symbol, trade type, position ID, or closing deal ID. It is not the same as the collection of open positions, so code should not use it to decide whether a position is currently active.
- Use Positions.Find or Positions.FindAll when the logic needs a currently open position.
- Subscribe to Positions.Opened, Positions.Modified, or Positions.Closed for position events.
- Use History.FindByPositionId when the logic needs completed trades tied to one position.
Where Pineify fits
Pineify turns a written cBot or indicator specification into editable cTrader C# and can check compiler diagnostics against its supported API contract. That is useful when you need correct lifecycle methods, parameter attributes, position filters, or indicator outputs in one source file.
The current workflow does not generate cTrader Python, plugins, multi-file projects, config.json, custom NuGet packages, DLL dependencies, Open API clients, or FIX clients. A successful compiler check confirms syntax and API compatibility only. It does not prove trading behavior, runtime safety, or profitability.
A practical way to choose the API
Start with where the code must run. Code that belongs inside a cBot or indicator uses the Algo API. A separate service, mobile app, or custom terminal that talks to the cTrader backend uses Open API. A system built around FIX messages for prices and orders uses FIX API.
If your goal is a C# cBot or indicator, describe the trading rule, symbol scope, timeframe, position limits, and risk inputs before generating code. Then review the source and test it in cTrader with data and settings that match your intended use.
Practical checks I use
Scope open positions
I filter Positions by a stable label and symbol before modifying or closing anything, so the cBot does not touch unrelated trades.
Separate open and completed trades
When I inspect closed trade behavior, I use History. I use Positions for trades that are open now.
Related cTrader pages
cTrader AI Coding Agent
Generate and revise C# cBots or indicators with compiler diagnostics.
cTrader cBot Builder
Turn an automated trading specification into an editable C# cBot.
cTrader Custom Indicator Builder
Build a C# indicator with parameters, output series, and chart logic.
cTrader Backtesting
Learn what a cTrader backtest can measure and what it cannot prove.
Primary sources
- Official cTrader Algo documentation
- Official cTrader Algo API reference
- Official History API reference
- Official Positions API reference
- Official cTrader Open API documentation
- Official cTrader FIX API limitations
Pineify is an information tool, not investment advice. Generated code and compiler checks do not promise returns or prove that a strategy is correct, profitable, or safe. Review the code, backtest it, and use a demo account before risking capital.
Frequently asked questions
More Pineify coding tools
cTrader AI Coding Agent
Generate single-file cTrader C# cBots and custom indicators, then review compiler diagnostics in the same coding workflow.
Try it
cTrader cBot Builder
Turn explicit entry, exit, position, and risk rules into editable single-file cTrader C# cBot source.
Try it
cTrader Custom Indicator Builder
Create editable cTrader C# custom indicator source for formulas, output series, and chart objects.
Try it
cTrader Backtesting Guide
Move from a reviewed cBot to cTrader backtesting while keeping compiler checks, test assumptions, and risk limits separate.
Try it
cTrader vs MT5
Compare cTrader C# and MetaTrader 5 MQL5 by language, automation model, testing workflow, and suitable project type.
Try it
Turn an Algo API idea into cTrader C#
Describe the cBot or indicator you need. Pineify generates one editable C# source file and checks compiler diagnostics within its supported cTrader.Automate 1.0.19 scope.
Open the cTrader Coding Agent