Red Energy Pty Ltd (ABN 60 107 479 372) is an Australian electricity and gas retailer, wholly owned by Snowy Hydro Ltd, that supplies more than a million residential and business customers across New South Wales, Victoria, Queensland, South Australia and the ACT from a Richmond, Victoria base. It sits on the retail end of the National Electricity Market value chain: Snowy Hydro generates, the distribution network businesses own the poles and wires, AEMO operates the market and holds metering data, and Red Energy owns the customer, the tariff and the bill. Its API posture is entirely a product of statute rather than product strategy. Red Energy publishes no developer portal, no self-serve API programme and no proprietary specification - developer., api., docs. and data. subdomains do not resolve, and redenergy.com.au itself sits behind a Cloudflare bot challenge that returns HTTP 403 to any non-browser client. What it does have is a real, verified Consumer Data Right implementation: it is a designated CDR energy data holder listed on the CDR Register with the public base URI https://public.cdr.redenergy.com.au, which serves the Consumer Data Standards discovery endpoints live with correct x-v version negotiation, while 1,705 Red Energy branded plans are published anonymously through the Australian Energy Regulator's Energy Made Easy CDR host. The split is the story - open, standardised, anonymous product reference data on one side, and consumer usage, billing and account data available only to accredited CDR data recipients with the customer's consent on the other, with nothing at all in between.
Red Energy publishes 3 APIs on the APIs.io network: CDR Energy Product Reference Data API, CDR Discovery API, and CDR Energy Consumer Data API. Tagged areas include Energy, Australia, Utilities, Electricity, and Gas.
Red Energy’s developer surface includes authentication, changelog, code examples, status page, documentation, API reference, support, and 29 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Energy & Utilities regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
The unauthenticated Consumer Data Right Product Reference Data surface for the Red Energy brand - Get Generic Plans and Get Generic Plan Detail from the Consumer Data Standards ...
Red Energy's own registered Consumer Data Right public base URI, serving the two unauthenticated Data Holder Operations endpoints of the Consumer Data Standards CDR Common API -...
The consumer-authorised half of the Consumer Data Right energy obligation that Red Energy is designated to meet as a data holder - electricity service points, usage, distributed...
Check that Red Energy's CDR implementation is available, then list its published electricity plans and pull the full tariff detail for one of them. Every step is unauthenticated...
aid: red-energy
url: https://raw.githubusercontent.com/api-evangelist/red-energy/refs/heads/main/apis.yml
name: Red Energy
kind: company
description: 'Red Energy Pty Ltd (ABN 60 107 479 372) is an Australian electricity and gas retailer, wholly owned by Snowy
Hydro Ltd, that supplies more than a million residential and business customers across New South Wales, Victoria, Queensland,
South Australia and the ACT from a Richmond, Victoria base. It sits on the retail end of the National Electricity Market
value chain: Snowy Hydro generates, the distribution network businesses own the poles and wires, AEMO operates the market
and holds metering data, and Red Energy owns the customer, the tariff and the bill. Its API posture is entirely a product
of statute rather than product strategy. Red Energy publishes no developer portal, no self-serve API programme and no proprietary
specification - developer., api., docs. and data. subdomains do not resolve, and redenergy.com.au itself sits behind a Cloudflare
bot challenge that returns HTTP 403 to any non-browser client. What it does have is a real, verified Consumer Data Right
implementation: it is a designated CDR energy data holder listed on the CDR Register with the public base URI https://public.cdr.redenergy.com.au,
which serves the Consumer Data Standards discovery endpoints live with correct x-v version negotiation, while 1,705 Red
Energy branded plans are published anonymously through the Australian Energy Regulator''s Energy Made Easy CDR host. The
split is the story - open, standardised, anonymous product reference data on one side, and consumer usage, billing and account
data available only to accredited CDR data recipients with the customer''s consent on the other, with nothing at all in
between.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/red-energy.png
tags:
- Energy
- Australia
- Utilities
- Electricity
- Gas
- Energy Retail
- Consumer Data Right
- CDR
- Product Reference Data
- Smart Metering
- Open Data
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.19'
apis:
- aid: red-energy:red-energy-cdr-energy-product-reference-data-api
name: Red Energy CDR Energy Product Reference Data API
description: 'The unauthenticated Consumer Data Right Product Reference Data surface for the Red Energy brand - Get Generic
Plans and Get Generic Plan Detail from the Consumer Data Standards CDR Energy API. Unlike CDR banking, where each authorised
deposit-taking institution serves its own product endpoint, energy plan data is served centrally by the Australian Energy
Regulator''s Energy Made Easy CDR host under a per-brand path. Confirmed live on 2026-07-27: GET /cds-au/v1/energy/plans
with header x-v 1 returned HTTP 200 with response header x-v 1 and meta.totalRecords 1705 Red Energy plans across electricity
and gas; the same call with no x-v header returned HTTP 400 and with x-v 9 returned HTTP 406, exactly the version-negotiation
behaviour the Consumer Data Standards prescribe. Plan detail requires x-v 3 or higher - x-v 1 returns a urn:au-cds:error:cds-all:Header/UnsupportedVersion
error. No API key, no signup and no accreditation is needed to call it.'
humanURL: https://consumerdatastandardsaustralia.github.io/standards/#energy-apis
baseURL: https://cdr.energymadeeasy.gov.au/red-energy/cds-au/v1
tags:
- Energy Plans
- Product Reference Data
- Consumer Data Right
- Tariffs
- Australia
properties:
- type: OpenAPI
url: openapi/red-energy-cds-energy-openapi.yml
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#energy-apis
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#get-generic-plans
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#get-generic-plan-detail
- type: Documentation
url: https://consumerdatastandardsaustralia.github.io/standards/
- type: Registry
url: https://api.cdr.gov.au/cdr-register/v1/energy/data-holders/brands/summary
- type: Overlay
name: API Evangelist enhancements for the CDR Energy API
url: overlays/red-energy-cds-energy-overlay.yaml
- type: Examples
name: Live list-plans capture, 2026-07-27
url: examples/red-energy-list-energy-plans-example.json
- type: Examples
name: Live plan-detail capture, 2026-07-27
url: examples/red-energy-get-energy-plan-detail-example.json
- type: Arazzo
name: Compare Red Energy tariff plans
url: arazzo/red-energy-compare-plans-workflow.yml
- type: AgentSkill
name: Compare Red Energy tariff plans
url: skills/red-energy-compare-energy-plans.md
- aid: red-energy:red-energy-cdr-discovery-api
name: Red Energy CDR Discovery API
description: 'Red Energy''s own registered Consumer Data Right public base URI, serving the two unauthenticated Data Holder
Operations endpoints of the Consumer Data Standards CDR Common API - Get Status and Get Outages. This is the only API
surface hosted on a Red Energy controlled domain. Confirmed live on 2026-07-27: GET /cds-au/v1/discovery/status with header
x-v 1 returned HTTP 200 and a CDS-shaped envelope reporting status OK and "All services operational", GET /cds-au/v1/discovery/outages
returned HTTP 200 with an empty outages array, the same calls without an x-v header returned HTTP 400, and x-v 3 returned
HTTP 406. The base URI serves nothing else anonymously - /cds-au/v1/energy/plans, the site root and /.well-known/openid-configuration
all return an nginx HTTP 404.'
humanURL: https://consumerdatastandardsaustralia.github.io/standards/#common-apis
baseURL: https://public.cdr.redenergy.com.au/cds-au/v1
tags:
- Discovery
- Status
- Outages
- Consumer Data Right
- Australia
properties:
- type: OpenAPI
url: openapi/red-energy-cds-common-openapi.yml
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#get-status
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#get-outages
- type: Status
url: https://public.cdr.redenergy.com.au/cds-au/v1/discovery/status
- type: StatusPage
url: https://public.cdr.redenergy.com.au/cds-au/v1/discovery/status
- type: Documentation
url: https://consumerdatastandardsaustralia.github.io/standards/
- type: Overlay
name: API Evangelist enhancements for the CDR Common API
url: overlays/red-energy-cds-common-overlay.yaml
- type: Examples
name: Live get-status capture, 2026-07-27
url: examples/red-energy-get-status-example.json
- type: Examples
name: Live get-outages capture, 2026-07-27
url: examples/red-energy-get-outages-example.json
- type: AgentSkill
name: Check Red Energy CDR availability before calling
url: skills/red-energy-check-cdr-availability.md
- aid: red-energy:red-energy-cdr-energy-consumer-data-api
name: Red Energy CDR Energy Consumer Data API
description: 'The consumer-authorised half of the Consumer Data Right energy obligation that Red Energy is designated to
meet as a data holder - electricity service points, usage, distributed energy resources, energy accounts, balances, invoices,
billing, concessions and payment schedules, sixteen paths in all from the Consumer Data Standards CDR Energy API. This
surface is real and mandated, but it is not open: it is reachable only by an accredited CDR data recipient, over mutual
TLS with FAPI-profile OAuth2 and OpenID Connect, after the individual customer grants consent, and the infosec base URI
is published only through the authenticated portion of the CDR Register. No baseURL is recorded here because none is publicly
discoverable, and no endpoint on this surface was called - it cannot be reached anonymously. The mandate is verified;
the endpoints are, by design, unverifiable from outside the accreditation regime.'
humanURL: https://consumerdatastandardsaustralia.github.io/standards/#energy-apis
tags:
- Energy Accounts
- Electricity Usage
- Billing
- Distributed Energy Resources
- Consumer Data Right
- Australia
properties:
- type: OpenAPI
url: openapi/red-energy-cds-energy-openapi.yml
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#energy-apis
- type: Authentication
url: https://consumerdatastandardsaustralia.github.io/standards/#security-profile
- type: Authentication
name: Red Energy CDR authentication profile
url: authentication/red-energy-authentication.yml
- type: OAuthScopes
name: CDR energy authorisation scopes
url: scopes/red-energy-scopes.yml
- type: Documentation
url: https://consumerdatastandardsaustralia.github.io/standards/
- type: Overlay
name: API Evangelist enhancements for the CDR Energy API
url: overlays/red-energy-cds-energy-overlay.yaml
- type: AgentSkill
name: Retrieve a consenting customer's energy data as an accredited data recipient
url: skills/red-energy-share-consumer-energy-data.md
common:
- type: AgenticAccess
url: agentic-access/red-energy-agentic-access.yml
- type: DomainSecurity
url: security/red-energy-domain-security.yml
- type: Authentication
name: Red Energy CDR authentication profile
url: authentication/red-energy-authentication.yml
- type: OAuthScopes
name: CDR energy authorisation scopes
url: scopes/red-energy-scopes.yml
- type: Conventions
name: Red Energy CDR API conventions
url: conventions/red-energy-conventions.yml
- type: ErrorCatalog
name: CDS error code catalogue
url: errors/red-energy-problem-types.yml
- type: Lifecycle
name: Red Energy CDR lifecycle, versioning and service levels
url: lifecycle/red-energy-lifecycle.yml
- type: StatusPage
name: CDR Get Status endpoint (machine-readable status surface)
url: https://public.cdr.redenergy.com.au/cds-au/v1/discovery/status
- type: Deprecation
name: CDS Endpoint Version Schedule (deprecation and retirement policy)
url: https://consumerdatastandardsaustralia.github.io/standards/#endpoint-version-schedule
- type: Roadmap
name: CDS Future Dated Obligations
url: https://consumerdatastandardsaustralia.github.io/standards/#future-dated-obligations
- type: ChangeLog
name: Consumer Data Standards changelog
url: changelog/red-energy-changelog.yml
- type: RateLimits
name: CDS traffic thresholds and velocity limits
url: rate-limits/red-energy-rate-limits.yml
- type: Conformance
name: Standards conformance, verified and asserted
url: conformance/red-energy-conformance.yml
- type: Compliance
name: Red Energy Consumer Data Right Policy
url: https://www.redenergy.com.au/docs/Red-Energy-Consumer-Data-Right-Policy.pdf
- type: DataModel
name: CDR energy entity graph
url: data-model/red-energy-data-model.yml
- type: Packages
name: Package registry search results and CDR ecosystem tooling
url: packages/red-energy-packages.yml
- type: MCPServer
name: Candidate MCP tool set derived from the CDR specs
url: mcp/red-energy-mcp.yml
- type: ToolCrosswalk
name: MCP tool to OpenAPI operation crosswalk
url: mcp/red-energy-tool-crosswalk.yml
- type: AgentSkill
name: Packaged agent skills for the Red Energy CDR surface
url: skills/_index.yml
- type: Examples
name: Live request/response captures, 2026-07-27
url: examples/
- type: LLMsTxt
name: Generated llms.txt
url: llms/red-energy-llms.txt
- type: Arazzo
name: Compare Red Energy tariff plans
url: arazzo/red-energy-compare-plans-workflow.yml
- type: Website
url: https://www.redenergy.com.au/
- type: LinkedIn
url: https://www.linkedin.com/company/red-energy
- type: Status
url: https://public.cdr.redenergy.com.au/cds-au/v1/discovery/status
- type: Registry
url: https://api.cdr.gov.au/cdr-register/v1/energy/data-holders/brands/summary
- type: Documentation
url: https://consumerdatastandardsaustralia.github.io/standards/
- type: APIReference
url: https://consumerdatastandardsaustralia.github.io/standards/#energy-apis
- type: Support
name: Red Energy Contact Us
url: https://www.redenergy.com.au/contactus/
- type: HelpCenter
name: Red Energy Help Centre
url: https://www.redenergy.com.au/help-centre/
- type: Pricing
name: Red Energy energy plans
url: https://www.redenergy.com.au/products/
- type: SignUp
name: Red Energy MyAccount registration
url: https://myaccount.redenergy.com.au/registration
- type: Login
name: Red Energy MyAccount
url: https://myaccount.redenergy.com.au/
- type: TermsOfService
name: Red Energy Terms and Conditions
url: https://www.redenergy.com.au/terms-and-conditions/
- type: PrivacyPolicy
name: Red Energy Privacy Policy
url: https://www.redenergy.com.au/privacy-policy/index.html
- type: Owner
name: Snowy Hydro Ltd
url: https://www.snowyhydro.com.au/retail/
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Kin Score
How this is scored →