The MT PASA Offers API allows Scheduled Generators, Market Customers, Market Network Service Providers, and Integrated Resource Providers to submit their MT PASA Offers for Bi-directional Units (BDU), Scheduled Generation Units (SGU), Scheduled Load Units (SLU), and Scheduled Network Services (SNS).
\nMT PASA Offers are input into the MT PASA process.
\nDraft for review. The design is not ready for participants’ builds
\nAPI and JSON or YAML basics.
Before you can use the MT PASA Offer API you must:
\nProd: https://apis.prod.marketnet.net.au:9319/NEMWholesale/v1/MTPASAOffers
\nPre-production: https://apis.preprod.marketnet.net.au:9319/NEMWholesale/v1/MTPASAOffers
\nAPI specification in progress.
\nParticipant administrators provide access to the MT PASA Offer API using the following entities:
\nParticipants Users provide the base-64 encoded URM credentials in the Basic Auth header.
\nYou can submit your API compressed or uncompressed. Compression protocols are gzip or deflate.
\nTo control traffic, AEMO implements Throttling on API Endpoint requests. If Participant ID requests exceed the Throttling limit a HTTP 429 or 422 response returns. For more details, see Response codes below.
\nFor details, see (API Reference > HTTP response)
\nThe submission endpoint allows participants to submit one or more MTPASA Offers.
\nYou provide the Offer details in the Offers array in the JSON schema. Every Submission must supply all required submission level information otherwise AEMO rejects the submission.
\nThis endpoint has payload parameters only (no query parameters).
\n• The weekly energy limit is in MWh.
• The first date must be a future Sunday.
• One Offer File can have many Generating Units (DUIDs).
• Each data line is for one week, notifying the weekly Energy limit and capacity for each day in the week.
• Successive data lines are for the same unit at weekly intervals for the period of the projection (usually two years).
• Rules for use of Reason Codes and Recall Times: TBC
For details, see MT PASA Offers csv Paylod Fields.
\nFor details, see Participant categories, unit states, and recall times.
\nAs well as API, you can use the following interfaces to submit Dispatch Bids ad Offers.
\nA submission request or response has a payload limit of 10 MB (compressed or uncompressed).
\nSubmissions are processed in the order AEMO receives them. You must ensure the correct submission order so your latest Offer is the Effective Offer Submission acknowledged by AEMO’s systems.
\nIf the entire submission is valid you receive a response 200 with transaction ID and other metadata related to the Submission.
\nIf your submission has multiple Units and multiple Trading Days in a single request, and one has an error, AEMO rejects the whole submission.
\nIf your submission has an error AEMO rejects it with a response code, displaying the source of the problem so you can identify its location. Rectify the issue by updating the values appropriately and resubmitting.
\nImmediately after submission, on the Participant File Server > ParticipantID\\Import\\CSV\\Reports folder, you receive a private MTPASA_OFFERFILETRK file with your submission information. For details, see Electricity Data Model, below.
\nYour submission populates the Data Model tables and files mentioned in this section.
\nFor help with:
\nFor help with terms see:
\n\n