Unified Projects
Access unified project data combining EIA 860M and interconnection queue sources
Overview
The unified projects endpoint provides a simplified, consolidated view of energy projects by combining data from multiple sources including EIA 860M and major grid operator interconnection queues. This endpoint standardizes project information across different data sources to provide a unified perspective on the energy project landscape.Endpoint
Query Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 1000 | Number of records to return (50-5000) |
offset | integer | 0 | Number of records to skip |
state | string | - | Filter by state code (e.g., CA, TX, NY) |
technology | string | - | Filter by standardized technology type |
status | string | - | Filter by project status |
source_table | string | - | Filter by data source table |
min_capacity | number | - | Minimum capacity (MW) |
max_capacity | number | - | Maximum capacity (MW) |
balancing_authority | string | - | Filter by balancing authority code |
developer | string | - | Filter by developer name (e.g., NextEra, Tesla). Supports partial matches |
Technology Types
Common standardized technology types:| Type | Description |
|---|---|
Solar | Solar photovoltaic |
Wind | Wind turbine |
Battery | Battery energy storage |
Natural Gas | Natural gas generation |
Biomass | Biomass generation |
Hydroelectric | Hydroelectric |
Geothermal | Geothermal |
Project Status
| Status | Description |
|---|---|
Operating | Currently operational |
Planned | Planned/permitted |
Cancelled | Cancelled/withdrawn |
Retired | Retired from service |
Data Sources
Projects are sourced from:| Source | Description |
|---|---|
eia_860m | EIA 860M Monthly data |
caiso_queue | CAISO interconnection queue |
ercot_queue | ERCOT interconnection queue |
pjm_queue | PJM interconnection queue |
miso_queue | MISO interconnection queue |
nyiso_queue | NYISO interconnection queue |
ne_iso_queue | ISO-NE interconnection queue |
spp_queue | SPP interconnection queue |
Developer Information
Developer information is always included in the response when available. Thedeveloper parameter can be used to filter results:
Filtering Options:
- Single developer:
developer=NextEra- Returns projects where developer name contains “NextEra” - Partial matching:
developer=Solar- Returns projects where developer name contains “Solar” (e.g., “First Solar”, “Solar Power Corp”) - Case insensitive: All developer filtering is case-insensitive
Example Requests
Get Solar Projects in California
Get Solar Projects in California
Get Operating Projects
Get Operating Projects
Get Large Projects (>100 MW)
Get Large Projects (>100 MW)
Get Projects from EIA Data Only
Get Projects from EIA Data Only
Get Projects by Specific Developer
Get Projects by Specific Developer
Data Availability Summary
| Source | Hybrid Projects | Status |
|---|---|---|
| PJM, MISO, SPP, NE-ISO, NYISO | 1,343 total | ✅ Full support |
| CAISO, ERCOT, EIA 860M | 0 | ❌ No hybrid classifications |
Complete Documentation
For comprehensive hybrid project guidance including:- ✅ All 4 query methods with code examples
- ✅ Detailed workarounds for sources without hybrid data
- ✅ Root cause analysis and technical limitations
- ✅ Future enhancement roadmap
Response Schema
raw_fields object containing all ISO-specific upstream data. EIA 860M projects return only standardized fields without the raw_fields object.Response Fields
Standardized Fields (All Sources)
| Field | Type | Description |
|---|---|---|
source_table | string | Source data table (eia_860m, caiso_queue, etc.) |
source_id | string | Unique identifier within source table |
project_name | string | Project or facility name |
capacity_mw | number | Capacity in megawatts |
operating_date | string | Operating or proposed online date (YYYY-MM-DD) |
technology | string | Standardized technology type |
county | string | County name |
state | string | State code (CA, TX, NY, etc.) |
balancing_authority | string | Balancing authority code |
status | string | Project status (Operating, Planned, Cancelled, Retired) |
latitude | number | Project latitude in decimal degrees (nullable) |
longitude | number | Project longitude in decimal degrees (nullable) |
developer | string | Developer/owner name |
has_ia_signed | boolean | Whether an Interconnection Agreement has been executed (null for EIA data) |
under_construction | boolean | Whether the project is or was under construction |
ir_request_date | string | Interconnection Request date in YYYY-MM-DD format (null for EIA data) |
Interconnection Milestone Fields
The fieldshas_ia_signed, under_construction, and ir_request_date represent milestone progression through the interconnection process, not just current operational state. This distinction is important for understanding cancelled projects.
status=Cancelled may still show has_ia_signed=true or under_construction=true. This indicates how far the project progressed before being cancelled—valuable for analyzing interconnection queue attrition patterns.Data Availability by Source
| Source | has_ia_signed | under_construction | ir_request_date |
|---|---|---|---|
| EIA 860M | null | Available | null |
| CAISO | Available | null | Available |
| ERCOT | Available | Available | Available |
| PJM | Available | Available | Available |
| MISO | Available | Available | Available |
| NYISO | Available | null | Available |
| ISO-NE | Available | Available | Available |
| SPP | Available | null | Available |
Example: Cancelled Project Analysis
has_ia_signed: true— The project secured an Interconnection Agreementunder_construction: true— Construction had begun before withdrawal- The
status: Cancelledindicates the project is no longer active
ISO-Specific Raw Fields
| Field | Type | Description |
|---|---|---|
raw_fields | object | Nested object containing all ISO-specific upstream data (interconnection queue sources only) |
raw_fields object structure varies by source_table:
- CAISO Queue: See CAISO endpoint documentation for 47 CAISO-specific fields
- ERCOT Queue: See ERCOT endpoint documentation for 45 ERCOT-specific fields
- PJM Queue: See PJM endpoint documentation for 38 PJM-specific fields
- MISO Queue: See MISO endpoint documentation for 41 MISO-specific fields (includes DPP process fields)
- NYISO Queue: See NYISO endpoint documentation for 38 NYISO-specific fields (includes storage fields)
- ISO-NE Queue: See ISO-NE endpoint documentation for 41 ISO-NE-specific fields (includes five-phase study process)
- SPP Queue: See SPP endpoint documentation for 43 SPP-specific fields (includes DISIS cluster data)
- EIA 860M: No raw_fields object - only standardized fields listed above
source_table and source_id fields help identify the original data source for each record.Authorizations
API key authentication using x-api-key header
Query Parameters
Number of records to return
50 <= x <= 5000Number of records to skip
Filter by state code (e.g., CA, TX, NY)
Filter by technology type (Solar, Wind, Battery, etc.)
Filter by project status (Operating, Planned, Cancelled, Retired)
Filter by data source (eia_860m, caiso_queue, ercot_queue, etc.)
Minimum capacity in MW
Maximum capacity in MW
Filter by balancing authority
Response
Successful response