openfeed status
Known issues affecting the openfeed platform, along with those originating upstream in the CDR ecosystem, and workarounds where they are available. Select an issue to view the full details.
openfeed platform
Confirmed defects and known-broken behaviour in the openfeed platform. Issues we own and are working to fix.
Banking account detail is missing fields
Banking account responses leave out accountType, and for loan, credit card and term deposit accounts, the product-specific fields the bank provides.
Banking transactions are missing transaction and value dates
transactionDate and valueDate are empty on every banking transaction.
Energy usage is missing interval detail after first connection
When a new energy account is first connected, most of the usage history is returned without interval readings.
An invalid billing amount can stop energy billing updates
If an energy retailer returns an invalid billing or invoice amount, billing and invoice updates for the whole connection can stall.
Connecting a Revolut account fails
After approving access at Revolut, the connection to openfeed can't be completed.
Some energy data is not available through openfeed yet
openfeed's energy responses leave out some detail that the Consumer Data Standards allow, including per-fuel plan detail for dual-fuel accounts and some billing and invoice fields.
Grant revocation via the grant management API fails
Revoking a grant through the grant management API currently fails because the required scope isn't applied at registration. In the meantime, users can still revoke grants from the openfeed dashboard.
Holder Sh*t List
Problems that originate upstream at a bank or energy retailer's CDR implementation, or the CDR register, not in openfeed. We detect, verify and document them, and work around them where we can, but the fix sits with the data holder.
Missing token_type field breaks consent finalisation
Suncorp and ING return token responses without the token_type field, causing consent finalisation to fail with a parse exception.
First identified: 23 July 2026
ANZ credit card transactions returned with a null transactionId
ANZ returns some credit card transactions with a null transactionId, which is permitted where the field is conditional under CDR rules. openfeed generates a synthetic transaction ID so these transactions can still be ingested and served.
First identified: 20 July 2026

Report it in our developer community and we'll triage it — confirmed issues land on this page. It's also where we share workarounds and hear what you're building.
Join the openfeed Discord →
See also Error handling and theAPI reference.