How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Red Energy Energy Account Billing API

Energy Account Billing endpoints

Red Energy Energy Account Billing API is one of 9 APIs that Red Energy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Energy Account Billing. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a status page, and authentication docs.

This API exposes 6 operations across 4 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.36.0.

Requests are made against a single base URL, https://mtls.dh.example.com/cds-au/v1.

6 operations 4 paths 30 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.36.0
Base URL
https://cdr.energymadeeasy.gov.au/red-energy/cds-au/v1
Resource Areas
1

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Energy Account Billing 6

Energy Account Billing endpoints

GET
/energy/accounts/billing
Get Bulk Billing
listEnergyAccountBillingBulk 10 params → 200400406422
POST
/energy/accounts/billing
Get Billing For Specific Accounts
listEnergyAccountBillingForSpecificAccounts 10 params body → 200400406422
GET
/energy/accounts/invoices
Get Bulk Invoices
listEnergyAccountInvoicesBulk 10 params → 200400406422
POST
/energy/accounts/invoices
Get Invoices For Specific Accounts
listEnergyInvoicesForSpecificAccounts 10 params body → 200400406422
GET
/energy/accounts/{accountId}/billing
Get Billing For Account
getBillingForEnergyAccount 11 params → 200400404406422
GET
/energy/accounts/{accountId}/invoices
Get Invoices For Account
getEnergyAccountInvoices 11 params → 200400404406422

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are EnergyInvoice (14 properties), EnergyBillingDemandTransactionV3 (12 properties), EnergyBillingUsageTransactionV2 (12 properties), EnergyBillingTransactionV3 (9 properties). Each schema is shown below with its type and property counts.

EnergyInvoiceGasUsageCharges
object
6 properties 4 required
EnergyBillingOnceOffTransaction
object
4 properties 2 required
EnergyInvoiceListResponse
object
3 properties 3 required
EnergyBillingListResponseV3_data
object
1 property 1 required
LinksPaginated
object
5 properties 1 required
EnergyBillingPaymentTransaction
object
2 properties 2 required
EnergyInvoiceElectricityUsageCharges
object
6 properties 4 required
ErrorV2_meta
object
Additional data for customised error codes.
1 property
RequestAccountIdListV1
object
2 properties 1 required
EnergyInvoice
object
14 properties 6 required
EnergyBillingUsageTransactionV2
object
12 properties 5 required
MeasureUnitEnum
string
Meta
object
EnergyInvoiceAccountCharges
object
Object contains account level charges and credits related to electricity usage.
3 properties 2 required
EnergyBillingTransactionV3
object
9 properties 3 required
ErrorV2
object
4 properties 3 required
EnergyAccountId
string
A unique identifier for an Energy account, generated according to [CDR ID Permanence](id-permanence) requirements.
EnergyBillingUsageTransactionV2_calculationFactors
object
2 properties 2 required
EnergyBillingDemandTransactionV3
object
12 properties 5 required
EnergyInvoice_period
object
Object containing the start and end date for the period covered by the invoice. Mandatory if any usage or demand based charges are included in the invoice.
2 properties 2 required
EnergyBillingUsageTransactionV2_adjustments
object
2 properties 2 required
EnergyInvoice_payOnTimeDiscount
object
A discount for on time payment.
3 properties 2 required
EnergyBillingOtherTransaction
object
9 properties 2 required
MetaPaginated
object
2 properties 2 required
EnergyServicePointId
string
A unique identifier for an Energy service point, generated according to [CDR ID Permanence](id-permanence) requirements.
ResponseErrorListV2
object
1 property 1 required
EnergyBillingListResponseV3
object
3 properties 3 required
EnergyInvoiceGasUsageCharges_otherCharges
object
3 properties 2 required
RequestAccountIdListV1_data
object
1 property 1 required
EnergyInvoiceListResponse_data
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-energy-energy-account-billing-api-openapi.yml Raw ↑

Other APIs Red Energy publishes across the network.

Red Energy Data Holder Customers API
Red Energy Data Holder Operations API
Red Energy Distributed Energy Resources API
Red Energy Electricity Service Points API
Red Energy Electricity Usage API
Red Energy Energy Account Balances API
Red Energy Energy Accounts API
Red Energy Energy Plans API
Where this information came from

This is an independent, third-party profile of Red Energy Energy Account Billing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.