v1.6.0

What's New

Raiffeisenbank outages are now recognised as outages. When the RB Premium API gateway is down for everyone, it answers every request with HTTP 500 and an outage: yes header. The library now detects this and throws a dedicated OutageException, so your application can show a clear "the bank's API is currently down" message and skip pointless retries instead of treating it as a problem with your own request or account. OutageException extends ApiException, so existing error handling keeps working unchanged.

Fixed

• Downloading statements no longer crashes when the bank rejects the client certificate (for example "Certificate is terminated" or a blocked certificate). You now get a readable ApiException that contains the bank's own error text, and the same text appears in logs.
• Error responses from the bank (400, 401, 403, 404, 429) are now consistently converted into readable exceptions instead of being returned as if they were normal data.

Other Changes

• The API specification now documents the terminated/blocked certificate responses.
• The code-generator templates were updated, so the outage and authorisation handling stays in place when the client is regenerated from the OpenAPI spec.