cTrader Trade Sync
cTrader Trade Sync retrieves provider trade history and writes trade notes into your Obsidian vault. Authorisation takes place on cTrader, not inside the plugin. Journalit requests read-only account access and cannot place, modify, or close orders.
Limited preview
cTrader Sync is not generally available. Connect only when the integration is enabled for your Journalit account. Provider authorisation and statement reconciliation must pass staging acceptance before a wider release.
Before you connect
You need Journalit Pro, a cTrader ID with access to the trading accounts you want to synchronise, and the Journalit plugin signed in to the same Journalit account as the website. No cBot or trading password is required by Journalit.
Connect and select accounts
Authorise on the website
Open Dashboard → Integrations → cTrader on Journalit.co and choose Connect cTrader. On cTrader's authorisation screen, review the read-only permissions and choose the accounts Journalit may access.
Choose your history
After returning to Journalit, enable the accounts you want to sync. Choose all available history, a start date, or new trades from the connection date. History can be widened, but not narrowed after the first successful sync. Demo and live accounts remain separate.
Map accounts to your vault
In Obsidian, open Journalit settings → Trade Sync → cTrader. Map each enabled account to a local journal account, then save and synchronise. Use Sync now on the website to retrieve provider data, or the plugin's sync action to retrieve data and write the resulting notes into your vault.
What synchronisation does
The first backfill retrieves available history. Later syncs merge overlapping updates with encrypted provider evidence already stored by Journalit. Periodic full reconciliation checks for older changes. Realised profit, commission, swap, and conversion fees come from cTrader's accounting, not price estimates.
The backend can retrieve trades while Obsidian is closed, but it cannot write into a closed vault. On opening Obsidian, the plugin checks for pending trade projections and continues checking while it is running. An open position is not treated as a completed trade; its realised costs and partial closes are preserved.
Preview limitations
- An authorisation callback without a verified returned state is rejected. If authorisation cannot complete, contact support rather than repeatedly reconnecting.
- Instrument classification uses cTrader's asset-class metadata. Classification observed before a symbol is archived is retained. A symbol already archived before the first sync may lack that metadata. Journalit stops synchronisation for the connection rather than guessing its asset type or silently omitting trades.
- If the provider reports more deals within a timestamp boundary than it can return completely, Journalit rejects the incomplete history instead of treating it as a successful backfill.
- Compare the preview against a cTrader statement, especially for reversals, partial closes, overnight swap, and non-account-currency instruments.
Data storage and removal
Journalit stores encrypted OAuth tokens and encrypted history checkpoints on its backend. Checkpoints contain the deal, offset, account, and symbol information needed to reproduce the synchronised trades. Normalised execution evidence, trade projections, selections, delivery acknowledgements, and operational records are also stored server-side. Your note text and local journal edits stay in the vault.
Disconnect stops synchronisation and deletes the connection's OAuth tokens. It preserves stored history and existing notes. Delete cloud data removes the connection's history checkpoint and account selections, and removes trades that have no other active source. Shared canonical execution evidence and audit records are not the same as connection-owned cloud data and can remain after this action. See the Privacy Policy for the retention distinction. Neither action deletes your Obsidian notes.