Interconnection Queue API Overview

The Cleanview API provides access to interconnection queue data from 7 major grid operators across the United States. Our API is designed with a focus on reliability and simplicity, offering the most valuable parameters for data analysis and pipeline applications.

Available Grid Operators

ISO/RTOStates ServedProject CountTop Technologies
CAISOCA, NV, AZ3,000+Solar, Battery, Wind
ERCOTTX2,200+Solar, Wind, Hybrid
PJM13 Mid-Atlantic states1,800+Solar, Natural Gas, Wind
MISO15 Midwest/South states1,500+Wind, Solar, Natural Gas
SPP8 Central states800+Wind, Solar, Battery
NYISONY400+Solar, Wind, Battery
ISO-NE6 New England states300+Solar, Wind, Battery

Supported Parameters

All interconnection endpoints support a streamlined set of parameters designed for data pipeline and analysis use cases:

Core Filtering Parameters

  • state - Filter by state code (e.g., CA, TX, NY) - supports comma-separated values
  • technology - Filter by technology type (e.g., Solar, Wind, Battery) - supports comma-separated values
  • status - Filter by project status (Operating, Planned, Cancelled, etc.)
  • min_capacity - Minimum capacity in MW (numeric)
  • max_capacity - Maximum capacity in MW (numeric)

Pagination Parameters

  • limit - Number of records per page (50-5000, default: 1000)
  • offset - Number of records to skip (default: 0)

Parameter Validation

Our API uses strict parameter validation following industry best practices:
  • Supported parameters are processed and applied as filters
  • Unknown parameters are rejected with a 400 Bad Request error
  • 🛡️ Invalid values are rejected with clear error messages
This approach prevents “silent failures” where invalid parameters might be ignored, ensuring your queries work exactly as intended.

Basic Usage Examples

# Get first 100 solar projects in California
GET /api/v1/interconnection/caiso?state=CA&technology=Solar&limit=100

# Get operating wind projects over 100 MW across multiple states  
GET /api/v1/interconnection/pjm?state=PA,OH,NJ&technology=Wind&status=Operating&min_capacity=100

# Get planned projects in Texas with pagination
GET /api/v1/interconnection/ercot?status=Planned&limit=500&offset=1000

Response Structure

All endpoints return consistent response structures:
{
  "success": true,
  "iso": "CISO",
  "summary": {
    "limit": 1000,
    "offset": 0,
    "total_results": 3027,
    "has_more": true,
    "current_page": 1,
    "total_pages": 4
  },
  "filters": {
    "state": "CA",
    "technology": "Solar",
    "status": null,
    "min_capacity": null,
    "max_capacity": null
  },
  "data": [
    {
      "iso": "CISO",
      "queue_id": "1379_photovoltaic",
      "project_name": "Alameda Solar Farm",
      "capacity_mw": 150.5,
      "technology": "Solar",
      "status": "Planned",
      "state": "CA",
      "county": "Alameda",
      // ... additional fields
    }
  ]
}

Common Use Cases

Market Analysis

  • Track renewable development by region and technology
  • Analyze capacity trends and market penetration
  • Identify growth opportunities by state

Site Selection

  • Find development patterns in target regions
  • Compare technology deployment across states
  • Analyze competitive landscape

Portfolio Management

  • Monitor project status changes across multiple ISOs
  • Track development pipelines
  • Benchmark against market trends

Data Integration

  • Export data for analysis in BI tools
  • Build automated reporting pipelines
  • Create custom dashboards and visualizations

Error Handling

The API returns clear, actionable error messages:
{
  "error": "INVALID_PARAMETER",
  "message": "Unknown parameters: developer, county. Supported parameters: limit, offset, state, technology, status, min_capacity, max_capacity"
}
Common error scenarios:
  • 400 Bad Request - Invalid or unknown parameters
  • 401 Unauthorized - Missing or invalid API key
  • 429 Too Many Requests - Rate limit exceeded
  • 500 Internal Server Error - Server-side issues

Next Steps

  1. Get Started: Request your API key from our team
  2. Explore Endpoints: Review individual ISO endpoint documentation
  3. Test Integration: Use our interactive API documentation
  4. Build Applications: Integrate with your data pipeline or application
For detailed parameter documentation and examples, see the individual endpoint pages for each ISO.