> ## 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.

# CAISO Interconnection Queue

> Access real-time CAISO interconnection queue data for all power projects

## Overview

The CAISO interconnection queue endpoint provides access to real-time data from the California Independent System Operator (CAISO) interconnection queue, which serves most of California and parts of Nevada.

<Note>
  **CAISO Coverage**: Contains **3,027 projects** across California (89%), Nevada (5%), Arizona (4%), and Mexico (1%). Top technologies: Solar (1,200+ projects), Battery Storage (1,100+ projects), Wind (300+ projects).
</Note>

<Warning>
  **Hybrid Projects**: CAISO represents hybrid projects (e.g., solar + storage) as single rows in their Excel source files with multiple technology columns. Our API splits these into separate records for each technology component. See our [comprehensive guide on hybrid project handling](/api-reference/interconnection-codes#how-we-handle-hybrid-projects) for details.
</Warning>

## Endpoint

<CodeGroup>
  ```bash cURL theme={null}
  curl -H "x-api-key: your_api_key_here" \
    "https://api.cleanview.co/api/v1/interconnection/caiso?limit=50"
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch('https://api.cleanview.co/api/v1/interconnection/caiso?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/caiso?limit=50',
      headers=headers
  )
  data = response.json()
  ```
</CodeGroup>

## 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 (CA, NV, AZ) - 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

<Tip>
  Use standardized technology names for consistent filtering. See our [Interconnection Reference](/api-reference/interconnection-codes#technology-classifications) for all available options.
</Tip>

<Warning>
  **CAISO Technology Field Mapping**: CAISO represents technology information differently from other ISOs. When filtering by `technology=Solar`, the API searches both the `technology` field (which contains CAISO's original terms like "Photovoltaic") and the `fuel` field (which contains "Solar"). This ensures consistent cross-ISO filtering while preserving CAISO's original data structure.

  **Example**: A CAISO solar project returns:

  * `technology`: "Photovoltaic" (CAISO's original term)
  * `fuel`: "Solar" (standardized term)
  * Both fields are searched when using `technology=Solar` filter
</Warning>

| Technology    | Count  | Description                                                                |
| ------------- | ------ | -------------------------------------------------------------------------- |
| `Solar`       | 1,200+ | Solar photovoltaic projects (searches both `technology` and `fuel` fields) |
| `Battery`     | 1,100+ | Battery energy storage systems                                             |
| `Wind`        | 300+   | Wind turbine projects                                                      |
| `Natural Gas` | 180+   | Natural gas generation                                                     |
| `Other`       | 200+   | Other technologies                                                         |

### Status Options

| Status      | Count  | Description                   |
| ----------- | ------ | ----------------------------- |
| `Planned`   | 1,800+ | Active projects in queue      |
| `Operating` | 800+   | Commercial operation achieved |
| `Cancelled` | 400+   | Withdrawn or terminated       |

## Example Requests

<AccordionGroup>
  <Accordion title="Get Active Solar Projects in California">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?technology=Solar&status=Planned&state=CA&limit=50"
    ```

    Returns active solar projects in the CAISO queue. Uses `technology=Solar` for standardized filtering.
  </Accordion>

  <Accordion title="Get Large Battery Storage Projects (>100 MW)">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?technology=Battery&min_capacity=100&limit=50"
    ```

    Finds large-scale battery storage projects. Uses `technology=Battery` for energy storage systems.
  </Accordion>

  <Accordion title="Get Wind Projects">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?technology=Wind&limit=50"
    ```

    Filters for wind projects in the CAISO queue.
  </Accordion>

  <Accordion title="Get Projects by Multiple Technologies">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?technology=Solar,Wind,Battery&limit=50"
    ```

    Uses comma-separated values for multiple technology filtering.
  </Accordion>

  <Accordion title="Get NextEra Energy Projects">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?developer=NextEra&limit=50"
    ```

    Filters for projects developed by NextEra Energy. Uses partial matching, so "NextEra" matches "NextEra Energy Resources".
  </Accordion>

  <Accordion title="Get Projects Without Developer Information">
    ```bash theme={null}
    curl -H "x-api-key: your_api_key_here" \
      "https://api.cleanview.co/api/v1/interconnection/caiso?developer=null&limit=50"
    ```

    Returns only projects that don't have developer information mapped in Cleanview's database.
  </Accordion>
</AccordionGroup>

## Response Schema

<ResponseExample>
  ```json Example Response theme={null}
  {
    "iso": "CAISO",
    "summary": {
      "limit": 50,
      "offset": 0,
      "total_results": 3027,
      "has_more": true,
      "current_page": 1,
      "total_pages": 61
    },
    "filters": {
      "state": null,
      "technology": null,
      "status": null,
      "min_capacity": null,
      "max_capacity": null,
      "developer": null
    },
    "data": [
      {
        "iso": "CISO",
        "queue_id": "1000_combined_cycle",
        "project_name": "Heca Scs",
        "capacity_mw": 300,
        "technology": "Combined Cycle",
        "fuel": "Other",
        "status": "Cancelled",
        "detailed_status": "Withdrawn",
        "operating_date": "2019-01-01T16:00:00.000Z",
        "request_date": "2013-05-01T07:00:00.000Z",
        "county": "Kern",
        "state": "CA",
        "queue_position": "1000",
        "interconnecting_entity": null,
        "developer": null,
        "feasibility_study_status": null,
        "system_impact_study_status": "Complete",
        "facilities_study_status": null,
        "optional_study_status": null,
        "interconnection_agreement_status": null,
        "deliverability_status": "Full Capacity",
        "voltage_kv": null,
        "station_transmission_line": "Midway-Wheeler Ridge 230 kV Line",
        "study_area": null,
        "balancing_authority_code": "CISO",
        "technology_normalized": "Natural Gas",
        "site_id": "1000",
        "site_generator_id": "1000_combined_cycle",
        "project_number": null,
        "interconnection_request_date": "2013-05-01T07:00:00.000Z",
        "queue_date": "2013-04-30T14:00:00.000Z",
        "application_status": "Withdrawn",
        "study_process": "C06",
        "technology_type": "Combined Cycle",
        "fuel_type": "Other",
        "net_mws_to_grid": 300,
        "tpd_allocation_percentage": null,
        "off_peak_deliverability": null,
        "utility": "PGAE",
        "pto_study_region": null,
        "proposed_online_date": "2019-01-01T16:00:00.000Z",
        "current_online_date": "2019-01-01T16:00:00.000Z",
        "suspension_status": null,
        "original_type_number": 1,
        "project_uuid": null,
        "withdrawn_date": "2014-04-24T14:00:00.000Z",
        "withdrawal_reason": null
      }
    ]
  }
  ```
</ResponseExample>

<Note>
  **Complete Upstream Data**: Each project includes all 47 database columns from CAISO's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and CAISO-specific raw fields like `site_generator_id`, `deliverability_status`, and study statuses.
</Note>

## Response Fields

### Core Identification Fields

| Field                      | Type   | Description                                                   |
| -------------------------- | ------ | ------------------------------------------------------------- |
| `iso`                      | string | Always "CISO" for CAISO data                                  |
| `queue_id`                 | string | Unique CAISO queue identifier (e.g., "1000\_combined\_cycle") |
| `project_name`             | string | Official project name in CAISO queue                          |
| `site_id`                  | string | CAISO site identifier                                         |
| `site_generator_id`        | string | Combined site and generator identifier                        |
| `project_number`           | string | CAISO project tracking number (often null)                    |
| `project_uuid`             | string | Unique project identifier (UUID format, often null)           |
| `balancing_authority_code` | string | Always "CISO"                                                 |

### Capacity & Technology

| Field                   | Type   | Description                                                |
| ----------------------- | ------ | ---------------------------------------------------------- |
| `capacity_mw`           | number | Project nameplate capacity in MW                           |
| `net_mws_to_grid`       | number | Net MW capacity to be delivered to grid                    |
| `technology`            | string | CAISO's technology classification (e.g., "Combined Cycle") |
| `technology_type`       | string | Detailed technology type from CAISO source                 |
| `technology_normalized` | string | Standardized technology for cross-ISO filtering            |
| `fuel`                  | string | Primary fuel source                                        |
| `fuel_type`             | string | Detailed fuel type from CAISO source                       |

### Project Status & Dates

| Field                          | Type   | Description                                         |
| ------------------------------ | ------ | --------------------------------------------------- |
| `status`                       | string | Standardized status (Planned, Operating, Cancelled) |
| `detailed_status`              | string | Original CAISO status (e.g., "Withdrawn", "Active") |
| `application_status`           | string | Current application status in CAISO process         |
| `queue_position`               | string | Queue position number                               |
| `queue_date`                   | date   | Date project entered CAISO queue                    |
| `request_date`                 | date   | Interconnection request submission date             |
| `interconnection_request_date` | date   | Original interconnection request date               |
| `operating_date`               | date   | Expected/actual commercial operation date           |
| `proposed_online_date`         | date   | Originally proposed online date                     |
| `current_online_date`          | date   | Current expected online date                        |
| `withdrawn_date`               | date   | Date project was withdrawn (if applicable)          |
| `withdrawal_reason`            | string | Reason for withdrawal (if provided by CAISO)        |
| `suspension_status`            | string | Current suspension status (if applicable)           |

### Location

| Field    | Type   | Description                              |
| -------- | ------ | ---------------------------------------- |
| `state`  | string | State code (CA=89%, NV=5%, AZ=4%, MX=1%) |
| `county` | string | County name where project is located     |

### Study Process & Interconnection

| Field                              | Type   | Description                                   |
| ---------------------------------- | ------ | --------------------------------------------- |
| `study_process`                    | string | CAISO study process designation (e.g., "C06") |
| `feasibility_study_status`         | string | Feasibility study completion status           |
| `system_impact_study_status`       | string | System Impact Study status                    |
| `facilities_study_status`          | string | Facilities Study completion status            |
| `optional_study_status`            | string | Optional study status                         |
| `interconnection_agreement_status` | string | Interconnection Agreement execution status    |

### Grid Connection & Deliverability

| Field                       | Type   | Description                                         |
| --------------------------- | ------ | --------------------------------------------------- |
| `deliverability_status`     | string | Full Capacity, Energy Only, or Partial Capacity     |
| `tpd_allocation_percentage` | number | Transmission Plan Deliverability (TPD) allocation % |
| `off_peak_deliverability`   | string | Off-peak deliverability designation                 |
| `voltage_kv`                | number | Interconnection voltage level in kV                 |
| `station_transmission_line` | string | Point of interconnection description                |
| `study_area`                | string | CAISO study area designation (typically null)       |
| `utility`                   | string | Participating Transmission Owner (PTO) utility      |
| `pto_study_region`          | string | PTO study region (if applicable)                    |

### Developer Information

| Field                    | Type   | Description                                                 |
| ------------------------ | ------ | ----------------------------------------------------------- |
| `developer`              | string | Developer name from Cleanview enrichment (limited coverage) |
| `interconnecting_entity` | string | Always null - not provided by CAISO                         |

### Technical Details

| Field                  | Type    | Description                               |
| ---------------------- | ------- | ----------------------------------------- |
| `original_type_number` | integer | Original CAISO type classification number |

<Note>
  **Data Updates**: CAISO queue data is updated weekly. The API reflects the most recent queue data available from CAISO's public reports.
</Note>

<Warning>
  **Field Availability**: Due to the nature of the CAISO interconnection queue, the `interconnecting_entity` field is always null. CAISO does not provide interconnecting entity information in their queue data. Use `station_transmission_line` for interconnection point details.
</Warning>

<Info>
  **Missing Coordinates**: CAISO data does not include latitude/longitude coordinates. For location analysis, use the `county` and `state` fields or the `station_transmission_line` for grid connection points.
</Info>


## OpenAPI

````yaml GET /interconnection/caiso
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/caiso:
    get:
      tags:
        - Interconnection
      summary: Get CAISO interconnection queue data
      description: >-
        Retrieve real-time interconnection queue data from the California
        Independent System Operator (CAISO)
      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 (CA, NV, AZ)
          example: CA
        - 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 CAISO interconnection queue data
          content:
            application/json:
              schema:
                type: object
                properties:
                  iso:
                    type: string
                    example: CAISO
                  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: CISO
                        queue_id:
                          type: string
                          example: 1379_photovoltaic
                        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: CA
                        county:
                          type: string
                          example: Fresno
        '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

````