2.6k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill ctrader-commander- _meta.json289 B
- endpoints.md5.0 KB
- SKILL.md7.5 KB
Overview
This skill places and manages cTrader orders and retrieves market and account data through a local HTTP proxy. It supports market, limit, and stop orders, live quotes, OHLC candles, open positions, and account balance/equity queries. No credentials are required at call time because the proxy loads them from a server-side .env file.
How this skill works
All requests go to a local REST proxy at http://localhost:9009 which wraps the cTrader OpenAPI connection. The proxy holds credentials and exposes endpoints for trading actions (POST /api/market-order), market data (POST /api/trendbars, POST /api/live-quote), and command passthrough (GET /get-data?command=...). You run the proxy locally once and then call the endpoints from scripts or tools without passing tokens.
When to use it
- Place or modify market, limit, or stop orders from automation scripts or a CLI.
- Fetch live quotes or recent OHLC candles for charting or signal generation.
- Query open positions, pending orders, or close positions programmatically.
- Check account balance, equity, or switch active account on the proxy.
- Run automated strategies that must not expose credentials at runtime.
Best practices
- Always query symbol IDs first; IDs are broker- and account-specific.
- Verify the proxy is running (ProtoOAVersionReq) before sending trade commands.
- Use volume in units (1000 = 0.01 lot) to avoid lot-to-unit conversion errors.
- Limit sensitive operations to trusted networks since the proxy controls live accounts.
- Include relativeStopLoss and relativeTakeProfit for market orders where applicable.
Example use cases
- Automated bot places a MARKET buy with a 0.01 lot and attaches SL/TP in pips.
- Backtester or analytics tool fetches M5 candles for the last hour via /api/trendbars.
- Monitoring script polls /get-data?command=ProtoOAReconcileReq to detect new positions.
- Manual script closes a position using ClosePosition <positionId> <volume> via the command passthrough.
- Retrieve current BID/ASK ticks for a symbol over the last 60 seconds using /api/live-quote.
FAQ
No. The proxy loads credentials from a server-side .env file so callers do not supply tokens.
How do I find the correct symbolId for my instrument?
Call GET /get-data?command=ProtoOASymbolsListReq and match symbolName to get the broker-specific symbolId.