AEMO

AEMO Hub Message Management V2 API

Introduction

Documentation GitHub OpenAPI

Operations 1

GET /getAlerts Get Alerts #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/aemo-hubmessagemanagementv2-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Hub Message Management V2 API
  description: '## Introduction

    The HubMessageManagement push API retrieves the current list of B2B and B2M stop files.'
  version: '3.0'
  x-origin:
  - format: openapi
    source: AEMO API Management developer portal
    url: https://dev.aemo.com.au/developer/apis/hubmsgmgt-v2/operations?api-version=2022-04-01-preview
servers:
- url: https://api-prd.aemo.local/HubMessageManagement
security:
- {}
- apiKeyHeader: []
- apiKeyQuery: []
tags:
- name: HubMessageManagementV2
  description: Introduction
paths:
  /getAlerts:
    get:
      operationId: getAlerts
      summary: Get Alerts
      tags:
      - HubMessageManagementV2
      description: Receive B2B and B2M stop file alerts
      parameters:
      - name: alertType
        in: query
        required: false
        schema:
          type: string
          default: B2BStopFile
        description: '''B2BStopFile'' or ''B2MStopFile''. If not provided, default to ''B2BStopFile'''
      - name: queryParticipantID
        in: query
        required: false
        schema:
          type: string
        description: Used for B2B alerts only. If provided, the alerts for that particular participant is returned. This value is ignored for B2M alerts.
      - name: X-initiatingParticipantID
        in: header
        required: true
        schema:
          type: string
        description: The ID of the Initiating Participant
      - name: X-transactionID
        in: header
        required: false
        schema:
          type: string
        description: unique ID for the transaction
      - name: Authorization
        in: header
        required: true
        schema:
          type: string
        description: The API requires the usage of HTTP Basic authentication header to allow access. This is your URM username and password.
      responses:
        '200':
          description: Success response with aseXml response payload
          content:
            application/xml:
              example: <_x0032_00APIResponseResponse-xml></_x0032_00APIResponseResponse-xml>
        '400':
          description: This response is provided when Mandatory HTTP header {missing Header Name} is missing. No response paylaod.
        '401':
          description: This response is provided when Authorisation is missing from the header OR user/password is incorrect OR user account is locked out. No response paylaod.
        '404':
          description: This response is provided when the requested resource for the endpoint URI is not found. No response paylaod.
        '405':
          description: This response is provided when the requested method/verb on a resource is invalid. No response paylaod.
        '429':
          description: This response is provided when number of inbound requests exceeded the throttling limits. No response paylaod.
        '500':
          description: This response is provided when any unforeseen error is encountered,such as; Certificate/key do not match or incorrect or downstream service is not available.
components:
  securitySchemes:
    apiKeyHeader:
      type: apiKey
      name: x-apikey
      in: header
    apiKeyQuery:
      type: apiKey
      name: subscription-key
      in: query