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

AEMO B2BMessagingPull

AEMO B2BMessagingPull from AEMO — 3 path(s) described in OpenAPI.

AEMO B2BMessagingPull is one of 77 APIs that AEMO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths. It is described by OpenAPI 3.0.1, at version 3.0.

Requests are made against a single base URL, https://api-prd.aemo.local/ws/B2BMessagingPull.

4 operations 3 paths 0 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.0
Base URL
https://visualisations.aemo.com.au/aemo/apps/api/report
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

AEMO B2BMessagingPull declares 2 security schemes for authenticating requests. An API key is passed in the header as x-eHub-APIKey (apiKeyHeader). An API key is passed in the query as subscription-key (apiKeyQuery). By default, every request must be authenticated, though some operations may also be called without credentials.

Paths & Operations 4

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

B2BMessagingPull 4

The B2BMessagingPull API is a B2B SMP API used to send and receive B2B messages between the participants in a Pull messaging pattern. The messages will be queued in the e-Hub and…

DELETE
/messageAcknowledgements
Delete Message Acknowledgement
deleteMessageAcknowledgement 2 params → 200400404405429500
POST
/messageAcknowledgements
Submit Message Acknowledgement
submitMessageAcknowledgement 1 param body → 200400404405429500
GET
/queues
Returns the meta-data of messages in the e-Hub queue (or) the aseXML messages queued awaiting delivery to the Recipient (initiator of this API).
returnsTheMetaDataOfMessagesInTheEHubQueueOrTheAseXMLMessagesQueuedAwaitingDeliveryToTheRecipientInitiatorOfThisAPI 5 params → 200400404405429500
POST
/messages
Submit a B2B message
submitAB2BMessage 1 param body → 200400404405429500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aemo-b2bmessaging-pull-v1-openapi.yml Raw ↑

Other APIs AEMO publishes across the network.

AEMO NEM Data Dashboard API
AEMO NEMWeb Public Data Feed
AEMO WA Market Data Public Feed
AEMO CDR
AEMO CDR Common
AEMO WEM Attributes Report
AEMO B2BMessagingAsync
AEMO B2BMessagingSync
AEMO B2MMessagingAsync
AEMO B2MMessagingPull
AEMO B2MMessagingSync
AEMO Balancing Reports v2.1
Where this information came from

This is an independent, third-party profile of AEMO B2BMessagingPull, 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.