# openfeed > openfeed is a consumer data platform built in Australia, for Australia. Connect your banking and energy accounts once through the Consumer Data Right, then share that data with any app in a single tap — one dashboard for consumers, one API for developers. openfeed is a consumer data platform native to Australia's Consumer Data Right (CDR). It provides a single integration layer over the CDR — comparable in purpose to open-banking platforms overseas, but native to Australia's CDR and spanning both banking and energy. openfeed is a product of Biza Pty Ltd, which is powered by software written by the team that built 30+ data-holder implementations, Open Gateway and a full CDR test ecosystem — one of the largest contributors to the build of Australia's CDR ecosystem. ## Core concepts - Consumers connect each data holder (bank or energy retailer) once through the full CDR consent flow. - openfeed aggregates that data and normalises it to a single API. - Data is batch-refreshed (banking every 4 hours, energy every 6 hours). - Consumers then share data onward with any app in a single tap (disclosure consent), governed by the Privacy Act. - Revoking a disclosure consent never cascades to the underlying CDR arrangement. - Developers integrate once against one OAuth 2.0 + REST API covering every holder, for both banking and energy. - Apps can offer optional "Login with openfeed" single sign-on — free to any developer. ## Build an app (developers) - [Developer hub](https://openfeed.au/developers): overview, API at a glance, key endpoints. - [Quickstart](https://openfeed.au/resources/quickstart): register an app, OAuth 2.0 PKCE, request disclosure consent, fetch data, handle errors. Markdown: https://openfeed.au/resources/quickstart.md - [API Reference](https://openfeed.au/developers/api): interactive OpenAPI 3.1 docs. - [OpenAPI spec (machine-readable)](https://openfeed.au/openapi.yaml): the canonical Sharing API spec. - [Pricing](https://openfeed.au/pricing): usage-based credits; 10 free credits per new account. - [Full developer docs (concatenated)](https://openfeed.au/llms-full.txt): everything an agent needs in one file. ### API essentials (Sharing API v4.0.0) - Base URL: https://api.openfeed.au/v1 - Auth: OAuth 2.0 Authorization Code + PKCE + PAR (mandatory). All clients are confidential. Recommended profile: private_key_jwt + DPoP (RFC 9449). Legacy profile: client_secret_basic + Bearer. - Scopes: openid, openfeed-au:data:banking:read, openfeed-au:data:energy:read, openfeed-au:grant:self:query, openfeed-au:grant:self:revoke - Discovery: resolve from the OIDC issuer's {issuer}/.well-known/openid-configuration (do not hard-code the host). - Access tokens are PS256-signed JWTs (RFC 9068, typ: at+jwt); carry a grant_id claim. Read grant_id from the decoded JWT, not from authorization_details. - PAR body must include resource=https://api.openfeed.au to bind the token to the sharing-api audience. - Data endpoints require an active disclosure grant; return 403 disclosure_grant_required (absent/revoked/not approved) or 402 credit_exhausted (grant suspended). - Energy meters are nested under accounts: /v1/energy/accounts/{accountId}/meters/{meterId}[/usage|/der] - Balance endpoints fetch live (~15min cache): /v1/banking/accounts/{accountId}/balance, /v1/energy/accounts/{accountId}/balance - Response envelope: { version: "V1", data, meta?, links? } — links.next absent on last page. ## For consumers - [How it works for consumers](https://openfeed.au/consumers): connect once, share in a tap, revoke any time. - Sign in / dashboard: https://app.openfeed.au/login ## Resources - [Connect once, share in a tap: how consent works](https://openfeed.au/resources/connect-once-share-in-a-tap): Why connecting your bank is a one-time step, and why sharing with each new app only takes a single tap — in plain English. - [Handling errors from the openfeed API](https://openfeed.au/resources/error-handling): Every non-200 response you can expect from the openfeed Sharing API, what it means, and how your app should react. - [Frequently asked questions](https://openfeed.au/resources/faq): Answers to the questions consumers and developers ask most about openfeed, the Consumer Data Right, sharing, security and getting started. - [Getting started: connecting your first account](https://openfeed.au/resources/getting-started-connecting-your-first-account): How to sign up for openfeed and connect your first bank or energy account — step by step, in plain English. - [Grant management & lifecycle](https://openfeed.au/resources/grant-management-and-lifecycle): How grants work on openfeed: the durable handle for a consumer share, how to create, amend, query and revoke them, and how to handle grant state in your app. - [How onward sharing works](https://openfeed.au/resources/how-onward-sharing-works): The one-tap sharing model — what happens when you share data with an app, what the app can and can't do, and how to turn it off. - [How openfeed keeps your data safe](https://openfeed.au/resources/how-openfeed-keeps-your-data-safe): Your data, protected — in plain English. What openfeed does to keep your banking and energy data secure, and how you stay in control. - [Introducing openfeed: one consent, every app](https://openfeed.au/resources/introducing-openfeed): Why we built a consumer data platform on top of technology proven across 30+ production CDR implementations, and what it means for consumers and developers in Australia. - [Login with openfeed](https://openfeed.au/resources/login-with-openfeed): Optional single sign-on so people can sign in to your app with their openfeed identity, the starting point for a streamlined path to data sharing. - [Disclosure consent vs. CDR arrangements: what developers need to know](https://openfeed.au/resources/onward-disclosure-explained): The two-consent model that lets consumers share in one tap — and how it keeps onward sharing clean, scoped and revocable. - [Open Banking in Australia: a primer](https://openfeed.au/resources/open-banking-primer): What Open Banking is, how it grew out of the Consumer Data Right, what data is in scope, and how openfeed makes it usable for everyone. - [Path to production](https://openfeed.au/resources/path-to-production): How to take your openfeed app from first build through verification and into the public app catalogue — the gates you cross, and the guidance to follow along the way. - [Quickstart](https://openfeed.au/resources/quickstart): From zero to live data in a few simple steps: register your app, let users log in with openfeed, request consent to their banking or energy data, and fetch it through a simple REST API. - [Security & data handling at openfeed](https://openfeed.au/resources/security-and-data-handling): The security posture developers build on: openfeed as an accredited CDR recipient software product, FAPI 2.0 authentication, and data-pipeline controls. - [Sign in to apps with your openfeed account](https://openfeed.au/resources/sign-in-to-apps-with-openfeed): What "Login with openfeed" means for you, a one-tap way to sign in to apps, separate from sharing your data. - [What is the Consumer Data Right (CDR)?](https://openfeed.au/resources/what-is-cdr): A plain-English primer on Australia's Consumer Data Right and how openfeed fits in. ## News - [Introducing openfeed: one consent, every app](https://openfeed.au/resources/introducing-openfeed): Why we built a consumer data platform on top of technology proven across 30+ production CDR implementations, and what it means for consumers and developers in Australia. ## Optional - [About / company](https://openfeed.au/about) - [Pricing](https://openfeed.au/pricing) - [Privacy](https://openfeed.au/privacy) - [Terms of Service](https://openfeed.au/terms) - [RSS feed](https://openfeed.au/rss.xml)