> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cleanview.co/llms.txt
> Use this file to discover all available pages before exploring further.
# ERCOT Interconnection Queue
> Access real-time ERCOT interconnection queue data for all power projects
## Overview
The ERCOT interconnection queue endpoint provides access to real-time data from the Electric Reliability Council of Texas (ERCOT) interconnection queue, which serves most of Texas.
**ERCOT Coverage**: Contains **2,200+ projects** primarily in Texas (99%). Top technologies: Solar (800+ projects), Wind (400+ projects), Battery Storage (350+ projects).
**Hybrid Projects**: ERCOT represents each technology component of hybrid projects (e.g., solar + storage) as separate rows in their Excel source files with different INR numbers. Our API maintains this structure. See our [comprehensive guide on hybrid project handling](/api-reference/interconnection-codes#how-we-handle-hybrid-projects) for details.
## Endpoint
```bash cURL theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/interconnection/ercot?limit=50"
```
```javascript JavaScript theme={null}
const response = await fetch('https://api.cleanview.co/api/v1/interconnection/ercot?limit=50', {
headers: {
'x-api-key': 'your_api_key_here'
}
});
const data = await response.json();
```
```python Python theme={null}
import requests
headers = {'x-api-key': 'your_api_key_here'}
response = requests.get(
'https://api.cleanview.co/api/v1/interconnection/ercot?limit=50',
headers=headers
)
data = response.json()
```
## 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 (primarily TX) - supports comma-separated |
| `technology` | string | - | Filter by standardized technology type - supports comma-separated |
| `status` | string | - | Filter by standardized status |
| `min_capacity` | number | - | Minimum capacity in MW |
| `max_capacity` | number | - | Maximum capacity in MW |
| `developer` | string | - | Filter by developer name (supports partial matches) |
### Technology Options
Use standardized technology names. See our [Interconnection Reference](/api-reference/interconnection-codes#technology-classifications) for all available options.
| Technology | Count | Description |
| ------------- | ----- | ------------------------------ |
| `Solar` | 800+ | Solar photovoltaic projects |
| `Wind` | 400+ | Wind turbine projects |
| `Battery` | 350+ | Battery energy storage systems |
| `Natural Gas` | 150+ | Natural gas generation |
| `Other` | 300+ | Other technologies |
### Status Options
| Status | Count | Description |
| ----------- | ------ | ----------------------------- |
| `Planned` | 1,500+ | Active projects in queue |
| `Operating` | 400+ | Commercial operation achieved |
| `Cancelled` | 300+ | Withdrawn or terminated |
## Example Requests
```bash theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/interconnection/ercot?technology=Solar&status=Planned&state=TX&limit=50"
```
Returns active solar projects in the ERCOT queue. Uses `technology=Solar` for standardized filtering.
```bash theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/interconnection/ercot?technology=Wind&min_capacity=200&limit=50"
```
Finds large-scale wind projects. Uses `technology=Wind` for wind turbine projects.
```bash theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/interconnection/ercot?technology=Battery&limit=50"
```
Filters for battery energy storage projects.
```bash theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/interconnection/ercot?technology=Solar,Wind,Battery&limit=50"
```
Uses comma-separated values for multiple technology filtering.
## Response Schema
```json Example Response theme={null}
{
"iso": "ERCOT",
"summary": {
"limit": 50,
"offset": 0,
"total_results": 2234,
"has_more": true,
"current_page": 1,
"total_pages": 45
},
"filters": {
"state": null,
"technology": null,
"status": null,
"min_capacity": null,
"max_capacity": null,
"developer": null
},
"data": [
{
"iso": "ERCO",
"queue_id": "12INR0059b",
"project_name": "HOVEY (Barilla Solar 1B)",
"capacity_mw": 7.4,
"technology": "Photovoltaic Solar",
"fuel": "SOL",
"status": "Planned",
"detailed_status": "Active",
"operating_date": "2025-11-30T08:00:00.000Z",
"request_date": null,
"county": "Pecos",
"state": "TX",
"queue_position": null,
"interconnecting_entity": "First Solar",
"developer": "Unable to find",
"gim_study_phase": null,
"screening_study_started": null,
"screening_study_complete": null,
"fis_requested": null,
"fis_approved": null,
"ia_signed": "2013-12-26T08:00:00.000Z",
"poi_location": "60385 Solstice 138kV",
"cdr_reporting_zone": "WEST",
"technology_display": "Photovoltaic Solar",
"fuel_display": "Solar",
"balancing_authority_code": "ERCO",
"technology_normalized": "Solar",
"inr_request_number": "12INR0059b",
"projected_cod": "2025-11-30T08:00:00.000Z",
"changes_from_last_report": null,
"proof_of_site_control": null,
"economic_study_required": null,
"financial_security": true,
"air_permit": null,
"ghg_permit": null,
"water_availability": null,
"meets_691_requirements": null,
"meets_69_requirements": null,
"meets_59_requirements": null,
"construction_start": null,
"construction_end": null,
"approved_for_energization": "2015-09-02T07:00:00.000Z",
"approved_for_synchronization": "2015-09-14T07:00:00.000Z",
"comment": null,
"size_category": "Small",
"model_ready_date": "2015-09-02T07:00:00.000Z",
"change_indicators": null,
"approved_for_commercial_operation": null,
"status_last_updated": null
}
]
}
```
**Complete Upstream Data**: Each project includes all 49 database columns from ERCOT's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and ERCOT-specific raw fields like `inr_request_number`, `screening_study_required`, and `planned_outage_season`.
## Response Fields
### Core Identification Fields
| Field | Type | Description |
| -------------------------- | ------ | --------------------------------------------- |
| `iso` | string | Always "ERCO" for ERCOT data |
| `queue_id` | string | Unique ERCOT queue identifier |
| `project_name` | string | Official project name in ERCOT queue |
| `inr_request_number` | string | Interconnection Request (INR) number |
| `balancing_authority_code` | string | Always "ERCO" |
| `queue_position` | string | Queue position (null - not provided by ERCOT) |
### Capacity & Technology
| Field | Type | Description |
| ----------------------- | ------ | ---------------------------------------------------- |
| `capacity_mw` | number | Project nameplate capacity in MW |
| `technology` | string | Technology type (e.g., "Photovoltaic Solar", "Wind") |
| `technology_display` | string | ERCOT's display technology description |
| `technology_normalized` | string | Standardized technology for cross-ISO filtering |
| `fuel` | string | ERCOT fuel code (SOL, WND, GAS, etc.) |
| `fuel_display` | string | Human-readable fuel type description |
### Project Status & Dates
| Field | Type | Description |
| --------------------- | ------ | --------------------------------------------------- |
| `status` | string | Standardized status (Planned, Operating, Cancelled) |
| `detailed_status` | string | Original ERCOT status (e.g., "Active") |
| `operating_date` | date | Expected/actual commercial operation date |
| `projected_cod` | date | Projected commercial operation date |
| `request_date` | date | Interconnection request date (often null) |
| `status_last_updated` | date | Date status was last updated |
### Location
| Field | Type | Description |
| -------- | ------ | ------------------------------------ |
| `state` | string | State code (primarily TX) |
| `county` | string | County name where project is located |
### Grid Connection
| Field | Type | Description |
| ------------------------ | ------ | ------------------------------------------- |
| `interconnecting_entity` | string | Interconnection customer/developer name |
| `poi_location` | string | Point of Interconnection with voltage level |
| `cdr_reporting_zone` | string | CDR zone (NORTH, SOUTH, WEST, HOUSTON) |
### Study Process & Milestones
| Field | Type | Description |
| -------------------------- | ------ | ---------------------------------------------------- |
| `gim_study_phase` | string | Generation Interconnection & Model (GIM) study phase |
| `screening_study_started` | date | Screening study start date |
| `screening_study_complete` | date | Screening study completion date |
| `fis_requested` | date | Facility Impact Study (FIS) requested date |
| `fis_approved` | date | Facility Impact Study approved date |
| `ia_signed` | date | Interconnection Agreement (IA) signed date |
### Project Requirements & Permits
| Field | Type | Description |
| ------------------------- | ------- | ----------------------------------------------- |
| `proof_of_site_control` | boolean | Site control documentation status |
| `economic_study_required` | boolean | Whether economic study is required |
| `financial_security` | boolean | Financial security posting status |
| `air_permit` | boolean | Air quality permit status |
| `ghg_permit` | boolean | Greenhouse gas permit status |
| `water_availability` | boolean | Water availability documentation status |
| `meets_691_requirements` | boolean | Meets Planning Guide Section 6.9.1 requirements |
| `meets_69_requirements` | boolean | Meets Planning Guide Section 6.9 requirements |
| `meets_59_requirements` | boolean | Meets Planning Guide Section 5.9 requirements |
### Construction & Energization
| Field | Type | Description |
| ----------------------------------- | ---- | ----------------------------------------- |
| `construction_start` | date | Construction start date |
| `construction_end` | date | Construction completion date |
| `approved_for_energization` | date | Date approved for energization |
| `approved_for_synchronization` | date | Date approved for synchronization to grid |
| `approved_for_commercial_operation` | date | Date approved for commercial operation |
| `model_ready_date` | date | Date project model was ready |
### Project Tracking
| Field | Type | Description |
| -------------------------- | ------ | -------------------------------------------------- |
| `size_category` | string | Project size classification (Small, Medium, Large) |
| `changes_from_last_report` | string | Notable changes since last queue report |
| `change_indicators` | string | Indicators of project changes |
| `comment` | string | Additional ERCOT comments or notes |
### Developer Information
| Field | Type | Description |
| ----------- | ------ | ---------------------------------------- |
| `developer` | string | Developer name from Cleanview enrichment |
**Data Updates**: ERCOT queue data is updated weekly. The API reflects the most recent Generation Interconnection Request (GIR) data available from ERCOT.
**Unique Features**: ERCOT data includes detailed point of interconnection information (`poi_location`) and congestion zone mapping (`cdr_reporting_zone`), making it excellent for grid analysis.
**Missing Coordinates**: ERCOT data does not include latitude/longitude coordinates. Use the `county`, `poi_location`, and `cdr_reporting_zone` fields for geographic analysis.
## OpenAPI
````yaml GET /interconnection/ercot
openapi: 3.0.0
info:
title: Cleanview Public API
version: 0.1.0
description: >-
RESTful API for accessing clean energy data including EIA capacity and ISO
queue information
contact:
name: Cleanview Energy
url: https://cleanview.co/demo
servers:
- url: https://api.cleanview.co/api/v1
description: Production server
security:
- ApiKeyAuth: []
paths:
/interconnection/ercot:
get:
tags:
- Interconnection
summary: Get ERCOT interconnection queue data
description: >-
Retrieve real-time interconnection queue data from the Electric
Reliability Council of Texas (ERCOT)
parameters:
- in: query
name: limit
schema:
type: integer
minimum: 50
maximum: 5000
default: 50
description: Number of records to return
- in: query
name: offset
schema:
type: integer
default: 0
description: Number of records to skip
- in: query
name: state
schema:
type: string
description: Filter by state code (TX)
example: TX
- in: query
name: technology
schema:
type: string
description: Filter by technology type
example: Solar
- in: query
name: min_capacity
schema:
type: number
description: Minimum capacity in MW
example: 100
- in: query
name: max_capacity
schema:
type: number
description: Maximum capacity in MW
example: 500
responses:
'200':
description: Successful response with ERCOT interconnection queue data
content:
application/json:
schema:
type: object
properties:
iso:
type: string
example: ERCOT
summary:
$ref: '#/components/schemas/Summary'
filters:
type: object
description: Applied filters for the request
data:
type: array
description: Array of interconnection queue records
items:
type: object
properties:
iso:
type: string
example: PJM
queue_id:
type: string
example: AB1-234
project_name:
type: string
example: Sample Solar Project
capacity_mw:
type: number
example: 156.04
technology:
type: string
example: Solar
status:
type: string
example: Planned
state:
type: string
example: PA
county:
type: string
example: Allegheny
'400':
description: Invalid request parameters
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- ApiKeyAuth: []
components:
schemas:
Summary:
type: object
description: Summary metadata for pagination
properties:
limit:
type: integer
description: Number of records per page
offset:
type: integer
description: Number of records to skip
total_results:
type: integer
description: Total number of records matching the query
has_more:
type: boolean
description: Whether additional records exist beyond this page
current_page:
type: integer
description: Current page number (1-indexed)
total_pages:
type: integer
description: Total number of pages available
Error:
type: object
description: Standardized error response structure
required:
- error
- message
properties:
error:
type: string
description: Error code identifier for programmatic handling
enum:
- INVALID_API_KEY
- API_KEY_NOT_FOUND
- INVALID_LIMIT
- INVALID_OFFSET
- INVALID_STATUS
- INVALID_CAPACITY
- INVALID_TECHNOLOGY
- INVALID_STATES
- INVALID_DATE
- INVALID_DATE_RANGE
- INVALID_BOOLEAN
- DATABASE_ERROR
- INTERNAL_ERROR
example: INVALID_LIMIT
message:
type: string
description: Human-readable error description
example: Limit must be at least 50 records per request
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: x-api-key
description: API key authentication using x-api-key header
````