Getting started

About Reserve Capacity Mechanism (RCM) API

The Reserve Capacity Mechanism (RCM) ensures the SWIS has sufficient available capacity to meet periods of peak demand. AEMO is responsible for assessing the capability of new or existing Facilities to provide capacity.

The RCM Operations application provides functionality related to the RCM, including Certified Reserve Capacity applications, Capacity Credit Assignments, Reserve Capacity Testing, Consumption Deviation applications, Non-Temperature Dependent Load applications, Individual Reserve Capacity Requirements, and Capacity Credit Allocations. 

Market Participants can interact with the RCM Operations application through the RCM Operations API and use features that include importing/creating, updating and publishing RCM Limit Advice and Constraint Equations in bulk. 

Contact AEMO RCM Team - Email: wa.capacity@aemo.com.au - for support for the following functionalities:

• Certified Reserve Capacity applications

• Capacity Credit Assignments

• Reserve Capacity Testing

• Consumption Deviation applications

Contact AEMO WA P&S team - Email: wa.settlements@aemo.com.au - for support for the following functionalities:

• Non-Temperature Dependent Load applications

• Individual Reserve Capacity Requirements

• Capacity Credit Allocations

Navigating this reference 

This page provides an overview of the API as well as information on how to use it. 

The icons at the top of the page link to the following, more detailed information sources:  

• The API Reference describes the paths, headers, request body and responses for each of the endpoints in the API. 

• The Swagger File links to the latest version of the swagger file for the API. 

Prerequisites for API access

Before using this API, you need the following:

• An enabled user account (created by your Market Participant Administrator) attached to a Registered Market Participant (see WEMS MPI User Management User Guide).

• A DigiCert Certificate created and installed for the user account.

For more information, see The Reformer: Accessing our test environments. 

External documents

• None.

Non-functional requirements 

The following provisional non-functional requirements (NFR) are relevant to this API. These may be revised in subsequent versions following consultation with Market Participants. 

Request/response payload required limits:

• For all APIs, there is an enforced 10 MB max limit

Rate Limits (Throttling) applied per user:  

• An individual user is restricted to accessing 50 calls to this API every minute, with a total of 250 calls in five minutes.

API details

Authentication method

This API uses the DigiCert TLS certificate authentication method. 

Base URLs

The base URLs used for this API are included below: