Interconnection Queues Data Guide

Overview

This API provides standardized access to interconnection queue data from all 7 major ISOs/RTOs in the United States. Each ISO has unique field structures and naming conventions, which our API standardizes into consistent field names and technology classifications.

ISO/RTO Coverage

Major Regional Operators

ISO Code	Full Name	Geographic Coverage	States Served
CISO	California Independent System Operator	California and parts of Nevada	CA, NV
ERCO	Electric Reliability Council of Texas	Most of Texas	TX
PJM	PJM Interconnection	Mid-Atlantic and Midwest	DE, IL, IN, KY, MD, MI, NJ, NC, OH, PA, TN, VA, WV, DC
MISO	Midcontinent Independent System Operator	Midwest and South	AR, IA, IL, IN, KY, LA, MI, MN, MO, MS, MT, ND, TX, WI
NYIS	New York Independent System Operator	New York State	NY
ISNE	ISO New England	New England	CT, MA, ME, NH, RI, VT
SWPP	Southwest Power Pool	Central United States	AR, KS, LA, MO, NE, NM, OK, TX, portions of IA, MN, MT, ND, SD, WY

These ISO codes align with EIA balancing authority codes used in official federal energy data reporting, including EIA-860M Monthly Generator Reports. For complete EIA balancing authority code references, see the EIA-860M documentation.Official ISO Documentation:

CAISO Generator Interconnection (Official CAISO interconnection process page)
CAISO Business Practice Manual for GIDAP (Detailed procedures manual)
ERCOT Planning Guide (Section 5: Generation Resource Interconnection)
ERCOT Resource Integration (Interconnection process guidance)
PJM Manual 14C (Generation and Transmission Interconnection Process)
PJM Interconnection Library (Complete manual library)
MISO Business Practices Manual (Generator Interconnection procedures)
For geographic coverage, see FERC Electric Industry Forms

Technology Classifications

Each ISO uses slightly different terminology to describe project technologies. For example, one ISO might list a project as “Photovoltaic,” another as “Solar PV,” and a third as simply “Solar.” These inconsistencies make it difficult to compare technologies across datasets or group them for analysis without extensive cleaning. To solve this, we normalize technology terms into a standardized set of categories. This ensures consistent labeling across projects, regardless of the original source, and makes it easier for users to filter by technology type, track deployment trends, or compare development pipelines across geographies and markets. We also provide the original technology column to enable users to do their own standardizations or in-depth data ISO-specific analysis. The table below outlines our core technology classifications and shows how common ISO-specific terms are mapped into each category.

Standardized Technology Types

Standard Technology	Description	Common ISO Variations
Solar	Solar photovoltaic projects	Photovoltaic, Solar PV, PV, Solar
Wind	Onshore and offshore wind	Wind Turbine, Wind, Onshore Wind, Offshore Wind
Battery	Battery energy storage systems	Storage, Battery Storage, BESS, Energy Storage
Hybrid - Solar + Storage	Co-located solar and battery	Solar + Storage, Hybrid Solar
Hybrid - Wind + Storage	Co-located wind and battery	Wind + Storage, Hybrid Wind
Hybrid - Solar + Wind	Co-located solar and wind	Solar + Wind
Natural Gas	Natural gas generation	Gas, Combined Cycle, Simple Cycle, Combustion Turbine
Nuclear	Nuclear power generation	Nuclear
Hydroelectric	Hydroelectric generation	Hydro, Water, Hydroelectric
Geothermal	Geothermal generation	Geothermal, Steam Turbine (Geothermal)
Biomass	Biomass and biofuel generation	Biofuel, Wood, Landfill Gas
Coal	Coal generation	Coal, Steam Turbine (Coal)
Other	Other technologies	Fuel Cell, Hydrogen, Transmission

ISO-Specific Technology Field Differences

CAISO Special Case: CAISO structures technology data differently from other ISOs. While most ISOs use a single field for technology classification, CAISO uses separate technology and fuel fields:

technology: Contains CAISO’s original technical terms (e.g., “Photovoltaic”, “Storage”)
fuel: Contains standardized fuel types (e.g., “Solar”, “Battery”)

Impact on Filtering: When using technology=Solar filter on CAISO data, the API automatically searches both fields to ensure consistent results. This means you’ll get projects where either:

technology field contains “Solar” OR
fuel field contains “Solar”

Example CAISO Response:

{
  "technology": "Photovoltaic",
  "fuel": "Solar",
  "technology_normalized": "Solar"
}

This approach ensures cross-ISO compatibility while preserving CAISO’s original data structure.

How We Handle Hybrid Projects

Hybrid projects present unique data challenges because each ISO handles them differently in their source data. Our API provides standardized hybrid technology classifications while preserving these original data structures:

