pytrpp: Download TradeRepublic files and export data to Portfolio Performance
This is a library for the private API of the Trade Republic online brokerage. This package and its authors are not affiliated with Trade Republic Bank GmbH.
Files can be produced to import orders and other transactions into Portfolio Performance: An open source tool to calculate the overall performance of an investment portfolio - across all accounts - using True-Time Weighted Return or Internal Rate of Return. https://www.portfolio-performance.info/. The package authors are not affiliated with Portfolio Performance.
This package is based on the source of pytr (https://github.com/pytr-org/pytr) originally by marzzzello.
Installation
Install release from PyPI with pip install pytrpp
Or install from git repo like so: pip install git+https://github.com/MartinScharrer/pytrpp
Usage
Recommended usages:
pytrpp [-n PHONE_NO] [-p PIN] -D TARGET_DIR
If either phone number or PIN is left out a prompt is generated for it.pytrpp -C CREDENTIALS_FILE -D TARGET_DIR
The credentials file consists of up to two lines with the phone number followed by the PIN. For security reasons the PIN can be left out or be an empty line from the credentials file. It must then be entered using the prompt.
Full usage information:
usage: pytrpp [-h] [-v {warning,info,debug}] [-V] [-n PHONE_NO] [-p PIN]
[-l LOCALE] [-D DIR] [-K COOKIES_FILE] [-C CREDENTIALS_FILE]
[-E EVENTS_FILE] [-P PAYMENTS_FILE] [-O ORDERS_FILE]
[-F DOCS_DIR] [-d DAYS | -s DATE | -r FILE] [--workers WORKERS]
Use "pytrpp command_name --help" to get detailed help to a specific command
options:
-h, --help show this help message and exit
-v {warning,info,debug}, --verbosity {warning,info,debug}
Set verbosity level (default: info)
-V, --version Print version information and quit
-n PHONE_NO, --phone_no PHONE_NO
TradeRepublic phone number (international format)
-p PIN, --pin PIN TradeRepublic pin
-l LOCALE, --locale LOCALE
Locale setting (e.g. "en" for English, "de" for
German)
-D DIR, --dir DIR Main directory to use. Special path can be set using
the following options.
-K COOKIES_FILE, --cookies-file COOKIES_FILE
Cookies file
-C CREDENTIALS_FILE, --credentials-file CREDENTIALS_FILE
Credential file
-E EVENTS_FILE, --events-file EVENTS_FILE
Events file to store
-P PAYMENTS_FILE, --payments-file PAYMENTS_FILE
Payments file to store
-O ORDERS_FILE, --orders-file ORDERS_FILE
Orders file to store
-F DOCS_DIR, --docs-dir DOCS_DIR
Directory to download files to
--workers WORKERS Number of workers for parallel downloading
Date Range:
Control date range to include (mutually exclusive):
-d DAYS, --last-days DAYS
Number of last days to include
-s DATE, --since DATE Include only entry since this date
-r FILE, --since-ref FILE
Include only entry newer than the modified date of
this file
Authentication
Currently only web login (simulating a browser) is supported.
The phone number and the PIN must be provided. A login code is then generated as second factor on the connected smartphone which also needs to be entered. The login can be buffered using a cookie file, so multiple runs will only require the login code once until the cookie expires.
Metadata
Release files for pytrpp 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pytrpp-0.4.2.tar.gz | 23.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytrpp-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.1 kB
Release files / pytrpp-0.4.2.tar.gz
| Download URL | pytrpp-0.4.2.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2be0d0dc5572d4040ebe2b8f9c61f29b8c04ade26243c71d8b9b588ac667d7bc
|
|
BLAKE2b-256 checksum How to use checksums |
0325eff0954abd26daf74bd8288b3cebdad262bb1f767838fcd3f6eace598688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 17, 2025.
Transparency logRelease files / pytrpp-0.4.2-py3-none-any.whl
| Download URL | pytrpp-0.4.2-py3-none-any.whl |
|---|---|
| Size | 23.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6373c076370f1965c61857bafd2f86705ec4046208e132d6a0448cbc98aa6c82
|
|
BLAKE2b-256 checksum How to use checksums |
f11852aa3655018284ec7d922e00440d5073c9508b654628705a5fc1ed50d862
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 17, 2025.
Transparency logSecurity for pytrpp 0.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pytrpp-0.4.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 17, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.