API Reference
Postman Collection

Getting Started

About the API

The NEM Retail B2M APIs allow Registered Market Participants to undertake Retail Business-to-Market communications to submit, acknowledge and manage B2M message exchange with AEMO.

Participants use this API to exchange B2M messages with AEMO using the Push-Push message pattern for the following transaction groups:

  1. CATS: Consumer Administration and Transfer Solution (CATS) to create, withdraw, edit, object to change requests and request CATS reports as per the CATS and WIGS Procedures and to request CATS reports.

  2. NMID: NMI Standing Data Management (NMID) to Discover the End User’s NMI and NMI Checksum or sufficient standing data about the NMI.

  3. MDMT: Meter Data Management Transaction Group (MDMT) to submit meter data notifications to support B2M Market Settlements and to request RM reports as per the Meteorology Procedures.

The Push-Push message pattern requires API implementation at:

  1. The e-Hub (API Gateway and API Portal).

  2. The Participant API Gateway. B2M messages intended for delivery to the Participant are delivered to the Participant’s API Gateway as soon as it is available.

To assist with the management of NEM B2M Retail APIs, AEMO recommends Participants utilise the HubMessageManagementv2 API to retrieve the current list of stop files or invalid message acknowledgments (badack) using the alerts resource.

Getting Access

To use NEM B2M Retail APIs Participants must:

  1. Be a Registered Participant with a Participant ID.

  2. Have an MSATS user ID with the required Participant User Rights Management (URM) entities granted to it

  3. Register with AEMO to use APIs.

  4. Set up your Participant API Gateway to receive AEMO Pushed response messages.

  5. Build the APIs needing implementation at the Participant API Gateway according to the specifications in the Guide to NEM Retail B2M APIs.

During formal onboarding, you will first be given access to Pre-Production and must complete your development/testing there prior to getting access to Production.

External Docs

Below are a list of external links for additional context to the API or Program:

API Details

Authentication Methods

This API is using the following Security Policies:

Note: The TLS certificates used to access Pre-Production are different from those used to access Production.


Below are the base URLs used for this API:


Base URL

Data Type

Pre-Production Internet Entry


Test Data

Pre-Production MarketNet Entry


Test Data

Production Internet Entry


Live Data

Production MarketNet Entry


Live Data


Paths, Headers, Request Body and Responses can be found in the API Reference (OpenAPI Spec).