CAISO: Represents hybrid projects as single rows in their Excel files with multiple technology columns (Type-1, Type-2, Type-3). Our API splits these into separate records for each technology component, allowing you to query individual components while maintaining relationships through the site_id field.
ERCOT: Unlike CAISO, ERCOT’s Excel files already contain separate rows for each technology component, each with its own INR number. Co-located hybrid projects appear as multiple records with similar naming patterns (e.g., “Lupinus Solar 1-3” and “Lupinus Storage 1-3”).
PJM: Uses single rows with semicolon-separated technology combinations in the fuel column (e.g., “Solar; Storage”, “Wind; Storage”).
SPP: Single rows with slash-separated combinations in the fuel_type field and a generation_type value of “Hybrid” (e.g., fuel_type=“Solar/Storage”).
MISO: Single rows where fuel_type=“Hybrid” and the facility_type field specifies the combination (e.g., “Solar/Battery”, “Wind/Battery”).
NYISO: Uses single-letter hybrid codes like “CR” (Combined Renewable = Solar + Storage) and “CW” (Combined Wind = Wind + Storage).
ISO-NE: Represents hybrids with space-separated fuel codes in single rows (e.g., “SUN BAT” for Solar + Battery).

Key Insight: The fundamental difference is that CAISO uses multiple columns within one row for hybrid projects, while ERCOT uses multiple rows. All other ISOs use single rows with various encoding schemes to represent the hybrid nature.

Detailed Raw Data Formats by ISO

Raw Excel Structure: Single row per project with multiple technology columns

Type-1, Type-2, Type-3 columns for different technologies
MW-1, MW-2, MW-3 columns for corresponding capacities
Fuel-1, Fuel-2, Fuel-3 columns for fuel types

API Response: Each technology component appears as a separate record in our API response. This allows you to:

Query individual technology components
Track capacity by technology type
Group related components using the site_id field

Example: A 100 MW solar + 50 MW battery project in CAISO’s Excel (Type-1=“Photovoltaic”, MW-1=100, Type-2=“Storage”, MW-2=50) becomes two API records with the same site_id.

Raw Excel Structure: Single row with combined technology field

Fuel column contains semicolon-separated values (e.g., “Solar; Storage”)
Single capacity value represents total project capacity

API Response: Single record per hybrid project with:

Original combined technology string preserved in the fuel field
technology_normalized field set to appropriate hybrid category (e.g., “Hybrid - Solar + Storage”)
Total project capacity (individual component capacities not available)

Example: A hybrid project appears as one API record with fuel=“Solar; Storage”, technology_normalized=“Hybrid - Solar + Storage”, capacity_mw=150

Raw CSV Structure: Single row with dual classification

“Fuel” column indicates hybrid status (value: “Hybrid”)
“Generating Facility” column specifies the combination (e.g., “Solar/Battery”)
Separate “Summer MW” and “Winter MW” columns

API Response: Single record per hybrid project with:

fuel field showing “Hybrid”
technology field showing the facility type (e.g., “Solar/Battery”)
technology_normalized mapped to standard hybrid categories
Both summer_capacity_mw and winter_capacity_mw values

Example: API record shows fuel=“Hybrid”, technology=“Solar/Battery”, technology_normalized=“Hybrid - Solar + Storage”, summer_capacity_mw=100, winter_capacity_mw=100

Raw CSV Structure: Single row with dual fields

“Generation Type” column (e.g., “Hybrid”)
“Fuel Type” column with slash notation (e.g., “Solar/Storage”)

API Response: Single record showing both generation_type and fuel_type fields, with technology_normalized based on the combination.Example: generation_type=“Hybrid”, fuel_type=“Solar/Storage”, technology_normalized=“Hybrid - Solar + Storage”

Raw Excel Structure: Single row with coded values

“Type/Fuel” column uses single-letter codes
CR = Combined Renewable (Solar + Storage)
CW = Combined Wind (Wind + Storage)

API Response: Single record with the code translated to readable technology types in the technology_normalized field while preserving the original code in the type_fuel field.Example: type_fuel=“CR”, technology_normalized=“Hybrid - Solar + Storage”

Key Insight: The fundamental difference is that CAISO’s raw Excel uses multiple columns within one row, while ERCOT uses multiple rows. All other ISOs use single rows with various encoding schemes to represent the hybrid nature.

Important Implications for Data Analysis

When analyzing hybrid projects across ISOs, be aware that:

Capacity Attribution:
- CAISO & ERCOT: Individual component capacities are available
- PJM, MISO, SPP: Only total project capacity is provided
- This affects capacity summation and technology-specific analysis
Project Counting:
- CAISO: One Excel row can become multiple API records
- ERCOT: Already multiple rows in source data
- Others: One-to-one mapping maintained
Relationship Tracking:
- CAISO: Use site_id to group related components
- ERCOT: No formal linking - use project name patterns
- Others: Single record represents the entire hybrid project

Status Classifications

Each ISO uses different terminology for project status, creating complexity when comparing across markets. We standardize these into five consistent categories—Planned, Operating, Cancelled, Retired, and Inactive—while preserving original status fields for detailed ISO-specific analysis. This standardization allows you to filter, analyze, and benchmark projects reliably across regions while maintaining access to ISO-specific terminology when needed. Below, you’ll find how we map common status terms from each ISO into our standardized framework. This mapping is designed to preserve as much fidelity as possible while reducing ambiguity for downstream analysis.

Standardized Status Types

