Here are the host environment URLs for the MarketSuite® REST APIs:
https://pmfileapi.apx.comhttps://pmfileapiuat.apx.comThe authentication tokens for the above environments must come from the corresponding UAT/Prod authentication server.
The Upload File Request is designed to support uploading files to the APX MarketSuite®, primarily files for ISO scheduling data. The response is a string representing the file unique identifier (GUID). This identifier can be used to retrieve the file using the Get File method. This identifier can also be used to retrieve the status of all data submitted (for CAISO/ERCOT submissions) or the exception data (other regions) using the GetStatus method.
If the file uploaded is the ISO Scheduling Data xml file, the method does XSD validation of the file and will reject any XML file submissions which are not valid. The ISO Scheduling Data CSV file is also validated for format. The returned error message will include the validation details.
The maximum request size for files uploaded through this Web service is 10MB.
Endpoint (POST): /fileRegistry/file
These parameters must be POST-ed to the endpoint above as URL-encoded form data.
| Field | Description | Available Values | Available Values | Available Values |
|---|---|---|---|---|
| location | ISO code. Values include PJM, ISONE, MISO, SPP, NYISO, MRTU (used for CAISO), TX (used for ERCOT). | CAISO | ERCOT | PJM ISONE MISO SPP NYISO |
| participant | MarketSuite® participant API code. Often, this is the ISO Scheduling code, preceded by some relevant text to make it unique. Please confirm the correct code with your APX Account manager. | MR_SAMPLE | QSAMPLE | PJM_SAMPLE SAMPLE MISO_SAMPLE SPP_SAMPLE NY_SAMPLE |
| intervalBegin | DateTime value marking the start of the interval for the file. The value is in XML DateTime format. This is the date that will be associated with the file when it is registered. The time component should be 00:00, e.g. 2019-11-18T00:00:00, representing start of the day. | 2025-06-01T00:00:00 | 2025-06-01T00:00:00 | 2025-06-01T00:00:00 |
| intervalEnd | DateTime value marking the end of the interval for the file.
| 2025-06-02T00:00:00 | 2025-06-02T00:00:00 | 2025-06-02T00:00:00 |
| fileType | Type of file being uploaded. Valid fileTypes for PJM, ISONE, MISO, SPP, NYISO are:
| APX_NonXmkrt_SchedulingData_CSV APX_Bids_and_Offers | APX_NonXmkrt_SchedulingData_CSV APX_Bids_and_Offers | APX_SchedulingData_CSV APX_SchedulingData_XML |
| source | Name of the source. For ISO Scheduling data submissions, use 'Client' | Client | Client | Client |
| rendition | Some file types have more than one rendition. Those are named sets that look identical but represent different sets. For example: "DA" and "RT" or "Initial", "recalc", and "final". For ISO Scheduling data submissions, use 'DAM' or 'RTM'. | DAM RTM | DAM RTM | DAM RTM |
| file | Byte array representing the compressed data file. |
CAISO/XML
{
"location": "MRTU",
"participant": "MR_SAMPLE",
"intervalBegin": "2024-05-03T00:00:00",
"intervalEnd": "2024-05-04T00:00:00",
"fileType": "APX_Bids_and_Offers",
"source": "Client",
"rendition": "RTM"
}ERCOT/CSV
{
"location": "ERCOT",
"participant": "QSAMPLE",
"intervalBegin": "2025-05-14T00:00:00",
"intervalEnd": "2025-05-15T00:00:00",
"fileType": "APX_NonXmkrt_SchedulingData_CSV",
"source": "Client",
"rendition": "DAM"
}PJM/CSV
{
"location": "PJM",
"participant": "PJM_SAMPLE",
"intervalBegin": "2025-06-01T00:00:00",
"intervalEnd": "2025-06-02T00:00:00",
"fileType": "APX_SchedulingData_CSV",
"source": "Client",
"rendition": "DAM"
}The return value is a string representing the file unique identifier. This identifier can be used to retrieve the file using the GetFile method and to retrieve the ISO scheduling data exception details of the file using the GetStatus method.
The GetStatus Request allows the user to retrieve the exception details of scheduling data uploaded to the APX MarketSuite®. A unique identifier called the File handle is returned from the Upload File Request. This unique identifier is used in the GetStatus Request to retrieve the exception details of the specified file data.
Each exception is returned in the results. Some individual rows may generate more than one exception, in which case one row per exception is returned.
The response of the GetStatus Request is in the form of a compressed XML file.
For CAISO/ERCOT, the returned XML complies with the schema definition ScheduleData.xsd. The full specification appears in the section “APX ISO Scheduling API specification.”
For PJM/ISONE/SPP/MISO/NYISO, the returned XML complies with the schema definition ScheduleData.xsd. The full specification appears in the section “APX ISO Scheduling API specification - xMarket”. Note that in the future other schemas will be returned, depending on the type of file uploaded.
Endpoint (GET): /fileRegistry/file/{fileHandle}/status
These parameters must be POST-ed to the endpoint above as URL-encoded form data.
| Field | Description |
|---|---|
| fileHandle | Unique identifier of the file for which status is being requested. |
A byte array containing the compressed data. The format of the file will be the same as the file that was uploaded: requesting the status of an XML file upload will return results in XML, and a CSV upload will have results in CSV.
Note: The GetStatus Request is recommended for gathering status upon a file upload. The response file contains an overall status and record level statuses.
- FileStatus – reflects the overall status of the file upload. Below is the list of fileStatuses.
| File Status |
|---|
| File load in progress |
| File loaded into system, records successfully retrieved |
| File loaded into system, no records found |
| Error in processing file |
| File does not exist |
| Unrecognized status retrieved from APX MarketSuite transformation; please contact support |
- Status – reflects the status of each bidoffer/resource parameter/bilateral schedule record.
The GetScheduleData request retrieves schedule data from the APX MarketSuite®. From many aspects it can be thought of as the API version of the Checkout application. The requested data sets may include trades, bid-offer or resource parameters, pre-market (APX image or ISO image) or post-market (awards and final schedules and trades).
The data may be requested in either XML or CSV format, and in either case will be in the same format as for uploads, with some additional info for status of the data.
The response of the GetScheduleData Request is in the form of a compressed XML file.
For CAISO/ERCOT, the returned XML complies with the schema definition ScheduleData.xsd. The full specification appears in the section “APX ISO Scheduling API specification.”
For PJM/ISONE/SPP/MISO/NYISO, the returned XML complies with the schema definition ScheduleData.xsd. The full specification appears in the section “APX ISO Scheduling API specification - xMarket”. Note that in the future other schemas will be returned, depending on the type of file uploaded.
Endpoint (PUT): /fileRegistry/getScheduleData/{fileName}
These parameters must be POST-ed to the endpoint above as URL-encoded form data.
| Field | Description |
|---|---|
| fileName (in endpoint) | The name of the file that will be created in the zip archive that is sent back as the return parameter. Clients can specify the file name and then use it to extract the contents of the zip archive. |
| region | ISO code. Values include PJM, ISONE, MISO, SPP, NYISO, MRTU (used for CAISO), TX (used for ERCOT). |
| marketParticipants | List of MarketSuite® participant codes for which the method should return data. Often, this is the ISO Scheduling code, preceded by some relevant text to make it unique. Please confirm the correct code with your APX Account manager. |
| marketStage | Market stage of the requested data |
| marketStatus | ‘Pre’ or ‘Post’—pre-market data with its status, or post-market awards. NOTE: Post-market awards only available for CAISO(MRTU) and ERCOT (TX). Post-market awards for other regions coming soon. |
| firstIntervalBegin | Required parameter that specifies the starting date for which data is being requested. |
| lastIntervalEnd | For PJM, ISONE, SPP, MISO, and NYISO required parameter that specifies the ending date for which data is being requested. If not given, default is tradeDate+1 day. Note: Not allowed for CAISO(MRTU) or ERCOT(TX), where each request may only be for one day. |
| applications | ‘BidsOffers’, ‘BilateralSchedules’, and/or ‘ResourceParameters’—applications for which data is being requested. Note: For PJM, ISONE, SPP, MISO, and NYISO, request is limited to ‘BilateralSchedule’ OR BidsOffers/ResourceParameters. |
| format | CSV or XML. XML will comply with the schema definition ScheduleData.xsd. CSV will be same format used for upload. |
A byte array containing the compressed data file.
The File List Request is designed to retrieve a list files which can be downloaded from the APX MarketSuite®. The response returns an array of file_list_items.
Endpoint (PUT): /fileRegistry/listFiles
These parameters must be POST-ed to the endpoint above as URL-encoded form data.
| Field | Description |
|---|---|
| region | ISO code. Values include PJM, ISONE, MISO, SPP, NYISO, MRTU (used for CAISO), TX (used for ERCOT). |
| participant | MarketSuite® participant API code. Often, this is the ISO Scheduling code, preceded by some relevant text to make it unique. Please confirm the correct code with your APX Account manager. |
| fileType | Type of file included in the list. |
| source | Data source of the files to search for. |
| rendition | Some file types have more than one rendition. Those are named sets that look identical but represent different sets. For example: “DA” and ”RT” or “Initial”, ”recalc”, and “final”. |
| latestVersionOnly | Flag indicating whether or not to list the most recent version of a file. True means list the most recent version only. False means list all versions. The default is true. |
A json array of file_list_items. file_list_items include the following properties:
| Field | Description |
|---|---|
| location | The name of the ISO or more granular location designation if one was specified when the file was registered. |
| participant | The name of the participant associated with this file |
| intervalBegin | DateTime value of interval_begin that was specified when the file was uploaded or otherwise registered. This is not necessarily true for the content of the file. |
| intervalEnd | Date time value of interval_end that was specified when the file was uploaded or otherwise registered. This is not necessarily true for the content of the file. |
| source | Data source of the files to search for. |
| rendition | Some file types have more than one rendition. Those are named sets that look identical but represent different sets. For example: “DA” and ”RT” or “Initial”, ”recalc”, and “final”. |
| fileType | Type of file included in the list. |
| fileVersion | The version of the file. |
| fileStructureVersion | The version of the structure of the file |
| fileFormat | The format of the file (CSV, XML, MDEF, etc.) |
| fileHandle | The handle of the file used to retrieve the file in the GetFile method |
| createDate | The create date of the file |
The File List Since Request is designed to retrieve a list files which can be downloaded from the APX MarketSuite® which have changed since the specified date. The response returns an array of file_list_items.
Endpoint (PUT): /fileRegistry/listFilesSince
These parameters must be POST-ed to the endpoint above as URL-encoded form data.
| Field | Description |
|---|---|
| region | ISO code. Values include PJM, ISONE, MISO, SPP, NYISO, MRTU (used for CAISO), TX (used for ERCOT). |
| participant | MarketSuite® participant API code. Often, this is the ISO Scheduling code, preceded by some relevant text to make it unique. Please confirm the correct code with your APX Account manager. |
| fileType | Type of file included in the list. |
| source | Data source of the files to search for. |
| rendition | Some file types have more than one rendition. Those are named sets that look identical but represent different sets. For example: “DA” and ”RT” or “Initial”, ”recalc”, and “final”. |
| latestVersionOnly | Flag indicating whether or not to list the most recent version of a file. True means list the most recent version only. False means list all versions. The default is true. |
| watermarkDate | DateTime value indicating the last date/time that files were fetched, results in the new list including only files that have changed since that date/time (the creation date is greater than and not equal to the watermark date). The value is in XML DateTime format which includes the GMT offset. |
| newWatermarkDate | Output DateTime value to use as the watermark_date in the next GetListSince call. The value is the maximum create_date of the files returned in the list. The value is in XML DateTime format which includes the GMT offset. |
A json array of file_list_items. file_list_items include the following properties:
| Field | Description |
|---|---|
| location | The name of the ISO or more granular location designation if one was specified when the file was registered. |
| participant | The name of the participant associated with this file |
| intervalBegin | DateTime value of interval_begin that was specified when the file was uploaded or otherwise registered. This is not necessarily true for the content of the file. |
| intervalEnd | Date time value of interval_end that was specified when the file was uploaded or otherwise registered. This is not necessarily true for the content of the file. |
| source | Data source of the files to search for. |
| rendition | Some file types have more than one rendition. Those are named sets that look identical but represent different sets. For example: “DA” and ”RT” or “Initial”, ”recalc”, and “final”. |
| fileType | Type of file included in the list. |
| fileVersion | The version of the file. |
| fileStructureVersion | The version of the structure of the file |
| fileFormat | The format of the file (CSV, XML, MDEF, etc.) |
| fileHandle | The handle of the file used to retrieve the file in the GetFile method |
| createDate | The create date of the file |
The File Download Request is designed to retrieve a specific file from the APX MarketSuite®. The file is returned in a zip file byte array.
Endpoint (GET): /fileRegistry/file/{fileHandle}
| Field | Description |
|---|---|
| fileHandle (in endpoint) | Unique string used to identify the file in the APX MarketSuite®. |
| file_name | Output parameter, the name of the file inside the compressed byte array |
A byte array containing the compressed data file.
The Report Download Request is designed to retrieve data from the APX MarketSuite® in the specified format. The data file is returned in a zip file byte array.
Endpoint (PUT): /reporting/getReport
| Field | Description |
|---|---|
| reportPath | The report-specific path for the report to run. See Appendix C for reports and paths. |
| [key/value pairs] | Parameter name/value pairs required to run the report. These are the report-specific parameters that will be unique for each report. See Appendix C for report-specific parameters (keys). |
| reportFormat | Output file format – CSV, Excel, and XML. |
A byte array containing the compressed data file.