cTrader cBot Specification Checklist

The checklist

1. 1

   Define order ownership

   State whether the cBot manages only its own labelled positions and pending orders, one TradingView source, or every order on the account. Owned-only is the safe default.

2. 2

   Freeze the transport

   Identify whether instructions already reach cTrader through an existing connector, cTrader Open API or another authorized route, and preserve the exact non-secret event fields.

3. 3

   Choose the time basis

   Define server time, UTC or a named timezone such as Europe/London, including daylight-saving behavior for sessions and daily resets.

4. 4

   Specify initial protection

   State the reference price, pip or tick semantics, stop loss, take profit, rounding and broker minimum-distance behavior after a fill.

5. 5

   Define each transition

   Write the exact event that moves a position to break-even, trailing, partial close, time exit or another state. Separate one-shot events from continuous management.

6. 6

   Keep stops monotonic

   Decide whether an automated protective stop may only tighten and what happens if a trader manually loosens or removes it.

7. 7

   Handle daily controls

   Define start-of-day balance or equity, realized and floating P/L, deposits, withdrawals, the close/cancel sequence and how long new entries remain locked.

8. 8

   Prevent duplicates

   Require a stable source ID or idempotency key so replayed alerts, reconnects and retries cannot create a second unintended order.

9. 9

   Plan rejects and restarts

   Set bounded retry counts, terminal failure states and reconciliation rules for partial fills, rejected modifications, disconnections and cBot restarts.

10. 10

    Supply acceptance cases

    Provide at least one should-act and one must-not-act example for every state transition, including an ambiguous or out-of-scope order.

Common questions