
BlindUpdateTool
The Blind Update Tool API is used by participants to submit Blind Update Tool (BUT) csv files, enabling blind updates to CATS Standing Data fields without triggering CATS Notifications.
The BUT takes the current record and overwrites NMI Standing Data records. The creation and maintenance dates remain unchanged.
BUT does not:
Send notifications to participants.
Create new records.
Prerequisites
Before using the API, see API Requirements in Markets Portal Help. You must also:
Understand the MSATS procedures > Provision and maintenance of CATS Standing Data.
Follow AEMO’s CSV Data Format Standard when creating a csv payload for blind update submissions.
Test your submission in the pre-production environment interface before submitting to production. AEMO encourages participants to use the pre-production environment to test procedures and train staff.
Getting access
To use BlindUpdateTool APIs, participants must:
Be a Registered Participant with a Participant ID.
Have an MSATS user ID with the required Participant User Rights Management (URM) entities granted to it by a participant administrator.
Register with AEMO to use APIs.
During formal onboarding, you are given access to pre-production and must complete your development / testing there prior to getting access to Production.
API details
Authentication Methods
This API uses the following security policies:
Note: Pre-production and production environments use different TLS certificates.
Base URLs
The following table lists the base URLs for this API.
Environment
Base URL
Data Type
Pre-production
https://apis.preprod.aemo.com.au:9319/NEMRetail/BlindUpdate/v1/{resource}
Test-Data (snapshot of production)
MarketNet entry pre-production
https://apis.preprod.marketnet.net.au:9319/NEMRetail/BlindUpdate/v1/{resource}
Test-Data (snapshot of production)
Production
https://apis.prod.aemo.com.au:9319/NEMRetail/BlindUpdate/v1/{resource}
Live Data
MarketNet entry production
https://apis.prod.marketnet.net.au:9319/NEMRetail/BlindUpdate/v1/{resource}
Live Data
Parameters
Paths, headers, request body, and Responses can be found in the Endpoint details.