ISO Scheduling API Summary

The purpose of this portal is to describe the data structures and processes for inbound and outbound Independent System Operator (ISO) scheduling-related data for the APX MarketSuite® for the following ISOs: PJM, MISO, SPP, ISONE, and NYISO.

This data includes ISO wholesale scheduling transactions such as generator bids, load schedules, generator parameters (such as operating limits) and bilateral schedules.

This page will describe the content of the files exchanged between the APX MarketSuite® and external users’ systems.

For details about the specific API methods and who they are called, refer to the REST APIs section of the portal.

ISO/Market Scope

The portal is designed to support functionality for markets PJM, MISO, SPP, ISONE, and NYISO. Region-specific details are highlighted throughout the portal.

The data structures for the CAISO and ERCOT ISOs are similar, and can be found in a separate page in the portal.

Data Lifecylce

Clients may submit data into the APX MarketSuite® from either the UI or the API. In both cases, all the data in the system is visible through the UI and can be submitted to the ISO via the Checkout application. In the case of API submissions, a flag can be set that will result in the data being submitted immediately to the ISO without requiring any user intervention through the UI.

Data statuses are managed in a variety of ways as supported by the regional ISO. For example, some markets perform a credit check after initial submission, and the APX system periodically checks the status of the submissions by querying the ISO systems.

When submitting data via the API through the Upload File method, clients will receive a file handle (a character string) that represents the file that was uploaded. The uploaded data may also use the external_id field to make it easier to identify and track data being sent to APX MarketSuite®, or to tag it at a level that is more granular than a file. The file handle may be used to query for exception data that was submitted via the API (i.e. data that could not be processed).

Clients may use the GetScheduleData method to obtain the most current schedule data that exists on the APX system.