PyneCore Capital.com Plugin

Capital.com integration for PyneCore: historical and live market data plus live order execution over the public REST v1 + WebSocket API.

Status

Both the data provider (LiveProviderPlugin) and live order execution (BrokerPlugin) are implemented: session-based authentication, historical plus live OHLCV, and position-based order routing with server-side stop-loss / take-profit / trailing stop.

Architecture

• Transport: REST v1 (api-capital.backend-capital.com, or the demo host with demo = true) for account, orders, and history; WebSocket for live quotes and OHLC updates. Execution events are polled from REST (/positions, /workingorders, /history/activity) — Capital.com has no order-event WebSocket channel.
• Authentication: API key + email + API password. The plugin encrypts the password with the server-provided RSA key and keeps the session tokens refreshed proactively.
• Order model: position-based (dealId rows) with server-side stop-loss / take-profit / trailing stop as position attributes. One-way (netting) accounts use the direct execution path; hedging-mode accounts run through PyneCore's one-way emulation layer, so Pine one-way semantics hold on both.

Account-mode notes

• Hedging mode is detected at connect time (GET /accounts/preferences) and handled transparently: closes, reversals, and brackets are decomposed per position row by the core one-way emulator.
• Partial closes on a hedging account are not supported: DELETE /positions/{dealId} is full-row only (it ignores any size parameter), so a fractional strategy.close(qty=...) becomes a loud, non-halting skip. Use a one-way (netting) account for partial closes — there the plugin emulates them via opposite-direction orders.
• Deferred trailing activation (Pine trail_price + trail_points) is only available on netting accounts; on a hedging account the trailing stop arms immediately at the given offset (logged as a warning).

License

Apache-2.0. See LICENSE and NOTICE.