Built-in templates

BXP ships working templates for several brokers, targeting both Wealthfolio and brycht.app. They are what a template happens to describe here, not what templates are for — see what a template is. Use one directly, or pattern-match against the closest one when authoring a new template.

Template ID	Converts
anycoin_to_wealthfolio	Anycoin (crypto) -> Wealthfolio
revolutx_to_wealthfolio	Revolut X (crypto) -> Wealthfolio
trading212_to_wealthfolio	Trading 212 -> Wealthfolio
xtb1_closed_to_wealthfolio	XTB closed positions, old export -> Wealthfolio
xtb1_cash_to_wealthfolio	XTB cash operations, old export -> Wealthfolio
xtb2_closed_to_wealthfolio	XTB closed positions, new export -> Wealthfolio
xtb2_cash_to_wealthfolio	XTB cash operations, new export -> Wealthfolio
anycoin_to_brychtapp	Anycoin (crypto) -> brycht.app tracker
revolutx_to_brychtapp	Revolut X (crypto) -> brycht.app tracker
trading212_to_brychtapp	Trading 212 -> brycht.app tracker
xtb2_cash_to_brychtapp	XTB cash operations, new export -> brycht.app tracker
xtb2_closed_to_brychtapp	XTB closed positions, new export -> brycht.app tracker

Template ids read <source>_to_<target>, so an id names both ends of the conversion, and bxp-cli --template <id> runs exactly one of them.

The shipping templates live in bxp-cli.examples.json — next to the bxp-cli binary in the console archive, inside the app bundle on desktop, and at resources/console/bxp-cli.examples.json in the GitHub repository. Each carries inline JSON5 comments documenting what every $variable represents and how the source's own vocabulary maps — they are the canonical reference for new templates.