Current Status: Trade Republic Connections Unstable
More Information
- Account types affected: CTO, PEA, current account
- What you may notice in Finary: missing investment details, accounts in error, only overall balance visible
- Current progress or blockers: most connections are syncing well. Some users remain stuck at authentication, either because Trade Republic doesn’t send the notification, or because it blocks Powens’ attempts (rate-limiting, a voluntary limitation on the number of requests imposed on TR’s side). For others, the blockage occurs later, during CTO data extraction: Powens deployed a fix on September 30 that unblocked some accounts, with no guarantee for all: some CTOs remain in error after this deployment and have been escalated to Powens. Unlinking the authenticator associated with the Trade Republic account unblocks validation for some affected users; the procedure is described in our help article. The API opened at the end of July is still not usable: transaction labels come back without information and Trade Republic has not communicated any correction date despite repeated follow-ups from Powens, whose legal department has reported the situation to ACPR and the German regulator. Continuously monitored with the partner. Details of the API’s expected functionality in this message.
Changelog
-
2025-06-09: Issue identified and escalated by Finary
-
2025-12-23: Fix deployed for new connections (partial)
-
2025-12-24: Analysis of remaining anomalies on certain accounts
-
2026-01-06: Developer assigned on partner side, fix in preparation
-
2026-01-14: Ongoing monitoring with the bank and partner
-
2026-02-11: Major fix in preparation on Powens’ side (optimization of flow management via WebSockets)
-
2026-02-17: Major fix deployed to production by Powens (systematic unsubscription of WebSockets after data retrieval) and start of monitoring phase
-
2026-02-18: New wave of improvements under review at Powens, with a new production deployment targeted for next week
-
2026-02-21: New fixes deployed
-
2026-02-23: Emergence of an OTP code generation issue by Trade Republic, impacting Powens and FinaryConnect integrations
-
2026-02-27: Fix completed on FinaryConnect
-
2026-03-11: Fix in testing phase at Powens
-
2026-03-13: Fix deployed, but persistent issues
-
2026-03-17: New fix in testing phase
-
2026-03-18: New fix deployed but inconclusive
-
2026-03-24: Trade Republic has again modified a security parameter on its site. New fix in testing phase.
-
2026-03-27: New symptoms observed (rate-limiting despite OTP receipt), analysis restarted and developer audit underway at the partner
-
2026-04-02: Trade Republic / Powens meeting
-
2026-04-20: Fix for rate-limiting deployed by Powens. Emergence of a new bug for some users previously blocked by this rate-limiting. Situation unblocked for others.
-
2026-04-21: Fix for error 405 deployed to production by Powens. Tests on Finary’s side partially conclusive.
-
2026-04-24: Identification of a new Trade Republic authentication flow (in-app validation via push + code). Workaround communicated. Request for improved handling of this step escalated to the partner.
-
2026-05-18: After new fix attempts, Powens will finally change approach this week. We hope the situation will be stabilized soon.
-
2026-06-25: Major fix deployed to production by Powens on rate-limiting. Emergence of a synchronization issue on certain CTOs or PEAs.
-
2026-06-30: Powens testing a fix for resolution.
-
2026-07-02: Regression: Trade Republic has redesigned its webapp and modified its authentication method, breaking part of the connections again.
-
2026-07-15: Powens has deployed several improvements to adapt to the new authentication method; tests conducted in parallel on Finary’s side with our own accounts to accelerate resolution.
-
2026-07-20: Authentication largely restored (residual timeouts and rate-limiting on Powens’ side). A data extraction issue for accounts persists and affects approximately 20% of users.
-
2026-07-23: Clarification on rate-limiting: this is a voluntary limitation on the number of requests imposed by Trade Republic (blocking on TR’s side), which Powens is actively working to bypass (priority project). The data extraction issue still affects approximately 20% of users.
-
2026-07-27: Trade Republic has opened access to its API, following repeated follow-ups from Powens. Tests are underway, in which Finary participated on July 24. Authentication will go through webauth (QR code displayed in the Powens webview, direct validation in the Trade Republic application) opening access valid for 180 days, with automatic synchronization of the cash account and its transactions (Budget). CTO and PEA positions will not be transmitted by the API and will remain in manual synchronization. Point of caution: transaction labels come back missing or incomplete, feedback must be provided to Trade Republic.
-
2026-08-28: Status update. Most connections are syncing well. Remaining blockages are split between authentication (notification not sent by Trade Republic, or Powens’ attempts blocked by rate-limiting) and CTO data extraction. Trade Republic’s API is still not usable, Powens continues to provide feedback on it.
-
2026-09-02: Powens is looking for workarounds with users blocked at authentication. Several users report in this thread that unlinking the authenticator in Trade Republic security settings unblocks their synchronization (#924).
-
2026-09-08: Unlinking the Trade Republic authenticator (Settings > Security > Authenticator > Unlink) is now documented in our help article. It only unblocks authentication: retrieval of CTO positions is still being corrected at Powens.
-
2026-09-15: The API opened at the end of July remains unusable, the blockage is on Trade Republic’s side (transaction labels returned without information). No correction date communicated despite follow-ups from Powens, whose legal department has reported the situation to ACPR and the German regulator.
-
2026-09-30: Fix deployed by Powens on CTO position extraction, effective for some accounts. Others remain in error after deployment, escalated to Powens the same day.
Practical Tips
- Avoid deleting then recreating the connection or making multiple reconnection attempts
Follow this thread to stay informed of updates
