Which broker should we support next? Vote 👍 #73
przemyslawbialon
started this conversation in
Broker support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Which broker should we support next? Vote 👍
pit-38 currently supports:
The community will drive what comes next. React with 👍 on the broker you'd most like to see supported, or drop a comment with your broker + a sanitized CSV snippet if it's not on this list.
Shortlist (by popularity of mentions so far)
Interactive Brokers (IBKR)
US-based, popular among more active Polish investors. Has an official CSV export via Flex Queries. Complex: multiple reporting formats (Activity Statement, Custom Flex).
Trade Republic
German broker, popular with younger EU investors. German-formatted CSV (comma decimal, dot thousand).
Exante
International broker popular in Poland. Already has a community-maintained tool (
wojteksbt/pit-exante) — we could port that as a native plugin.Degiro
Netherlands-based, big EU audience. Multi-language exports.
Kraken (crypto)
Major exchange missing from our lineup. Several users already use manual CSV workaround.
Coinbase (crypto)
Large US audience with Polish users. Historical CSV format changes.
How to help add broker support
Once the plugin API is formalized (see issue #49) and the cookiecutter template is published (see issue #50), adding a new broker should take about an afternoon for someone familiar with Python.
If you have a broker export that doesn't fit any of these categories, reply with:
We'll use community input to prioritize and either build it in-house or label it
good first issuefor a contributor.🔗 Related: issue #49 (plugin API), issue #50 (cookiecutter)
Beta Was this translation helpful? Give feedback.
All reactions