Standard Status	Description	Common ISO Variations
Planned	Active projects in interconnection process	Active, In Progress, Under Study
Operating	Projects that have achieved commercial operation	Completed, Commercial, In Service
Cancelled	Projects withdrawn or terminated	Withdrawn, Terminated, Cancelled
Retired	Operating projects that have been retired	Retired, Decommissioned
Inactive	Projects with suspended or unclear status	Suspended, On Hold, Inactive

Status Mapping by ISO

All status mappings are implemented in our API’s status mapping service. CAISO Status Mapping

“Active” → Planned
“Completed” → Operating
“Withdrawn” → Cancelled

ERCOT Status Mapping

“Active” → Planned
“Commercial Operation” → Operating
“Cancelled” → Cancelled
“Inactive” → Inactive
“Approved for energization” → Planned
“Approved for synchronization” → Planned

PJM Status Mapping

“Active” → Planned
“In Service” → Operating
“Withdrawn” → Cancelled
“Engineering and Procurement” → Planned
“Confirmed” → Planned
“Under Construction” → Planned
“Suspended” → Inactive
“Deactivated” → Inactive
“Retracted” → Cancelled
“Annulled” → Cancelled

MISO Status Mapping

“Active” → Planned
“Done” → Operating
“Withdrawn” → Cancelled

NYISO Status Mapping

“Active” → Planned
“In Service” → Operating
“Withdrawn” → Cancelled

ISO-NE Status Mapping

“Under Study” → Planned (active projects) or Inactive (withdrawn projects)
“Under Construction” → Planned
“In Service” → Operating
“Partially In Service” → Planned
“Suspended” → Inactive

SPP Status Mapping

“Active” → Planned
“In service” → Operating
“Inactive” → Inactive
“WITHDRAWN” → Cancelled
“TERMINATED” → Cancelled

Field Definitions

Core Standardized Fields

Field Name	Type	Description	Availability
`iso`	string	ISO/RTO identifier	All ISOs
`queue_id`	string	Unique queue identifier	All ISOs
`project_name`	string	Project name	Most ISOs
`capacity_mw`	number	Project capacity in MW	All ISOs
`technology`	string	Standardized technology type	All ISOs
`status`	string	Standardized project status	All ISOs
`operating_date`	date	Planned/actual commercial operation date	Most ISOs
`request_date`	date	Date entered queue	Most ISOs
`state`	string	State code (CA, TX, etc.)	Most ISOs
`county`	string	County name	Most ISOs

Additional Fields by ISO

In addition to the core standardized fields listed above, each ISO has its own ISO-specific fields that provide additional details relevant to that region’s interconnection process. These fields preserve the original data structure and terminology from each ISO’s queue, allowing for detailed ISO-specific analysis.

Data Quality Notes

Field Availability

ISO	Project Names	Coordinates	Study Status
CAISO	✅ Always	❌ Not available	✅ Detailed
ERCOT	✅ Always	❌ Not available	✅ Detailed
PJM	✅ Usually	❌ Not available	✅ Detailed
MISO	❌ Limited	❌ Not available	✅ Basic
NYISO	✅ Usually	❌ Not available	✅ Basic
ISO-NE	✅ Usually	❌ Not available	✅ Basic
SPP	❌ Limited	❌ Not available	✅ Basic

Common Filtering Patterns

By Technology

technology=Solar
technology=Solar,Wind,Battery

By Status

status=Planned
status=Operating

By Capacity

min_capacity=100
max_capacity=500

By Location

state=CA
states=CA,TX,NY
county=Los Angeles

By Timeline

cod_start=2024-01-01
cod_end=2025-12-31
queue_date_start=2020-01-01

API Response Structure

All interconnection endpoints return data in this standardized format:

{
  "success": true,
  "data": [
    {
      "iso": "CISO",
      "queue_id": "1379_photovoltaic", 
      "project_name": "Heartland Solar 1",
      "capacity_mw": 156.04,
      "technology": "Solar",
      "status": "Planned",
      // ... additional fields
    }
  ],
  "iso": "CISO",
  "pagination": {
    "limit": 50,
    "offset": 0,
    "total": 3027,
    "has_more": true,
    "current_page": 1,
    "total_pages": 61
  },
  "filters": {
    // Applied filters
  },
  "customer": {
    "id": "customer_id",
    "name": "Customer Name"
  }
}

Usage Examples

Find Large Solar Projects in California

curl -H "x-api-key: your_api_key" \
  "https://api.cleanview.co/api/v1/interconnection/caiso?technology=Solar&min_capacity=100&state=CA&limit=50"

Get Active Battery Storage Projects

curl -H "x-api-key: your_api_key" \
  "https://api.cleanview.co/api/v1/interconnection/ercot?technology=Battery&status=Planned&limit=50"

Find Projects by Multiple Technologies

curl -H "x-api-key: your_api_key" \
  "https://api.cleanview.co/api/v1/interconnection/pjm?technology=Solar,Wind&limit=50"

For optimal performance, use specific filters to narrow your results. The API works best with targeted queries rather than broad data exports.

Overview

EIA Data