# 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.

## Core concepts

- Two consent layers: CDR arrangement (per holder, established once through the full CDR flow) + disclosure grant (per app, granted in a single tap via the openfeed consent screen).
- A disclosure grant is required before any data endpoint call — a token without a grant_id returns 403. Establishing the grant is a distinct step after login.
- Disclosure revocation is isolated — revoking a grant does NOT cascade to the CDR arrangement.
- One OAuth 2.0 + REST API covering every holder: banking and energy.
- All third-party clients use private_key_jwt + DPoP (Recommended profile). PAR is mandatory.

## Build an app (developers)

> **Start here for integration:** [Full developer docs](https://openfeed.au/llms-full.txt) — complete zero-question bootstrap, end-to-end worked example (new app and existing app paths), full auth flow, grant model, all endpoints, error handling. One file, no clarifying questions needed. **Primary integration surface for AI agents.**

- [Quickstart](https://openfeed.au/resources/quickstart): step-by-step guide — register an app, implement OAuth 2.0 PKCE + PAR, establish the disclosure grant (the two-phase flow that gates all data access), fetch banking and energy accounts, handle errors. Markdown: https://openfeed.au/resources/quickstart.md
- [Developer hub](https://openfeed.au/developers): overview, API at a glance, key endpoints.
- [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 — authoritative source for all field names, types, and shapes.

## 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

- [The Consumer Data Right just got bigger. Your build shouldn't have to.](https://openfeed.au/resources/cdr-just-got-bigger): At least 35 non-bank lenders entered the Consumer Data Right in July 2026. What the expansion means for product roadmaps, and the three ways teams get access.
- [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.
- [Live before lunch: what the first hour with openfeed actually looks like](https://openfeed.au/resources/live-before-lunch): This is a build log, not a brochure. If you want the pitch, it's one line: consented Australian banking and energy data through one API, no accreditation project. Here's what happens after you decide to try it.
- [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

- [Live before lunch: what the first hour with openfeed actually looks like](https://openfeed.au/resources/live-before-lunch): This is a build log, not a brochure. If you want the pitch, it's one line: consented Australian banking and energy data through one API, no accreditation project. Here's what happens after you decide to try it.
- [The Consumer Data Right just got bigger. Your build shouldn't have to.](https://openfeed.au/resources/cdr-just-got-bigger): At least 35 non-bank lenders entered the Consumer Data Right in July 2026. What the expansion means for product roadmaps, and the three ways teams get access.
- [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)