By default, Portfolio Performance (developed in Java) sends a generic User-Agent of the Java/11 type… or the identifier specific to the application. Boursorama’s servers immediately detect that it is a bot/script and block the connection (often with an HTTP 403 Forbidden error or an invisible Cloudflare challenge).
Version 0.84.2 seems not be available under flatpak.By the way gemini says Hello everyone,
Since May 29, 2026, I have been unable to update historical quotes for my financial instruments in Portfolio Performance using Boursorama.
I am using the JSON provider with the following URL structure: [https://www.boursorama.com/bourse/action/graph/ws/GetTicksEOD?symbol=1rPICAD&length=7300&period=0](https://www.boursorama.com/bourse/action/graph/ws/GetTicksEOD?symbol=1rPICAD&length=7300&period=0)
Interestingly, if I use the exact same app on my Android device with the identical URL syntax, it works perfectly and returns a valid response. However, it fails consistently on the Desktop version.
It looks like Boursorama might have tightened their security/anti-bot measures recently, and the Desktop client’s User-Agent or request headers are getting blocked, while the Android webview passes through.
Thank you for your point regarding the date.By the way i hope someone is able to fix the Http header.I had similar issue using woob to scrap bank bu written in Python and solved here by modifing the header Work items · woob / woob · GitLab