# EIA codes reference Source: https://docs.cleanview.co/api-reference/eia-codes Standardized EIA 860M codes for balancing authorities, energy sources, and prime movers. # EIA codes documentation ## EIA 860M reference codes This API uses standardized codes from the U.S. Energy Information Administration (EIA) to represent balancing authorities, energy sources, and prime movers. These codes are derived from official EIA forms and documentation. Use these codes to filter or interpret results in API responses. > [!NOTE] > > **Official EIA documentation:** > > * [EIA Form 860 Data](https://www.eia.gov/electricity/data/eia860/) (Annual Electric Power Industry Report) > * [EIA Form 860M Data](https://www.eia.gov/electricity/data/eia860m/) (Monthly Generator Inventory - source of our API data) *** ### Example queries * To find all **solar projects in CAISO**, filter using: `energy_source_code = "SUN"` and `balancing_authority_code = "CISO"` * To find **planned combined cycle plants in ERCOT**, filter using: `prime_mover_code = "CC"` and `balancing_authority_code = "ERCO"` *** ## Balancing authority codes > [!NOTE] > > Balancing authority codes in EIA Form 860M data are standardized by NERC (North American Electric Reliability Corporation). These codes may not match current corporate names due to mergers, acquisitions, or other business changes. The codes used in our API data come from the EIA Form 860M monthly generator inventory reporting. ### Most common balancing authorities Below are the most common balancing authorities that represent the 7 major RTOs and ISOs in the US: | Code | Name | | - | - | | CISO | California Independent System Operator | | ERCO | Electric Reliability Council of Texas, Inc. | | MISO | Midcontinent Independent System Operator, Inc. | | ISNE | ISO New England Inc. | | NYIS | New York Independent System Operator | | PJM | PJM Interconnection, LLC | | SWPP | Southwest Power Pool | ### All balancing authority codes | Code | Balancing authority name | | - | :- | | AEC | PowerSouth Energy Cooperative | | AECI | Associated Electric Cooperative, Inc. | | AMPL | Anchorage Municipal Light & Power | | AVA | Avista Corporation | | AVRN | Avangrid Renewables LLC | | AZPS | Arizona Public Service Company | | BANC | Balancing Authority of Northern California | | BPAT | Bonneville Power Administration | | CEA | Chugach Electric Assn Inc | | CHPD | Public Utility District No. 1 of Chelan County | | CISO | California Independent System Operator | | CPLE | Duke Energy Progress East | | CPLW | Duke Energy Progress West | | CSTO | Constellation Energy Control and Dispatch, LLC | | DEAA | Arlington Valley, LLC - AVBA | | DOPD | PUD No. 1 of Douglas County | | DUK | Duke Energy Carolinas | | EEI | Electric Energy, Inc. | | EPE | El Paso Electric Company | | ERCO | Electric Reliability Council of Texas, Inc. | | FMPP | Florida Municipal Power Pool | | FPC | Duke Energy Florida Inc | | FPL | Florida Power & Light Company | | GCPD | Public Utility District No. 2 of Grant County, Washington | | GLHB | Gridforce Energy Management, LLC | | GRID | GridLiance | | GRIF | Griffith Energy, LLC | | GRIS | Gridforce South | | GVL | Gainesville Regional Utilities | | GWA | NaturEner Power Watch, LLC (GWA) | | HECO | Hawaiian Electric Co Inc | | HGMA | New Harquahala Generating Company, LLC - HGBA | | HST | City of Homestead | | IID | Imperial Irrigation District | | IPCO | Idaho Power Company | | ISNE | ISO New England Inc. | | JEA | JEA | | LDWP | Los Angeles Department of Water and Power | | LGEE | LG\&E and KU Services Company as agent for Louisville Gas and Electric Company and Kentucky Utilities | | MISO | Midcontinent Independent Transmission System Operator, Inc. | | NA | No balancing authority | | NA - AK | No balancing authority - AK | | NA - HI | No balancing authority - HI | | NA - PR | No balancing authority - PR | | NBSO | New Brunswick System Operator | | NEVP | Nevada Power Company | | NSB | New Smyrna Beach, Utilities Commission of | | NWMT | NorthWestern Energy (NWMT) | | NYIS | New York Independent System Operator | | OVEC | Ohio Valley Electric Corporation | | PACE | PacifiCorp - East | | PACW | PacifiCorp - West | | PGE | Portland General Electric Company | | PJM | PJM Interconnection, LLC | | PNM | Public Service Company of New Mexico | | PSCO | Public Service Company of Colorado | | PSEI | Puget Sound Energy | | SC | South Carolina Public Service Authority | | SCEG | South Carolina Electric & Gas Company | | SCL | Seattle City Light | | SEC | Seminole Electric Cooperative | | SEPA | Southeastern Power Administration | | SOCO | Southern Company Services, Inc. - Trans | | SPA | Southwestern Power Administration | | SRP | Salt River Project | | SWPP | Southwest Power Pool | | TAL | City of Tallahassee | | TEC | Tampa Electric Company | | TEPC | Tucson Electric Power Company | | TIDC | Turlock Irrigation District | | TPWR | City of Tacoma, Department of Public Utilities, Light Division | | TVA | Tennessee Valley Authority | | WACM | Western Area Power Administration - Rocky Mountain Region | | WALC | Western Area Power Administration - Desert Southwest Region | | WAUW | Western Area Power Administration UGP West | | WWA | NaturEner Wind Watch, LLC | | YAD | Alcoa Power Generating, Inc. - Yadkin Division | ## Energy source codes > [!NOTE] > > Energy source codes are defined by the EIA for Form 860M monthly generator inventory reporting. The EIA Form 860M includes a codes spreadsheet that defines energy sources and prime movers for generators with 1 MW or greater combined nameplate capacity. These are the codes used in our API data. These codes represent the primary fuel or energy type used at a generating facility. The most commonly used codes are: | Code | Description | | - | - | | SUN | Solar | | WND | Wind | | MWH | Electricity used for energy storage (megawatt hour) | | NUC | Nuclear | | WAT | Water (Hydro) | | GEO | Geothermal | | NG | Natural gas | | ANT,BIT,LIG,SUB,WC,RC | All coal-related codes | ### All energy sources codes Here is EIA’s full list of energy source codes and groupings: | **Group** | **Code** | **Description** | | - | - | - | | **Fossil fuels** | | | | Coal | ANT | Anthracite Coal | | Coal | BIT | Bituminous Coal | | Coal | LIG | Lignite Coal | | Coal | RC | Refined Coal (A coal product that is created when impurities and/or moisture are removed to improve heat content and reduce emissions. Includes any coal which meets the IRS definition of refined coal. Does not include coal processed by coal preparation plants.) | | Coal | SGC | Coal-Derived Synthesis Gas | | Coal | SUB | Subbituminous Coal | | Coal | WC | Waste/Other Coal (including anthracite culm, bituminous gob, fine coal, lignite waste, waste coal) | | Petroleum Products | DFO | Distillate Fuel Oil (including diesel, No. 1, No. 2, and No. 4 fuel oils) | | Petroleum Products | JF | Jet Fuel | | Petroleum Products | KER | Kerosene | | Petroleum Products | PC | Petroleum Coke | | Petroleum Products | PG | Propane, gaseous | | Petroleum Products | RFO | Residual Fuel Oil (including No. 5 and No. 6 fuel oils, and bunker C fuel oil) | | Petroleum Products | SGP | Petroleum Coke Derived Synthesis Gas | | Petroleum Products | WO | Waste/Other Oil (including crude oil, liquid butane, liquid propane, naphtha, oil waste, re-refined motor oil, sludge oil, tar oil, or other petroleum-based liquid wastes) | | Natural Gas and Other Fossil Gas | BFG | Blast Furnace Gas | | Natural Gas and Other Fossil Gas | NG | Natural Gas | | Natural Gas and Other Fossil Gas | OG | Other Gas | | **Renewable fuels** | | | | Solid Renewable Fuels | AB | Agricultural By-products | | Solid Renewable Fuels | MSW | Municipal Solid Waste | | Solid Renewable Fuels | OBS | Other Biomass Solids | | Liquid Renewable (Biomass) Fuels | WDS | Wood/Wood Waste Solids (including paper pellets, railroad ties, utility poles, wood chips, bark, and wood waste solids) | | Liquid Renewable (Biomass) Fuels | BLQ | Black Liquor | | Liquid Renewable (Biomass) Fuels | OBL | Other Biomass Liquids | | Liquid Renewable (Biomass) Fuels | SLW | Sludge Waste | | Liquid Renewable (Biomass) Fuels | WDL | Wood Waste Liquids excluding Black Liquor (includes red liquor, sludge wood, spent sulfite liquor, and other wood-based liquids) | | Gaseous Renewable (Biomass) Fuels | LFG | Landfill Gas | | Gaseous Renewable (Biomass) Fuels | OBG | Other Biomass Gas (includes digester gas, methane, and other biomass gasses) | | **Renewables** | | | | All Other Renewable Fuels | GEO | Geothermal | | All Other Renewable Fuels | SUN | Solar | | All Other Renewable Fuels | WAT | Water at a Conventional Hydroelectric Turbine, and water used in Wave Buoy Hydrokinetic Technology, Current Hydrokinetic Technology, and Tidal Hydrokinetic Technology | | All Other Renewable Fuels | WND | Wind | | **All other fuels** | | | | All Other Fuels | H2 | Hydrogen | | All Other Fuels | MWH | Electricity used for energy storage | | All Other Fuels | NUC | Nuclear Uranium, Plutonium, Thorium | | All Other Fuels | PUR | Purchased Steam | | All Other Fuels | TDF | Tire-derived Fuels | | All Other Fuels | WAT | Pumping Energy for Reversible (Pumped Storage) Hydroelectric Turbine | | All Other Fuels | WH | Waste heat not directly attributed to a fuel source | | All Other Fuels | OTH | Other | ## Prime mover codes > [!NOTE] > > Prime mover codes identify the equipment that converts energy into electricity at power plants. These codes are standardized by the EIA for Form 860M monthly generator inventory reporting. Prime movers represent the mechanical equipment that drives the electrical generator (e.g., steam turbine, wind turbine, photovoltaic cells). Here is the full list of EIA prime mover codes: | Prime mover codes | Description | | - | - | | BA | Energy Storage, Battery | | BT | Turbines Used in a Binary Cycle (including those used for geothermal applications) | | CA | Combined-Cycle – Steam Part | | CE | Energy Storage, Compressed Air | | CP | Energy Storage, Concentrated Solar Power | | CS | Combined-Cycle Single-Shaft (Combustion Turbine and Steam Turbine share a single generator) | | CT | Combined-Cycle Combustion Turbine Part | | ES | Energy Storage, Other (Specify on Schedule 9, Comments) | | FC | Fuel Cell | | FW | Energy Storage, Flywheel | | GT | Combustion (Gas) Turbine (including Jet Engine design) | | HA | Hydrokinetic, Axial Flow Turbine | | HB | Hydrokinetic, Wave Buoy | | HK | Hydrokinetic, Other | | HY | Hydraulic Turbine (including turbines associated with delivery of water by pipeline) | | IC | Internal Combustion (diesel, piston, reciprocating) Engine | | PS | Energy Storage, Reversible Hydraulic Turbine (Pumped Storage) | | OT | Other | | ST | Steam Turbine (including Nuclear, Geothermal, and Solar Steam; excludes Combined Cycle) | | PV | Photovoltaic | | WT | Wind Turbine, Onshore | | WS | Wind Turbine, Offshore | ## Status detailed codes > [!NOTE] > > Status codes track the operational and development status of generators throughout their lifecycle. These codes are defined in EIA Form 860M monthly generator inventory reporting. The status field helps distinguish between operating, planned, under construction, and retired generators. The `status_detailed` field provides granular information about a generator's lifecycle stage and operational status. These codes help distinguish between various states of development, operation, and retirement. ### Lifecycle stages and status details | Lifecycle stage | Status code | Status details | Description | | - | - | - | - | | **Operating / active** | OP | Operating | Currently in commercial operation. | | | SB | Standby/Backup: available for service but not normally used | Generator is available but not normally used. | | | OA | Out of service but expected to return to service in next calendar year | Temporarily offline but expected to return soon. | | | OS | Out of service and NOT expected to return to service in next calendar year | Offline with no expected return. | | | OT | Other | Does not fit standard categories. | | **Construction / development** | U | Under construction, less than or equal to 50 percent complete | Construction started, ≤ 50% complete. | | | V | Under construction, more than 50 percent complete | Construction underway, > 50% complete. | | | TS | Construction complete, but not yet in commercial operation | Construction done, not yet operating. | | **Planned / proposed** | P | Planned for installation, but regulatory approvals not initiated | Early planning stage, no approvals yet. | | | L | Regulatory approvals pending. Not under construction | Approvals in progress; construction not started. | | | T | Regulatory approvals received. Not under construction | Approvals complete, awaiting construction. | | **Inactive / canceled** | CN | Canceled or Postponed | Project was canceled or indefinitely delayed. | | | RE | Retired | Generator permanently removed from service. | # CAISO interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/caiso GET /interconnection/caiso 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). > [!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. ## Endpoint ```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() ``` ## 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. > [!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 | 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 > **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. > **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. > **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. > **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. > **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". > **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. ## Response schema ```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 } ] } ``` > [!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. ## 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. > [!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. > [!NOTE] > > **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. # Data center campuses Source: https://docs.cleanview.co/api-reference/endpoint/data-center-campuses GET /data-center-campuses Retrieve data center campuses with status, capacity and building counts rolled up from their buildings ## Overview A campus is a site with one or more data center buildings or phases. This endpoint returns one record per campus, with its status, capacity, building count, tenants, location and grid connection rolled up from its buildings. The buildings themselves are on the [Data Centers](/api-reference/endpoint/data-centers) endpoint, where each carries its campus's `campus_id`. This is a "download link" style endpoint that returns all records in a single response. There is no pagination - every campus record is returned at once. ### Which campuses are included Campuses that have passed Cleanview's review and have at least one building that isn't canceled. Canceled buildings are left out of every figure: status, capacity, counts, years, size and tenants. A campus whose buildings are all canceled isn't returned. ### Status values A campus's status is rolled up from its buildings, ignoring canceled ones. A campus with operating buildings and a phase under construction is `Under Construction`. | Status | Description | | - | - | | `Under Construction` | At least one building is under construction | | `Operating` | No building is under construction and at least one is operating | | `Planned` | Every building is planned | ### Capacity Capacity is facility power: the total power the campus draws from the grid, not its IT load. `total_capacity_mw` sums the campus's buildings, and `operating_capacity_mw`, `under_construction_capacity_mw` and `planned_capacity_mw` split that sum by building status, so the three add up to the total. Sums use the buildings that have a capacity. When `buildings_with_capacity` is less than `building_count`, some buildings have no known capacity and the totals are a lower bound. A capacity field is `null` when no building in it has a capacity, including when the campus has no buildings with that status. IT capacity is on each building in [Data Centers](/api-reference/endpoint/data-centers) (`it_capacity_mw`). To total IT capacity by campus, join the buildings on `campus_id` and leave out canceled ones. ### Grid connection and on-site gas * `has_onsite_gas` is `true` when an on-site, behind-the-meter gas plant serves the campus. * The utility and balancing authority fields are set only when known with high confidence; `null` means unknown. A campus's buildings in Data Centers carry the same values. ## Example requests > **Get all data center campuses** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/data-center-campuses" > ``` > > Returns all campus records in a single response. ## Response schema ```json Example Response theme={null} { "success": true, "metadata": { "total_count": 1445, "generated_at": "2026-10-15T16:00:00.000Z" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "id": 358, "campus_name": "Google Cedar Rapids", "developer": "Google", "status": "Under Construction", "operating_capacity_mw": 97.4, "under_construction_capacity_mw": 200.7, "planned_capacity_mw": 309.9, "total_capacity_mw": 608, "building_count": 6, "buildings_with_capacity": 6, "first_operating_year": 2026, "last_operating_year": 2030, "building_square_footage": 846651, "tenant_name": null, "end_user_name": null, "has_onsite_gas": false, "county": "Linn", "state": "IA", "latitude": 41.9182, "longitude": -91.7226, "utility": "Alliant Energy", "utility_parent": "Alliant Energy", "utility_eia_id": 9417, "balancing_authority": "MISO", "balancing_authority_code": "MISO", "iso_rto": "MISO" }, { "id": 160, "campus_name": "Stargate Abilene", "developer": "Crusoe", "status": "Under Construction", "operating_capacity_mw": 300, "under_construction_capacity_mw": 900, "planned_capacity_mw": null, "total_capacity_mw": 1200, "building_count": 8, "buildings_with_capacity": 8, "first_operating_year": 2025, "last_operating_year": 2026, "building_square_footage": 3920000, "tenant_name": "Oracle", "end_user_name": "OpenAI", "has_onsite_gas": true, "county": "Taylor", "state": "TX", "latitude": 32.50018025, "longitude": -99.783973125, "utility": "AEP Texas", "utility_parent": "American Electric Power", "utility_eia_id": 20404, "balancing_authority": "ERCOT", "balancing_authority_code": "ERCO", "iso_rto": "ERCOT" } ] } ``` ## Response fields ### Metadata section | Field | Type | Description | | - | - | - | | `success` | boolean | Indicates if the request was successful | | `total_count` | number | Total number of campus records returned | | `generated_at` | string | ISO 8601 timestamp when response was generated | ### Campus fields | Field | Type | Description | | - | - | - | | `id` | number | Unique identifier for the campus; buildings in Data Centers carry it as `campus_id` | | `campus_name` | string | Name of the campus | | `developer` | string | Developer or operator of the campus | | `status` | string | Campus status rolled up from its buildings (Planned, Under Construction, Operating) | | `operating_capacity_mw` | number | Facility power of the operating buildings in megawatts (MW) | | `under_construction_capacity_mw` | number | Facility power of the buildings under construction (MW) | | `planned_capacity_mw` | number | Facility power of the planned buildings (MW) | | `total_capacity_mw` | number | Facility power of all the buildings (MW); a lower bound when `buildings_with_capacity` is less than `building_count` | | `building_count` | number | Number of buildings or phases on the campus, not counting canceled ones | | `buildings_with_capacity` | number | Number of those buildings with a known facility power | | `first_operating_year` | number | Earliest year a building began or will begin operations | | `last_operating_year` | number | Latest year a building began or will begin operations | | `building_square_footage` | number | Total building area in square feet, summed over the buildings that have it | | `tenant_name` | string | Tenant(s) across the campus's buildings, comma-separated when there are multiple | | `end_user_name` | string | End user(s) across the campus's buildings, comma-separated when there are multiple | | `has_onsite_gas` | boolean | `true` when an on-site, behind-the-meter gas plant serves the campus | | `county` | string | County where the campus is located | | `state` | string | Two-letter state code where the campus is located | | `latitude` | number | Latitude coordinate of the campus | | `longitude` | number | Longitude coordinate of the campus | | `utility` | string | Retail utility whose service territory the campus is in | | `utility_parent` | string | The utility's parent company; `null` for co-ops, municipal and public utilities | | `utility_eia_id` | number | The utility's EIA utility number (EIA-861) | | `balancing_authority` | string | Balancing authority the campus is in | | `balancing_authority_code` | string | The balancing authority's EIA-930 code (e.g. `ERCO`, `PJM`, `SOCO`) | | `iso_rto` | string | ISO/RTO the campus is in: PJM, ERCOT, MISO, SPP, CAISO, NYISO, ISO-NE, or `Non-ISO` | > [!NOTE] > > **Null values**: Fields are `null` when the information isn't available. The capacity fields are `null` when no building in them has a capacity, `first_operating_year` and `last_operating_year` when no building has an operating year, and `latitude` and `longitude` for the few campuses without coordinates. `tenant_name` and `end_user_name` are only populated where a tenant or end user has been publicly identified. The utility and balancing authority fields are `null` unless known with high confidence. ## Data updates Campus figures are computed from the building records in [Data Centers](/api-reference/endpoint/data-centers) on every request, so the two endpoints always agree. # Data centers Source: https://docs.cleanview.co/api-reference/endpoint/data-centers GET /data-centers Retrieve comprehensive data center project information including capacity, location, and development status ## Overview The Data Centers endpoint provides access to a curated database of data center projects across the United States. This dataset includes information about planned, under-construction, operating, and canceled data center facilities, with details on power capacity, tenants, land usage, capital expenditure, and geographic location. This is a "download link" style endpoint that returns all records in a single response. There is no pagination - every data center record is returned at once. Each record is one building or phase. Campus totals (status, capacity and building count per campus) are on the [Data Center Campuses](/api-reference/endpoint/data-center-campuses) endpoint; join on `campus_id`. ### Status values | Status | Description | | - | - | | `Planned` | Project is planned but not yet under construction | | `Under Construction` | Project is actively under construction | | `Operating` | Data center is currently operational | | `Canceled` | Project has been canceled or postponed | ### Geographic coverage Data centers are tracked across multiple states with the highest concentrations in: * **Virginia (VA)** - Northern Virginia data center corridor * **Texas (TX)** - Major metro areas including Dallas-Fort Worth, Austin, San Antonio * **Georgia (GA)** - Atlanta metro area * **Arizona (AZ)** - Phoenix metro area * **California (CA)** - Bay Area and Los Angeles ## Example requests > **Get all data centers** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/data-centers" > ``` > > Returns all data center records in a single response. ## Response schema ```json Example Response theme={null} { "success": true, "metadata": { "total_count": 3423, "generated_at": "2026-09-15T16:00:00.000Z" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "id": 802, "project_name": "Stargate Milam - Building 1", "campus_id": 455, "campus_name": "Stargate Milam", "developer": "SB Energy", "status": "Under Construction", "operating_year": 2027, "capacity_mw": 383.9, "it_capacity_mw": 308, "land_acres": null, "building_square_footage": 548950, "cap_ex": 3000000000, "county": "Milam", "state": "TX", "latitude": 30.996249, "longitude": -97.010689, "tenant_name": "OpenAI", "end_user_name": "OpenAI", "utility": null, "utility_parent": null, "utility_eia_id": null, "balancing_authority": "ERCOT", "balancing_authority_code": "ERCO", "iso_rto": "ERCOT", "source_1": "https://storage.googleapis.com/data-center-source-files/developers/sb-energy/2026-08-31_sec-filing_sb-energy-form-s-1-cosmos-50-mw-it-travis-tx-softb.htm", "source_2": "https://storage.googleapis.com/data-center-source-files/campuses/455__stargate-milam/2026-04-15_building-permit_tdlr-freebird-phase1-dc01.pdf", "source_3": "https://storage.googleapis.com/data-center-source-files/campuses/455__stargate-milam/2026-04-22_news_dcd-freebird-548950-sqft-phase1.pdf" }, { "id": 753, "project_name": "River Bend - Building 1", "campus_id": 142, "campus_name": "River Bend Campus", "developer": "Hut 8", "status": "Under Construction", "operating_year": 2027, "capacity_mw": 165, "it_capacity_mw": 122.5, "land_acres": 300, "building_square_footage": 900000, "cap_ex": 2500000000, "county": "West Feliciana Parish", "state": "LA", "latitude": 30.715939, "longitude": -91.316943, "tenant_name": "Fluidstack", "end_user_name": "Anthropic", "utility": "Entergy Louisiana", "utility_parent": "Entergy", "utility_eia_id": 11241, "balancing_authority": "MISO", "balancing_authority_code": "MISO", "iso_rto": "MISO", "source_1": "https://www.prnewswire.com/news-releases/hut-8-signs-15-year-245-mw-ai-data-center-lease-at-river-bend-campus-with-total-contract-value-of-7-0-billion-302644600.html", "source_2": "https://www.sec.gov/Archives/edgar/data/1964789/000110465925122052/hut-20251217x8k.htm", "source_3": "https://www.hut8.com/data-centers/river-bend" } ] } ``` ## Response fields ### Metadata section | Field | Type | Description | | - | - | - | | `success` | boolean | Indicates if the request was successful | | `total_count` | number | Total number of data center records returned | | `generated_at` | string | ISO 8601 timestamp when response was generated | ### Data center fields | Field | Type | Description | | - | - | - | | `id` | number | Unique identifier for the data center record | | `project_name` | string | Name of the data center project | | `campus_id` | number | ID of the building's campus (the `id` in [Data Center Campuses](/api-reference/endpoint/data-center-campuses)); `null` when the building isn't assigned to a campus | | `campus_name` | string | Name of the building's campus; `null` when `campus_id` is `null` | | `developer` | string | Developer or operator of the data center | | `status` | string | Project status (Planned, Under Construction, Operating, Canceled) | | `operating_year` | number | Year the facility began or will begin operations (if known) | | `capacity_mw` | number | Total facility power capacity in megawatts (MW) | | `it_capacity_mw` | number | IT (critical load) capacity in megawatts (MW) | | `land_acres` | number | Land area in acres | | `building_square_footage` | number | Building area in square feet | | `cap_ex` | number | Capital expenditure (investment amount in USD) | | `county` | string | County where the data center is located | | `state` | string | Two-letter state code where data center is located | | `latitude` | number | Latitude coordinate of the facility | | `longitude` | number | Longitude coordinate of the facility | | `tenant_name` | string | Tenant(s) of the data center, comma-separated when there are multiple | | `end_user_name` | string | End user(s) of the capacity, comma-separated when there are multiple | | `utility` | string | Retail utility whose service territory the site is in | | `utility_parent` | string | The utility's parent company; `null` for co-ops, municipal and public utilities | | `utility_eia_id` | number | The utility's EIA utility number (EIA-861) | | `balancing_authority` | string | Balancing authority the site is in | | `balancing_authority_code` | string | The balancing authority's EIA-930 code (e.g. `ERCO`, `PJM`, `SOCO`) | | `iso_rto` | string | ISO/RTO the site is in: PJM, ERCOT, MISO, SPP, CAISO, NYISO, ISO-NE, or `Non-ISO` | | `source_1` | string | Primary source URL for the data center information | | `source_2` | string | Secondary source URL (if available) | | `source_3` | string | Tertiary source URL (if available) | > [!NOTE] > > **Null values**: Many fields may contain `null` values when specific information is not available. This is particularly common for `operating_year`, `capacity_mw`, `latitude`, and `longitude` fields on newly announced projects. `tenant_name` and `end_user_name` are only populated where a tenant or end user has been publicly identified. The utility and balancing authority fields are `null` unless known with high confidence; buildings on the same campus share them. A canceled building can have a `campus_id` that isn't in Data Center Campuses, which leaves out campuses whose buildings are all canceled. ## Data quality notes * Source URLs are provided for transparency and verification * Geographic coordinates (latitude/longitude) are included when available and accurate * Capacity and financial data (capacity\_mw, cap\_ex) may be estimates based on public announcements * Some projects may have multiple source URLs for cross-verification > [!WARNING] > > **Large response size**: This endpoint returns all approved records in a single response. The response size can be 500KB or more depending on the current dataset. Ensure your application can handle this payload size. ## Use cases This endpoint is ideal for: * **Market analysis**: Understanding data center development trends by region, developer, or capacity * **Location intelligence**: Mapping data center locations and analyzing geographic clustering * **Competitive research**: Tracking which developers are active in specific markets * **Energy planning**: Analyzing power capacity requirements and grid impact * **Real estate analysis**: Understanding land and building size requirements for data center projects ## Data updates The data center database is continuously updated as new projects are announced or existing projects reach new milestones. # EIA 860M data Source: https://docs.cleanview.co/api-reference/endpoint/eia-860m GET /eia-860m Retrieve EIA 860M power plant data with detailed capacity, operational status, and location information ## Overview The EIA 860M endpoint provides access to the U.S. Energy Information Administration's monthly electric generator inventory data. This dataset includes comprehensive information about power plants and generators across the United States, including renewable energy projects, traditional generation facilities, and energy storage systems. ### Energy source codes The most common energy source codes in our dataset: | Code | Description | Count | | - | - | - | | `NG` | Natural Gas | 9,742 | | `SUN` | Solar | 9,000 | | `DFO` | Distillate Fuel Oil (Diesel) | 5,517 | | `WAT` | Hydro | 4,598 | | `LFG` | Landfill Gas | 1,983 | | `WND` | Wind | 1,955 | | `MWH` | Battery Storage | 1,435 | | `BIT` | Bituminous Coal | 828 | | `SUB` | Subbituminous Coal | 463 | | `GEO` | Geothermal | 341 | ### Balancing authority codes The most common balancing authorities in our dataset: | Code | Description | Count | | - | - | - | | `MISO` | Midcontinent Independent System Operator | 6,404 | | `PJM` | PJM Interconnection | 5,370 | | `CISO` | California Independent System Operator | 3,738 | | `ERCO` | Electric Reliability Council of Texas | 2,850 | | `ISNE` | ISO New England | 2,694 | | `NYIS` | New York Independent System Operator | 2,303 | | `SWPP` | Southwest Power Pool | 2,126 | > [!TIP] > > Need the complete list of EIA codes? See our [EIA Codes Reference](/api-reference/eia-codes) for all balancing authorities, energy sources, and prime mover codes. ### Status options | Status | Description | | - | - | | `operating` | Currently operating facilities | | `retired` | Retired from service | | `planned` | Planned but not yet operating | | `canceled` | Cancelled projects | | `all` | All statuses | ## Example requests > **Get solar projects in California** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?state=CA&energy_source=SUN&limit=50" > ``` > > Uses `energy_source=SUN` for solar. See [all energy source codes](/api-reference/eia-codes#energy-source-codes). > **Get wind projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?energy_source=WND&limit=50" > ``` > > Uses `energy_source=WND` for wind. See [all energy source codes](/api-reference/eia-codes#energy-source-codes). > **Get battery storage projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?energy_source=MWH&status=operating&limit=50" > ``` > > Uses `energy_source=MWH` for battery storage. See [all energy source codes](/api-reference/eia-codes#energy-source-codes). > **Get projects by multiple balancing authorities** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?balancing_authority=CISO,ERCO&limit=50" > ``` > > Uses `balancing_authority=CISO,ERCO` for California ISO and ERCOT. See [all balancing authority codes](/api-reference/eia-codes#balancing-authority-codes). > **Get projects by developer** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?developer=NextEra&limit=50" > ``` > > Filters projects that have developer mapping data. Supports partial matching. Projects without developer data are excluded from filtered results. ## Response schema ```json Example Response theme={null} { "success": true, "summary": { "limit": 50, "offset": 0, "total_results": 3044, "has_more": true, "current_page": 1, "total_pages": 61 }, "filters": { "state": "CA", "energy_source": null, "balancing_authority": null, "status": "all", "start_year": null, "end_year": null, "developer": null }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "plant_id": "66659", "plant_name": "Acid BESS", "plant_state": "CA", "county": "Fresno", "latitude": 36.6905, "longitude": -119.7404, "entity_id": "65678", "entity_name": "Malaga BESS LLC", "generator_id": "MAL", "unit_code": null, "nameplate_capacity_mw": 97, "nameplate_energy_capacity_mwh": 97, "energy_source_code": "MWH", "technology": "Batteries", "prime_mover_code": "BA", "status": "Operating", "status_detailed": "(OP) Operating", "operating_year": 2025, "operating_month": "3", "retirement_year": null, "retirement_month": null, "operating_date": "2025-03-01", "retirement_date": null, "balancing_authority_code": "CISO", "sector": "IPP Non-CHP", "plant_generator_key": "66659_MAL", "developer": "Malaga BESS LLC" }, { "plant_id": "66167", "plant_name": "AM Wind Repower LLC", "plant_state": "CA", "county": "Riverside", "latitude": 33.943741, "longitude": -116.6615, "entity_id": "63235", "entity_name": "Brookfield Renewable Trading and Marketing LP", "generator_id": "63235", "unit_code": null, "nameplate_capacity_mw": 27, "nameplate_energy_capacity_mwh": null, "energy_source_code": "WND", "technology": "Onshore Wind Turbine", "prime_mover_code": "WT", "status": "Operating", "status_detailed": "(OP) Operating", "operating_year": 2025, "operating_month": "3", "retirement_year": null, "retirement_month": null, "operating_date": "2025-03-01", "retirement_date": null, "balancing_authority_code": "CISO", "sector": "IPP Non-CHP", "plant_generator_key": "66167_63235", "developer": "Brookfield Renewable" } ] } ``` ## Response fields | Field | Type | Description | | - | - | - | | `plant_id` | string | Unique EIA plant identifier | | `plant_name` | string | Name of the power plant facility | | `plant_state` | string | Two-letter state code where plant is located | | `county` | string | County name where plant is located | | `latitude` | number | Plant latitude coordinate | | `longitude` | number | Plant longitude coordinate | | `entity_id` | string | EIA entity (utility/company) identifier | | `entity_name` | string | Name of utility or company operating the plant | | `generator_id` | string | Generator unit identifier within the plant | | `unit_code` | string | Additional unit identifier (if applicable) | | `nameplate_capacity_mw` | number | Nameplate capacity in megawatts (MW) | | `nameplate_energy_capacity_mwh` | number | Energy storage capacity in megawatt-hours (MWh) for storage units | | `energy_source_code` | string | Primary energy source code (SUN, WND, NG, etc.) | | `technology` | string | Technology description | | `prime_mover_code` | string | Prime mover technology code | | `status` | string | Operational status | | `status_detailed` | string | Detailed operational status with EIA codes | | `operating_year` | number | Year facility began/will begin operation | | `operating_month` | string | Month facility began/will begin operation | | `retirement_year` | number | Year facility retired/will retire (if applicable) | | `retirement_month` | number | Month facility retired/will retire (if applicable) | | `operating_date` | string | Operating date in YYYY-MM-DD format | | `retirement_date` | string | Retirement date in YYYY-MM-DD format (if applicable) | | `balancing_authority_code` | string | Balancing authority acronym | | `sector` | string | Sector classification | | `plant_generator_key` | string | Composite key combining plant\_id and generator\_id | | `developer` | string | Developer company name(s) associated with the project | > [!NOTE] > > **Data updates**: EIA 860M data is updated monthly by the U.S. Energy Information Administration. Our API reflects the most recent available data. # ERCOT interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/ercot GET /interconnection/ercot 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. > [!NOTE] > > **ERCOT coverage**: Contains **2,200+ projects** primarily in Texas (99%). Top technologies: Solar (800+ projects), Wind (400+ projects), Battery Storage (350+ projects). > [!NOTE] > > **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 > [!TIP] > > 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 > **Get active solar projects in Texas** > > ```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. > **Get large wind projects (>200 MW)** > > ```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. > **Get battery storage 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. > **Get projects by multiple technologies** > > ```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 } ] } ``` > [!NOTE] > > **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 | > [!NOTE] > > **Data updates**: ERCOT queue data is updated weekly. The API reflects the most recent Generation Interconnection Request (GIR) data available from ERCOT. > [!NOTE] > > **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. > [!WARNING] > > **Missing coordinates**: ERCOT data does not include latitude/longitude coordinates. Use the `county`, `poi_location`, and `cdr_reporting_zone` fields for geographic analysis. # Gas plant units Source: https://docs.cleanview.co/api-reference/endpoint/gas-plant-units GET /gas-plant-units Retrieve the turbines, engines and fuel cells at behind-the-meter gas plants: manufacturer, model, count, capacity, status and year > [!NOTE] > > The BTM gas plant endpoints require the `gas-plants` scope on your API key. A key without it gets `403 INSUFFICIENT_SCOPE`. [Contact us](https://cleanview.co/contact) to add it. ## Overview This endpoint returns the equipment at the plants in [Gas Plants](/api-reference/endpoint/gas-plants). Each record is one unit: one equipment model at one stage of a plant's build, with its manufacturer (OEM), model, number of machines, capacity, status and year. A plant that uses two models has two units. So does a plant that installs the same model in two stages with different timelines. The plant's developer and location are repeated on every record, so the table stands on its own. Pivot it by OEM, model, status, year or state. This is a "download link" style endpoint that returns all records in a single response. There is no pagination. ### Equipment * `oem` and `model` are spelled the way the manufacturer sells them, like Siemens Energy SGT-800 or INNIO Jenbacher J624. * `model` is `null` when a document names the manufacturer but not the model. Cleanview doesn't guess a model from the plant's size. * `model_family` groups products built on the same machine: GE's TM2500 and LM2500XPRESS are both `LM2500`. Use it to count every machine of a kind, however it was packaged. * `version` is the model's rated version, when a document identifies it. ### Configuration `equipment_type` is the kind of machine: `Gas turbine`, `Steam turbine`, `Reciprocating engine` or `Fuel cell`. `configuration` is how it generates: | Configuration | Description | | - | - | | `simple_cycle` | Gas turbines on their own: frame, aeroderivative (adapted from jet engines) and mobile turbines | | `combined_cycle` | Gas turbines built to run with a heat recovery steam generator, which turns their exhaust into steam. Includes turbines that run on their own first and join a combined-cycle block later | | `steam_turbine` | The steam turbines in a combined-cycle plant, which run on that steam | | `reciprocating_engine` | Large natural gas engines, like those from Caterpillar, INNIO Jenbacher and Wärtsilä | | `fuel_cell` | Equipment that makes electricity from gas without burning it, like Bloom Energy's servers | A combined-cycle plant has `combined_cycle` records for its gas turbines and `steam_turbine` records for its steam turbines. Add both for the plant's full combined-cycle capacity. ### Capacity `nameplate_capacity_mw` is the nameplate capacity of all the unit's machines together: the number of machines times the manufacturer's rating for each one. Manufacturers rate gas turbines at 59°F at sea level and engines at 77°F, so one machine has one rating wherever it's installed. `capacity_basis` says where the number comes from: | Basis | Description | | - | - | | `rating` | `unit_count` × `iso_rating_mw`: the manufacturer's data sheet rating for the exact version a document names | | `stated` | A rating a filing or announcement gives, for equipment Cleanview has no data sheet for | | `estimate` | Cleanview's estimate, when the version isn't confirmed and the versions differ by more than about 10%. It uses the developer's own figure first, then the version the evidence points to, then the middle of the permitted range | ### Status `status` uses the same five values as [Gas Plants](/api-reference/endpoint/gas-plants#status-values). Canceled units are included with status `Canceled`, and Gas Plants leaves them out of its capacity figures. ## Example requests > **Get all gas plant units** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/gas-plant-units" > ``` > > Returns all unit records in a single response. ## Response schema ```json Example Response theme={null} { "success": true, "metadata": { "total_count": 209, "generated_at": "2026-10-15T16:00:00.000Z" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "id": 165, "plant_id": 88, "plant_name": "Apollo Power Generation Facility", "developer": "Williams", "campus_id": 243, "county": "Wood", "state": "OH", "latitude": 41.463279, "longitude": -83.626865, "oem": "Siemens Energy", "model": "SGT-800", "model_family": "SGT-800", "version": "62 MW rating", "equipment_type": "Gas turbine", "configuration": "simple_cycle", "unit_count": 2, "iso_rating_mw": 62.5, "nameplate_capacity_mw": 125, "capacity_basis": "rating", "status": "Under Construction", "operating_year": 2027, "source_1": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-06-02_air-permit_ohio-epa-final-pti-p0139272-will-power-oh-apollo.pdf", "source_2": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-01-06_utility-filing_opsb-25-973-response-to-staff-data-request-1-unit-mw-table.pdf", "source_3": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-01-27_utility-filing_opsb-25-973-staff-report-of-investigation.pdf" }, { "id": 170, "plant_id": 88, "plant_name": "Apollo Power Generation Facility", "developer": "Williams", "campus_id": 243, "county": "Wood", "state": "OH", "latitude": 41.463279, "longitude": -83.626865, "oem": "Caterpillar", "model": "G3520", "model_family": "G3520", "version": null, "equipment_type": "Reciprocating engine", "configuration": "reciprocating_engine", "unit_count": 6, "iso_rating_mw": null, "nameplate_capacity_mw": 15, "capacity_basis": "stated", "status": "Under Construction", "operating_year": 2027, "source_1": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-06-02_air-permit_ohio-epa-final-pti-p0139272-will-power-oh-apollo.pdf", "source_2": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-01-06_utility-filing_opsb-25-973-response-to-staff-data-request-1-unit-mw-table.pdf", "source_3": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-01-27_utility-filing_opsb-25-973-staff-report-of-investigation.pdf" } ] } ``` ## Response fields ### Metadata section | Field | Type | Description | | - | - | - | | `success` | boolean | Indicates if the request was successful | | `total_count` | number | Total number of unit records returned | | `generated_at` | string | ISO 8601 timestamp when response was generated | ### Unit fields | Field | Type | Description | | - | - | - | | `id` | number | Unique identifier for the unit | | `plant_id` | number | The plant, as `id` in Gas Plants | | `plant_name` | string | Name of the plant | | `developer` | string | Company that builds and owns the plant | | `campus_id` | number | The data center campus the plant powers, as `id` in Data Center Campuses | | `county` | string | County where the plant's generation equipment is | | `state` | string | Two-letter state code | | `latitude` | number | Latitude of the plant's generation equipment, not the data center campus | | `longitude` | number | Longitude of the plant's generation equipment, not the data center campus | | `oem` | string | Equipment manufacturer, like Siemens Energy or Caterpillar | | `model` | string | Model as the manufacturer sells it, like SGT-800. `null` when a document names only the manufacturer | | `model_family` | string | The machine the model is built on: GE's TM2500 and LM2500XPRESS are both LM2500 | | `version` | string | The model's rated version, when a document identifies it | | `equipment_type` | string | Kind of machine: `Gas turbine`, `Steam turbine`, `Reciprocating engine` or `Fuel cell` | | `configuration` | string | How it generates: `simple_cycle`, `combined_cycle`, `steam_turbine`, `reciprocating_engine` or `fuel_cell` (see Configuration) | | `unit_count` | number | Number of machines in the unit | | `iso_rating_mw` | number | One machine's rating from the manufacturer's data sheet, at standard conditions (MW). `null` when the version isn't known | | `nameplate_capacity_mw` | number | Nameplate capacity of all the unit's machines together (MW) | | `capacity_basis` | string | Where the capacity comes from: `rating`, `stated` or `estimate` (see Capacity) | | `status` | string | `Announced`, `Permitted`, `Under Construction`, `Operating` or `Canceled` (see Status) | | `operating_year` | number | Year the unit began generating, or Cleanview's estimate of when it will | | `source_1` | string | Cleanview's archived copy of a document behind the record | | `source_2` | string | Cleanview's archived copy of a document behind the record | | `source_3` | string | Cleanview's archived copy of a document behind the record | > [!NOTE] > > **Null values**: `null` means Cleanview doesn't know the value yet, not zero. `oem`, `model`, `model_family` and `version` are `null` until they're public; `iso_rating_mw` when the version isn't known; `equipment_type` and `configuration` for the few units whose configuration isn't known; `unit_count`, `nameplate_capacity_mw` and `capacity_basis` when the number or size of the machines isn't public yet. # Gas plants Source: https://docs.cleanview.co/api-reference/endpoint/gas-plants GET /gas-plants Retrieve behind-the-meter gas plants built to power data centers, with status and capacity rolled up from their units > [!NOTE] > > The BTM gas plant endpoints require the `gas-plants` scope on your API key. A key without it gets `403 INSUFFICIENT_SCOPE`. [Contact us](https://cleanview.co/contact) to add it. ## Overview Data centers that can't wait for the grid are building their own gas plants. This endpoint returns one record per behind-the-meter gas plant built to power a data center. A plant is behind the meter when its power goes straight to the data center instead of through a utility meter. Each record has the plant's developer, status, capacity, the data center campus it powers, its location, its air permit, and the documents Cleanview archived for it. This is a "download link" style endpoint that returns all records in a single response. There is no pagination. ### Plants and units A plant is one generation site. Its equipment is broken into units on [Gas Plant Units](/api-reference/endpoint/gas-plant-units), linked by `plant_id`. A unit is one equipment model at one stage of the build, with its own count, capacity, status and year. A plant with two engine models, each installed in two stages, has four units. The plant's status and capacity on this endpoint are rolled up from its units. The campus it powers is on [Data Center Campuses](/api-reference/endpoint/data-center-campuses), linked by `campus_id`. ### Status values Each unit has its own status. A plant shows the status of its most advanced unit that isn't canceled, so a plant with an operating first stage and a second stage under construction is `Operating`. A plant is `Canceled` only when every unit is. | Status | Description | | - | - | | `Announced` | Announced or applied for. No air permit or siting approval has been issued | | `Permitted` | An air permit or state siting approval has been issued, but construction hasn't started | | `Under Construction` | Work on the generation equipment is underway: foundations, equipment on pads, stacks. Clearing and grading don't count | | `Operating` | Generating power for its data center, including temporary bridge power | | `Canceled` | The project won't be built | ### Capacity `nameplate_capacity_mw` is the number of machines times the manufacturer's rating for each machine, summed over the units that aren't canceled. Manufacturers rate gas turbines at 59°F at sea level and engines at 77°F. So one machine has one rating wherever it's installed, and nameplate adds up across plants and manufacturers. A plant's real output on a hot day or at altitude is lower. `operating_capacity_mw`, `under_construction_capacity_mw`, `permitted_capacity_mw` and `announced_capacity_mw` split the nameplate capacity by unit status, so they add up to it. When `capacity_is_partial` is `true`, some units have no known capacity yet, and the capacity fields are a minimum. `firm_output_mw` is the power the plant is contracted, permitted or stated to deliver to its data center. It's usually 55% to 85% of nameplate, because of heat, altitude, the plant's own load and spare machines. It's only given when a document states it, and never estimated. `firm_output_basis` names the kind of document: | Basis | Description | | - | - | | `contracted` | A contract figure stated in a filing | | `permit_limit` | A permit or siting condition on the power the plant can deliver | | `net_capacity` | A grid-connected plant's net capacity, from the EIA or a commission order | | `developer_stated` | The developer's own statement of the power the plant delivers | ### Air permits and sources `air_permit_url` is Cleanview's copy of the plant's issued air permit, or its latest amendment, once the plant is `Permitted`, `Under Construction` or `Operating`. `sources` lists every document Cleanview archived for the plant, newest first, including permit applications and drafts. Each `url` is Cleanview's archived copy, so it keeps working if the original is taken down. `original_url` is where the document was first published. ## Example requests > **Get all gas plants** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/gas-plants" > ``` > > Returns all gas plant records in a single response. ## Response schema ```json Example Response theme={null} { "success": true, "metadata": { "total_count": 110, "generated_at": "2026-10-15T16:00:00.000Z" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "id": 88, "plant_name": "Apollo Power Generation Facility", "developer": "Williams", "status": "Under Construction", "nameplate_capacity_mw": 493.1, "operating_capacity_mw": null, "under_construction_capacity_mw": 493.1, "permitted_capacity_mw": null, "announced_capacity_mw": null, "capacity_is_partial": false, "generating_units": 27, "firm_output_mw": 350, "firm_output_basis": "permit_limit", "first_operating_year": 2027, "announcement_date": "2025-11-05", "equipment_types": "Gas turbine, Reciprocating engine", "oems": "Caterpillar, Siemens Energy, Solar Turbines", "campus_id": 243, "campus_name": "Meta Bowling Green", "county": "Wood", "state": "OH", "latitude": 41.463279, "longitude": -83.626865, "air_permit_url": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-06-02_air-permit_ohio-epa-final-pti-p0139272-will-power-oh-apollo.pdf", "sources": [ { "title": "Final Air Pollution Permit-to-Install P0139272, Will-Power OH LLC - Apollo", "document_type": "air-permit", "document_date": "2026-06-02", "url": "https://storage.googleapis.com/data-center-source-files/gas-plants/88__meta-bowling-green-power-plant/2026-06-02_air-permit_ohio-epa-final-pti-p0139272-will-power-oh-apollo.pdf", "original_url": "https://edocpub.epa.ohio.gov/publicportal/ViewDocument.aspx?docid=4139063" } ] } ] } ``` ## Response fields ### Metadata section | Field | Type | Description | | - | - | - | | `success` | boolean | Indicates if the request was successful | | `total_count` | number | Total number of plant records returned | | `generated_at` | string | ISO 8601 timestamp when response was generated | ### Gas plant fields | Field | Type | Description | | - | - | - | | `id` | number | Unique identifier for the plant. Units carry it as `plant_id` | | `plant_name` | string | The plant's name in its permit, siting case or announcement; otherwise the data center's name followed by "power plant" | | `developer` | string | Company that builds and owns the plant. Often not the data center developer: Williams builds Meta's plants in Ohio | | `status` | string | Status of the plant's most advanced unit that isn't canceled (see Status Values) | | `nameplate_capacity_mw` | number | Number of machines × the manufacturer's rating, summed over the units that aren't canceled (MW) | | `operating_capacity_mw` | number | Nameplate capacity of the operating units (MW) | | `under_construction_capacity_mw` | number | Nameplate capacity of the units under construction (MW) | | `permitted_capacity_mw` | number | Nameplate capacity of the permitted units (MW) | | `announced_capacity_mw` | number | Nameplate capacity of the announced units (MW) | | `capacity_is_partial` | boolean | `true` when some units have no known capacity yet, so the capacity fields are a minimum | | `generating_units` | number | Number of turbines, engines and fuel cell servers that aren't canceled. A minimum when a unit's count isn't public | | `firm_output_mw` | number | Power the plant is contracted, permitted or stated to deliver to its data center (MW). Only given when a document states it | | `firm_output_basis` | string | The kind of document behind `firm_output_mw`: `contracted`, `permit_limit`, `net_capacity` or `developer_stated` | | `first_operating_year` | number | Year the plant's first unit began generating, or Cleanview's estimate of when it will | | `announcement_date` | string | Date of the first public record of the plant (YYYY-MM-DD) | | `equipment_types` | string | Kinds of equipment at the plant, comma-separated: Gas turbine, Steam turbine, Reciprocating engine, Fuel cell | | `oems` | string | Equipment manufacturers at the plant, comma-separated | | `campus_id` | number | The data center campus the plant powers, as `id` in Data Center Campuses | | `campus_name` | string | Name of the data center campus the plant powers | | `county` | string | County where the plant's generation equipment is | | `state` | string | Two-letter state code | | `latitude` | number | Latitude of the plant's generation equipment, not the data center campus | | `longitude` | number | Longitude of the plant's generation equipment, not the data center campus | | `air_permit_url` | string | Cleanview's archived copy of the plant's issued air permit, or its latest amendment. `null` until the plant is permitted | | `sources` | array | Every document Cleanview archived for the plant, newest first: `title`, `document_type`, `document_date`, `url` (Cleanview's copy) and `original_url` | > [!NOTE] > > **Null values**: `null` means Cleanview doesn't know the value yet, not zero. A capacity field is `null` when no unit in it has a capacity, including when the plant has no units with that status. `campus_id` is `null` when the campus the plant powers isn't in Data Center Campuses; `campus_name` is still given. `equipment_types` and `oems` are `null` until the equipment is public. ## Data updates Plant figures are computed from the unit records in [Gas Plant Units](/api-reference/endpoint/gas-plant-units) on every request, so the two endpoints always agree. # ISO-NE interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/iso-ne GET /interconnection/iso-ne Access real-time ISO New England interconnection queue data for all power projects ## Overview The ISO-NE interconnection queue endpoint provides access to real-time data from ISO New England's interconnection queue, which serves all six New England states. ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/interconnection/iso-ne?limit=50" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/interconnection/iso-ne?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/iso-ne?limit=50', headers=headers ) data = response.json() ``` ## Coverage area **States served**: Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont. Note: Small number of projects in New Brunswick, Canada and New York also included. ## 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 (MA, CT, ME, etc.) - 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. | Technology | Description | | - | - | | `Solar` | Solar photovoltaic projects | | `Wind` | Wind turbine projects (onshore) | | `Battery` | Battery energy storage systems | | `Hybrid - Solar + Storage` | Combined solar and battery projects | | `Hybrid - Wind + Storage` | Combined wind and battery projects | | `Natural Gas` | Natural gas generation (combined cycle, gas turbines) | | `Nuclear` | Nuclear power plants | | `Hydro` | Hydroelectric generation | | `Other` | Other technologies | ### Status options | Status | Count | Description | | - | - | - | | `Planned` | 93 | Active projects currently in interconnection queue | | `Operating` | 351 | Projects that achieved commercial operation | | `Cancelled` | 1,308 | Projects withdrawn from queue | ### Top states by project count | State | Project count | Top technologies | | - | - | - | | Massachusetts | About 600 | Solar, hybrid storage | | Connecticut | About 400 | Solar, natural gas | | Maine | About 300 | Solar, wind | | New Hampshire | About 200 | Solar | | Rhode Island | About 150 | Solar | | Vermont | About 100 | Solar, wind, hydro | ## Example requests > **Get active solar projects in Maine** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/iso-ne?technology=Solar&status=Planned&state=ME&limit=50" > ``` > > Returns active solar projects in ISO-NE's queue. Uses `technology=Solar` for standardized filtering. > **Get hybrid solar + storage projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/iso-ne?technology=Hybrid - Solar + Storage&limit=50" > ``` > > Finds projects combining solar PV with battery storage, common in ISO-NE's interconnection queue. > **Get projects with CNR service type** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/iso-ne?status=Planned&limit=200" > ``` > > Filter for Capacity Network Resource (CNR) projects in the response. CNR is the most common service type for battery storage in New England. > **Get Brookfield projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/iso-ne?developer=Brookfield&limit=50" > ``` > > Filters for projects developed by Brookfield. Uses partial matching to find all Brookfield projects across New England. > **Get projects by multiple technologies** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/iso-ne?technology=Solar,Wind,Battery&limit=50" > ``` > > Uses comma-separated values for multiple technology filtering. ## Response schema ```json Example Response theme={null} { "success": true, "iso": "NEISO", "summary": { "limit": 50, "offset": 0, "total_results": 1752, "has_more": true, "current_page": 1, "total_pages": 36 }, "filters": { "state": null, "technology": null, "status": null, "min_capacity": null, "max_capacity": null, "developer": null }, "data": [ { "iso": "ISNE", "queue_id": "1021_emery_meadow_solar_req20200427_ME_york_poicmp_345_kv_section_182", "project_name": "Emery Meadow Solar", "capacity_mw": 16.425, "technology": "G", "fuel": "SUN", "status": "Planned", "detailed_status": null, "operating_date": "2026-09-30T07:00:00.000Z", "request_date": "2020-04-27T07:00:00.000Z", "county": "York", "state": "ME", "queue_position": "1021", "neiso_developer": "PD", "developer": "Glenvale Solar", "data_source": "active", "balancing_authority_code": "ISNE", "technology_normalized": "Solar", "project_id": "1021_emery_meadow_solar_req20200427_ME_york_poicmp_345_kv_section_182", "cluster": null, "last_updated": "2024-07-11T20:30:33.089Z", "project_type": "G", "requested_date": "2020-04-27T07:00:00.000Z", "unit_id": "PV", "fuel_type": "SUN", "summer_capacity_mw": 16.425, "winter_capacity_mw": 16.425, "operation_date": "2026-09-30T07:00:00.000Z", "synchronization_date": "2026-08-01T07:00:00.000Z", "withdrawal_date": null, "interconnection_location": "CMP 34.5 kV, Section 182", "service_type": "CNR", "sis_complete": true, "i39": true, "to_report": "ISO-NE", "zone": "ME", "fs": null, "sis": "Document Posted", "os": null, "fac": null, "ia": "Executed" }, { "iso": "ISNE", "queue_id": "1138_husky_solar_req20210603_CT_windham_poithe_poi_will_be_located_about_69_miles_from_the_16071505_line_row_exeter_tap_and_about_11_miles_from_the_exeter_sub_54n_along_the_115_kv_underground_line_to_the_exeter_sub_54n", "project_name": "Husky Solar", "capacity_mw": 50.159, "technology": "G", "fuel": "SUN", "status": "Planned", "detailed_status": null, "operating_date": "2029-05-10T07:00:00.000Z", "request_date": "2021-06-03T07:00:00.000Z", "county": "Windham", "state": "CT", "queue_position": "1138", "neiso_developer": "PD", "developer": "Brookfield", "data_source": "active", "balancing_authority_code": "ISNE", "technology_normalized": "Solar", "project_id": "1138_husky_solar_req20210603_CT_windham_poithe_poi_will_be_located_about_69_miles_from_the_16071505_line_row_exeter_tap_and_about_11_miles_from_the_exeter_sub_54n_along_the_115_kv_underground_line_to_the_exeter_sub_54n", "cluster": null, "last_updated": "2025-10-17T20:47:49.473Z", "project_type": "G", "requested_date": "2021-06-03T07:00:00.000Z", "unit_id": "PV", "fuel_type": "SUN", "summer_capacity_mw": 50.159, "winter_capacity_mw": 50.159, "operation_date": "2029-05-10T07:00:00.000Z", "synchronization_date": "2029-05-01T07:00:00.000Z", "withdrawal_date": null, "interconnection_location": "The POI will be located about 6.9 miles from the 1607/1505 line ROW (Exeter Tap) and about 1.1 miles from the Exeter Sub 54N along the 115 kV underground line to the Exeter Sub 54N.", "service_type": "NR", "sis_complete": true, "i39": true, "to_report": "ISO-NE", "zone": "CT", "fs": "Document Posted", "sis": "Document Posted", "os": "Not Required", "fac": "Not Required", "ia": "Executed" } ] } ``` > [!NOTE] > > **Complete upstream data**: Each project includes all 41 database columns from ISO-NE's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and ISO-NE-specific raw fields like `fs`, `sis`, `os`, `fac`, `ia` (five-phase study process), `i39` (small generator designation), and `service_type` (CNR, NR, etc.). ## Response fields ### Core identification fields | Field | Type | Description | | - | - | - | | `iso` | string | Always "ISNE" for ISO New England data | | `queue_id` | string | Unique project identifier combining queue position, technology, location | | `project_id` | string | Alias for queue\_id (standardized across all ISOs) | | `project_name` | string | Official project name in ISO-NE queue | | `queue_position` | string | Numeric queue position assigned when interconnection request deemed complete | | `balancing_authority_code` | string | Always "ISNE" | | `last_updated` | date | Timestamp of last data update in Cleanview database | ### Capacity & technology | Field | Type | Description | | - | - | - | | `capacity_mw` | number | Primary nameplate capacity rating in MW | | `summer_capacity_mw` | number | Summer-rated capacity (typically lower due to heat derating) | | `winter_capacity_mw` | number | Winter-rated capacity (typically higher in New England climate) | | `technology` | string | Raw project type code (G=Generation, TS=Transmission Service, ETU=Elective Transmission Upgrade) | | `technology_normalized` | string | Standardized technology category for cross-ISO filtering | | `fuel` | string | Raw fuel type code (SUN, WND, BAT, etc., space-separated for hybrids) | | `fuel_type` | string | Detailed fuel type with hybrid combinations | | `unit_id` | string | Unit type identifier (PV, WT, OT, CC, GT, ST, HD, HW, IC, FC, PS) | | `project_type` | string | Project classification: G (Generation), TS (Transmission Service), ETU (Elective Transmission Upgrade) | ### Project status & dates | Field | Type | Description | | - | - | - | | `status` | string | Standardized status (Planned, Operating, Cancelled, Inactive) | | `detailed_status` | string | Original ISO-NE detailed status (typically null, enriched in data\_source) | | `request_date` | date | Date interconnection request submitted to ISO-NE | | `requested_date` | date | Alias for request\_date | | `operating_date` | date | Projected commercial operation date | | `operation_date` | date | Alias for operating\_date | | `synchronization_date` | date | Date project synchronized to the grid | | `withdrawal_date` | date | Date project withdrew from queue (null if not withdrawn) | ### Location | Field | Type | Description | | - | - | - | | `state` | string | Two-letter state code (MA, CT, ME, NH, RI, VT, plus NB \[Canada], NY) | | `county` | string | County within state where project is located | | `zone` | string | ISO-NE load zone (13 zones: BOST, CT, ME, NH, RI, VT, SEMA, WMA, NOR, CMA, SME, SWCT, BHE) | | `interconnection_location` | string | Detailed point of interconnection description | ### Study process (five-phase sequence) | Field | Type | Description | | - | - | - | | `fs` | string | Feasibility Study status (Not Started, In Progress, Document Posted, Not Required) | | `sis` | string | System Impact Study status (adds ISA Not Executed option for projects without signed ISA) | | `os` | string | Optional Study status (Document Posted, Not Required - rarely needed) | | `fac` | string | Facilities Study status (engineering design and cost estimates) | | `ia` | string | Interconnection Agreement status (adds IA Filed Unexecuted, Executed options) | ### Grid connection & service | Field | Type | Description | | - | - | - | | `service_type` | string | Type of interconnection service (CNR, NR, CNI, NI, ES, MIS, NS) | | `sis_complete` | boolean | Indicates whether System Impact Study has been completed | | `i39` | boolean | Indicates if project follows I.3.9 small generator (≤20 MW) interconnection process | ### Developer information | Field | Type | Description | | - | - | - | | `neiso_developer` | string | Developer name from original ISO-NE queue data | | `developer` | string | Cleanview-enriched developer name with corporate hierarchy mapping | ### ISO-NE specific fields | Field | Type | Description | | - | - | - | | `data_source` | string | Source dataset lifecycle (active, withdrawn, commercial) | | `to_report` | string | Reporting entity/transmission owner (ISO-NE, BHE, CMP, MPS, NGRID, NSTAR, NU, TEUS, UI) | | `cluster` | string | Cluster study group assignment (typically null) | ## ISO-NE queue terminology Understanding ISO New England's specific interconnection processes and terminology is essential for working with their queue data. ### I.3.9 interconnection process Section I.3.9 of ISO-NE's Open Access Transmission Tariff (OATT) governs the interconnection process for small generators (≤20 MW capacity). This expedited process is designed for smaller distributed generation projects. Projects are assigned numeric queue positions (e.g., "1000", "1021") when their interconnection application is deemed complete by ISO-NE. ### Study process phases ISO-NE uses a comprehensive five-phase study sequence for interconnection projects. Each phase has specific deliverables and status values: | Phase | Field | Possible values | Description | | - | - | - | - | | **Feasibility study** | `fs` | Not Started, In Progress, Document Posted, Not Required | Initial assessment of interconnection feasibility and system impacts | | **System impact study** | `sis` | Not Started, In Progress, Document Posted, Not Required, ISA Not Executed | Detailed reliability analysis requiring Interconnection System Agreement (ISA) | | **Optional study** | `os` | Document Posted, Not Required | Additional studies requested by customer (rarely required) | | **Facilities study** | `fac` | Not Started, In Progress, Document Posted, Not Required | Engineering design and cost estimates for required interconnection facilities | | **Interconnection agreement** | `ia` | Not Started, In Progress, Document Posted, Not Required, IA Filed Unexecuted, Executed | Final agreement governing interconnection terms and conditions | **Study status details:** * **Not Started**: Study phase has not yet begun * **In Progress**: Study currently being conducted by ISO-NE or transmission owner * **Document Posted**: Study completed and results published * **Not Required**: Study phase not needed for this project type * **ISA Not Executed**: (SIS only) Study cannot proceed without signed Interconnection System Agreement * **IA Filed Unexecuted**: (IA only) Agreement filed with FERC but not yet executed by all parties * **Executed**: (IA only) Final agreement signed by all parties ### Service types ISO-NE offers seven types of interconnection service, determining how the project participates in New England's wholesale electricity markets: | Code | Full name | Description | Common use cases | | - | - | - | - | | **CNR** | Capacity Network Resource | Full network interconnection service with capacity supply rights | Battery storage projects (30+ active CNR projects) | | **NR** | Network Resource | Energy delivery service via transmission network | Solar projects (22+ active NR projects) | | **CNI** | Capacity Network Import | Network import service with capacity designation | Imports from neighboring regions with capacity rights | | **NI** | Network Import | Import interconnection from external areas | Energy imports from New York, Canada, or Maritime provinces | | **ES** | Energy Service | Energy-only interconnection without capacity rights | Projects selling energy only, not participating in capacity market | | **MIS** | Market Interconnection Service | Historical service type for capacity increases at existing facilities | Legacy designation for uprates and expansions | | **NS** | Network Service | Legacy network service designation | Older projects predating current service type structure | ### Load zones ISO-NE divides New England into 13 load zones for locational pricing and resource planning: | Zone code | Geographic area | Description | | - | - | - | | **BOST** | Boston | Metro Boston area, Massachusetts | | **CT** | Connecticut | Connecticut aggregate zone | | **ME** | Maine | Maine aggregate zone | | **NH** | New Hampshire | New Hampshire aggregate zone | | **RI** | Rhode Island | Rhode Island aggregate zone | | **VT** | Vermont | Vermont aggregate zone | | **SEMA** | Southeast Massachusetts | Cape Cod and southeastern Massachusetts | | **WMA** | Western/Central Massachusetts | Western and central Massachusetts regions | | **NOR** | Northeast Massachusetts | Northeast Massachusetts | | **CMA** | Central Massachusetts | Central Massachusetts | | **SME** | Southern Maine | Southern Maine region | | **SWCT** | Southwest Connecticut | Southwest Connecticut | | **BHE** | Bangor Hydro Electric | Northern Maine (Bangor Hydro service territory) | ### Project classifications ISO-NE categorizes projects into three main types: **Project types** (`project_type` field): * **G (Generation)**: New generation facilities - represents vast majority of queue * **TS (Transmission Service)**: Transmission-only interconnection requests * **ETU (Elective Transmission Upgrade)**: Merchant transmission upgrades proposed by developers **Unit types** (`unit_id` field - 11 codes): * **PV**: Photovoltaic (solar) * **WT**: Wind Turbines * **OT**: Other (typically used for batteries) * **CC**: Combined Cycle (natural gas) * **GT**: Gas Turbines * **ST**: Steam Turbines * **HD**: Hydraulic/Hydro * **HW**: Hydro Water Wheels * **IC**: Internal Combustion * **FC**: Fuel Cells * **PS**: Pumped Storage ### Seasonal capacity ratings New England experiences significant temperature variations affecting equipment performance. ISO-NE therefore tracks both summer and winter capacity ratings: * **Summer capacity** (`summer_capacity_mw`): Capacity rating during hot weather, typically lower due to heat derating of transformers and transmission equipment * **Winter capacity** (`winter_capacity_mw`): Capacity rating during cold weather, typically higher as equipment operates more efficiently at lower temperatures Winter capacity is particularly important in New England due to peak electricity demand occurring during cold weather events when natural gas is also needed for heating. ### Fuel type hybrid notation ISO-NE represents hybrid projects using space-separated fuel codes in the `fuel` and `fuel_type` fields: * **"SUN BAT"**: Solar + Battery hybrid * **"WND BAT"**: Wind + Battery hybrid * **"NG SUN BAT"**: Natural Gas + Solar + Battery multi-technology project This differs from other ISOs that may use different delimiters or create separate records for each technology component. ### Data source lifecycle The `data_source` field tracks projects through their lifecycle: * **active**: Projects currently in interconnection queue or under development (93 projects) * **withdrawn**: Projects that withdrew from the queue before achieving commercial operation (1,308 projects - 75% of total) * **commercial**: Projects that successfully achieved commercial operation (351 projects) The 75% withdrawal rate reflects the speculative nature of many interconnection requests and the challenges of project development in New England. ### Transmission owners The `to_report` field identifies the reporting entity or transmission owner responsible for the interconnection. Nine entities report to ISO-NE: **Transmission owners**: * **ISO-NE**: ISO New England itself (for system-level projects) * **BHE**: Bangor Hydro Electric (Northern Maine) * **CMP**: Central Maine Power * **MPS**: Massachusetts Power Supply (historical) * **NGRID**: National Grid (Massachusetts, Rhode Island) * **NSTAR**: Eversource (previously NSTAR, Eastern Massachusetts) * **NU**: Northeast Utilities/Eversource (Connecticut, New Hampshire) * **TEUS**: Transmission Enhancement Services * **UI**: United Illuminating (Connecticut) > [!NOTE] > > **Data updates**: ISO-NE queue data is updated based on ISO New England's interconnection queue reports published periodically. > [!WARNING] > > **Developer field limitations**: The `neiso_developer` field often contains "PD" (Protected Developer) for confidentiality. The enriched `developer` field provides better corporate entity mapping but may still have limited coverage for smaller developers. > [!NOTE] > > **Geographic edge cases**: While ISO-NE primarily serves the six New England states, a small number of projects are located in New Brunswick, Canada (state code "NB") and New York (state code "NY") that interconnect to the New England grid system. # MISO interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/miso GET /interconnection/miso Access real-time MISO interconnection queue data for all power projects ## Overview The MISO interconnection queue endpoint provides access to real-time data from Midcontinent Independent System Operator (MISO) interconnection queue. MISO serves 15 states and one Canadian province across the Midwest and South. > [!NOTE] > > **MISO coverage**: Contains **1,500+ projects** across the Midwest and South. Top technologies: Wind (500+ projects), Solar (400+ projects), Natural Gas (300+ projects), Battery Storage (200+ projects). ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/interconnection/miso?limit=50" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/interconnection/miso?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/miso?limit=50', headers=headers ) data = response.json() ``` ## Coverage area **States served**: Arkansas, Illinois, Indiana, Iowa, Kentucky, Louisiana, Michigan, Minnesota, Mississippi, Missouri, Montana, North Dakota, Texas, Wisconsin, and parts of South Dakota. Also serves Manitoba, Canada. ## 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 - 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 distribution | Technology | Count | Description | | - | - | - | | `Wind` | 500+ | Wind turbine projects (dominant in MISO) | | `Solar` | 400+ | Solar photovoltaic projects | | `Natural Gas` | 300+ | Natural gas generation | | `Battery` | 200+ | Battery energy storage systems | | `Other` | 100+ | Other technologies | ### Status options | Status | Description | | - | - | | `Planned` | Active projects in queue | | `Operating` | Commercial operation achieved | | `Cancelled` | Withdrawn or terminated | ## Example requests > **Get wind projects in Illinois** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/miso?technology=Wind&state=IL&limit=50" > ``` > **Get large solar projects (>100 MW)** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/miso?technology=Solar&min_capacity=100&limit=50" > ``` > **Get Apex Clean Energy projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/miso?developer=Apex&limit=50" > ``` > > Filters for projects developed by Apex Clean Energy. Uses partial matching, so "Apex" matches "Apex Clean Energy". ## Response schema ```json Example Response theme={null} { "success": true, "iso": "MISO", "summary": { "limit": 50, "offset": 0, "total_results": 3571, "has_more": true, "current_page": 1, "total_pages": 72 }, "filters": { "state": null, "technology": null, "status": null, "min_capacity": null, "max_capacity": null, "developer": null }, "data": [ { "iso": "MISO", "queue_id": "J1000", "project_name": "Project J1000", "capacity_mw": 50, "technology": "Photovoltaic", "fuel": "Solar", "status": "Operating", "detailed_status": "Done", "operating_date": "2021-10-01T04:00:00.000Z", "request_date": "2018-03-12T04:00:00.000Z", "county": "Grant County", "state": "WI", "queue_position": null, "interconnecting_entity": null, "developer": "Alliant Energy", "study_cycle": "DPP-2018-APR", "study_group": "East (ATC)", "service_type": "NRIS", "balancing_authority_code": "MISO", "technology_normalized": "Solar", "project_id": "J1000", "request_status": "Done", "queue_date": "2018-03-12T04:00:00.000Z", "withdrawn_date": null, "done_date": "2021-04-02T04:00:00.000Z", "in_service_date": "2021-10-01T04:00:00.000Z", "transmission_owner": "American Transmission Co. LLC", "study_phase": "GIA", "poi_name": "Nelson Dewey - Lancaster 138kV Line", "summer_mw": 50, "winter_mw": 50, "fuel_type": "Solar", "facility_type": "Photovoltaic", "post_gia_status": "In Service", "negotiated_in_service_date": "2023-03-27T04:00:00.000Z", "dp1_eris_mw": 50, "dp1_nris_mw": 50, "dp2_eris_mw": 50, "dp2_nris_mw": 50, "winter_capacity_mw": 50, "summer_capacity_mw": 50 }, { "iso": "MISO", "queue_id": "J1846", "project_name": "Project J1846", "capacity_mw": 200, "technology": "Solar/Battery", "fuel": "Hybrid", "status": "Planned", "detailed_status": "Active", "operating_date": "2024-09-01T04:00:00.000Z", "request_date": "2021-07-22T04:00:00.000Z", "county": "Renville", "state": "MN", "queue_position": null, "interconnecting_entity": null, "developer": "Ranger Power", "study_cycle": "DPP-2021", "study_group": "West", "service_type": "NRIS", "balancing_authority_code": "MISO", "technology_normalized": "Hybrid - Solar + Storage", "project_id": "J1846", "request_status": "Active", "queue_date": "2021-07-22T04:00:00.000Z", "withdrawn_date": null, "done_date": null, "in_service_date": "2024-09-01T04:00:00.000Z", "transmission_owner": "GREAT RIVER ENERGY", "study_phase": "Phase 2", "poi_name": "PANTHER", "summer_mw": 200, "winter_mw": 200, "fuel_type": "Hybrid", "facility_type": "Solar/Battery", "post_gia_status": "Not Started", "negotiated_in_service_date": null, "dp1_eris_mw": 200, "dp1_nris_mw": 200, "dp2_eris_mw": 200, "dp2_nris_mw": 200, "winter_capacity_mw": 200, "summer_capacity_mw": 200 } ] } ``` > [!NOTE] > > **Complete upstream data**: Each project includes all 41 database columns from MISO's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and MISO-specific raw fields like `study_phase`, `post_gia_status`, and Decision Point capacity breakdowns. ## Response fields ### Core identification fields | Field | Type | Description | | - | - | - | | `iso` | string | Always "MISO" for MISO data | | `queue_id` | string | Unique MISO queue identifier (e.g., "J1000") | | `project_id` | string | MISO project identifier, same as queue\_id | | `project_name` | string | Official project name in MISO queue | | `balancing_authority_code` | string | Always "MISO" | | `queue_position` | string | Queue position number (typically null for MISO) | ### Capacity & technology | Field | Type | Description | | - | - | - | | `capacity_mw` | number | Project nameplate capacity in MW | | `summer_capacity_mw` | number | Summer-rated capacity (MISO tracks seasonal variations) | | `winter_capacity_mw` | number | Winter-rated capacity (MISO tracks seasonal variations) | | `summer_mw` | number | Summer MW rating from MISO source | | `winter_mw` | number | Winter MW rating from MISO source | | `technology` | string | MISO's technology classification (e.g., "Photovoltaic") | | `technology_normalized` | string | Standardized technology for cross-ISO filtering | | `fuel` | string | Primary fuel source | | `fuel_type` | string | Detailed fuel type from MISO source | | `facility_type` | string | Facility/technology type from MISO source | ### Project status & dates | Field | Type | Description | | - | - | - | | `status` | string | Standardized status (Planned, Operating, Cancelled) | | `detailed_status` | string | Original MISO status (e.g., "Active", "Done", "Withdrawn") | | `request_status` | string | Current request status in MISO process | | `queue_date` | date | Date project entered MISO queue | | `request_date` | date | Interconnection request submission date | | `operating_date` | date | Expected/actual commercial operation date | | `in_service_date` | date | Proposed in-service date | | `negotiated_in_service_date` | date | Negotiated in-service date (if different from proposed) | | `done_date` | date | Date project completed MISO process | | `withdrawn_date` | date | Date project was withdrawn (if applicable) | ### Location | Field | Type | Description | | - | - | - | | `state` | string | Two-letter state code | | `county` | string | County name where project is located | ### Study process (DPP) | Field | Type | Description | | - | - | - | | `study_cycle` | string | Definitive Planning Phase cycle identifier (e.g., "DPP-2018-APR") | | `study_group` | string | Study group assignment (East, West, Central, South) | | `study_phase` | string | Current DPP phase (Phase 1, Phase 2, Phase 3, GIA) | ### Decision point capacity allocations | Field | Type | Description | | - | - | - | | `dp1_eris_mw` | number | Decision Point 1 ERIS capacity allocation in MW | | `dp1_nris_mw` | number | Decision Point 1 NRIS capacity allocation in MW | | `dp2_eris_mw` | number | Decision Point 2 ERIS capacity allocation in MW | | `dp2_nris_mw` | number | Decision Point 2 NRIS capacity allocation in MW | ### Grid connection & service | Field | Type | Description | | - | - | - | | `service_type` | string | ERIS or NRIS interconnection service designation | | `transmission_owner` | string | Transmission owner at point of interconnection | | `poi_name` | string | Point of interconnection name and voltage level | | `post_gia_status` | string | Generation Interconnection Agreement execution status | ### Developer information | Field | Type | Description | | - | - | - | | `developer` | string | Developer name from Cleanview enrichment (limited coverage) | | `interconnecting_entity` | string | Always null - not provided by MISO | ## MISO queue terminology Understanding MISO-specific terms is essential for interpreting interconnection queue data. ### Definitive Planning Phase (DPP) MISO's three-phase interconnection study process that replaced the old serial queue system in 2018. Projects progress sequentially through Phase 1 (feasibility assessment), Phase 2 (detailed system impact analysis), and Phase 3 (facilities study). Each phase has specific deliverables and timelines designed to accelerate project development. ### Decision points (DP1, DP2, DP3) Critical milestones where developers must demonstrate project viability and commit financial security deposits. At each Decision Point, developers must confirm capacity allocations (ERIS/NRIS) and post additional security. Failure to meet Decision Point requirements results in automatic queue withdrawal. ### Service types **ERIS (Energy Resource Interconnection Service)**: Energy-only delivery service without capacity delivery rights. ERIS projects can inject energy into the grid but don't receive capacity credit in MISO markets. **NRIS (Network Resource Interconnection Service)**: Full network service with capacity delivery rights. NRIS projects can both deliver energy and receive capacity credit, but require more extensive system upgrades. ### Study groups MISO processes projects in regional cohorts based on queue submission windows. Study groups are typically identified by geographic region (East, West, Central, South) and may include the transmission owner designation (e.g., "East (ATC)", "East (ITC)"). ### Study cycles Intake windows when MISO accepts new interconnection requests, typically identified by year and month (e.g., "DPP-2021", "DPP-2018-APR"). All projects in a study cycle progress through the DPP phases together. ### Generation Interconnection Agreement (GIA) Final contractual agreement between generator and MISO governing interconnection terms, construction responsibilities, and operational requirements. Projects reaching "GIA" study phase have completed all technical studies and are finalizing interconnection contracts. ### Seasonal capacity ratings MISO tracks both summer and winter capacity ratings due to significant temperature variations across its multi-state footprint. Solar projects may have lower summer ratings due to heat effects, while wind projects often have higher winter output in the upper Midwest. > [!WARNING] > > **Field availability**: MISO does not provide `interconnecting_entity` information in their queue data. Use `transmission_owner` for transmission system connection details. ## Raw fields ### Complete upstream data Each project includes **all database columns** from MISO's interconnection queue **at the top level** of the response. This provides complete transparency and access to specialized MISO fields with a clean, flat structure. > [!NOTE] > > **Complete data access**: All 41 fields (19 standardized + 22 ISO-specific) are available at the top level. No nesting, no duplication. ### MISO raw fields (22 additional fields) > **Identification & dates (8 fields)** > > * `project_id` - MISO queue identifier (e.g., "J1000") > * `queue_date` - Queue entry date > * `request_status` - Raw MISO status value > * `withdrawn_date` - Project withdrawal date (if applicable) > * `done_date` - Project completion date > * `in_service_date` - Proposed in-service date > * `negotiated_in_service_date` - Negotiated ISD (if different from proposed) > **Interconnection details (4 fields)** > > * `transmission_owner` - Transmission owner at POI > * `poi_name` - Point of Interconnection name and voltage > * `service_type` - ERIS or NRIS designation > * `post_gia_status` - Generator Interconnection Agreement status > **Study information (3 fields)** > > * `study_cycle` - Definitive Planning Phase cycle (e.g., "DPP-2018-APR") > * `study_group` - Study group assignment (Central, East, South, West) > * `study_phase` - Current study phase (DPP, GIA, etc.) > **Capacity & technology (5 fields)** > > * `summer_mw` - Summer capacity rating > * `winter_mw` - Winter capacity rating > * `fuel_type` - Raw fuel type from MISO > * `facility_type` - Raw facility/technology type > * `dp1_eris_mw`, `dp1_nris_mw` - Decision Point 1 capacity breakdowns > * `dp2_eris_mw`, `dp2_nris_mw` - Decision Point 2 capacity breakdowns > **Location (2 fields)** > > * `county` - County name > * `state` - State code ### Raw field use cases **Changelog integration** ```javascript theme={null} // Join projects with changelog using MISO's project_id const project = data.data[0]; const projectId = project.project_id; // "J1000" // Use this to query changelog API ``` **Detailed interconnection analysis** ```javascript theme={null} // Access transmission owner and POI details const transmission = project.transmission_owner; const poi = project.poi_name; const voltage = poi.match(/(\d+)\s*kV/)[1]; // Extract voltage ``` **Study status tracking** ```javascript theme={null} // Track project through MISO study process const phase = project.study_phase; const cycle = project.study_cycle; const giaStatus = project.post_gia_status; ``` **Capacity analysis** ```javascript theme={null} // Analyze ERIS vs NRIS capacity allocations const erisCapacity = project.dp2_eris_mw; const nrisCapacity = project.dp2_nris_mw; const serviceType = project.service_type; ``` > [!NOTE] > > **Data updates**: MISO queue data is updated based on MISO's Generator Interconnection Queue reports. > [!NOTE] > > **Wind focus**: MISO territory has significant wind resources, particularly in the upper Midwest states. Wind projects typically have seasonal capacity variations reflected in the summer/winter capacity fields. # NYISO interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/nyiso GET /interconnection/nyiso Access real-time NYISO interconnection queue data for all power projects ## Overview The NYISO interconnection queue endpoint provides access to real-time data from the New York Independent System Operator (NYISO) interconnection queue. NYISO serves all of New York State. > [!NOTE] > > **NYISO coverage**: Contains **400+ projects** across New York State. Top technologies: Solar (150+ projects), Wind (100+ projects), Battery Storage (80+ projects), Natural Gas (70+ projects). ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/interconnection/nyiso?limit=50" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/interconnection/nyiso?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/nyiso?limit=50', headers=headers ) data = response.json() ``` ## Coverage area **State served**: New York (entire state) ## 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 (NY) - 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 distribution | Technology | Count | Description | | - | - | - | | `Solar` | 150+ | Solar photovoltaic projects | | `Wind` | 100+ | Wind turbine projects (onshore and offshore) | | `Battery` | 80+ | Battery energy storage systems | | `Natural Gas` | 70+ | Natural gas generation | | `Other` | 50+ | Other technologies | ### Status options | Status | Description | | - | - | | `Planned` | Active projects in queue | | `Operating` | Commercial operation achieved | | `Cancelled` | Withdrawn or terminated | ### NYISO load zones | Zone | Description | Primary technologies | | - | - | - | | A | Western NY | Wind, Natural Gas | | B | Genesee | Wind, Solar | | C | Central NY | Wind, Solar | | D | North NY | Wind, Hydro | | E | Mohawk Valley | Solar, Natural Gas | | F | Capital | Solar, Wind | | G | Hudson Valley | Solar, Storage | | H | Millwood | Solar, Storage | | I | Dunwoodie | Solar, Storage | | J | NYC | Solar, Storage, Natural Gas | | K | Long Island | Solar, Storage, Wind (offshore) | ## Example requests > **Get solar projects in New York** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/nyiso?technology=Solar&state=NY&limit=50" > ``` > **Get offshore wind projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/nyiso?technology=Wind&min_capacity=400&limit=50" > ``` > **Get Ørsted projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/nyiso?developer=Orsted&limit=50" > ``` > > Filters for projects developed by Ørsted (offshore wind). Uses partial matching to find all Ørsted projects. > Note: Ørsted is stored as Orsted in the database. ## Response schema ```json Example Response theme={null} { "success": true, "iso": "NYISO", "summary": { "limit": 50, "offset": 0, "total_results": 2151, "has_more": true, "current_page": 1, "total_pages": 44 }, "filters": { "state": null, "technology": null, "status": null, "min_capacity": null, "max_capacity": null, "developer": null }, "data": [ { "iso": "NYIS", "queue_id": "0495_mohawk_solar", "project_name": "Mohawk Solar", "capacity_mw": 90.5, "technology": "S", "fuel": "S", "status": "Planned", "detailed_status": "IA Completed", "operating_date": "2027-11-01T07:00:00.000Z", "request_date": "2015-04-02T07:00:00.000Z", "county": "Montgomery", "state": "NY", "queue_position": "0495", "developer_interconnection_customer": "Mohawk Solar LLC", "developer": "AES Clean Energy", "zone": "F", "utility": "NM-NG", "balancing_authority_code": "NYIS", "technology_normalized": "Solar", "project_id": "0495_mohawk_solar", "queue_pos": "0495", "date_of_ir": "2015-04-02T07:00:00.000Z", "capacity_mw_summer": 90.5, "capacity_mw_winter": 90.5, "type_fuel": "S", "energy_storage_capability": null, "minimum_duration_full_discharge": null, "points_of_interconnection": "St. Johnsville - Marshville 115kV", "affected_transmission_owner_ato": null, "status_detailed": "IA Completed", "last_updated_date": "2022-09-30T07:00:00.000Z", "availability_of_studies": "FES, SRIS, FS", "ia_tender_date": "2021-02-08T08:00:00.000Z", "cy_fs_complete_date": "2021-02-08T08:00:00.000Z", "proposed_in_service_initial_backfeed_date": "2027-06-01T07:00:00.000Z", "proposed_sync_date": "2027-10-01T07:00:00.000Z", "proposed_cod": "2027-11-01T07:00:00.000Z", "withdrawal_date": null }, { "iso": "NYIS", "queue_id": "0522_nyc_energy", "project_name": "NYC Energy", "capacity_mw": 79.9, "technology": "ES", "fuel": "ES", "status": "Planned", "detailed_status": "Accepted Cost Allocation/IA in Progress", "operating_date": "2027-06-01T07:00:00.000Z", "request_date": "2015-12-16T08:00:00.000Z", "county": "Kings", "state": "NY", "queue_position": "0522", "developer_interconnection_customer": "NYC Energy LLC", "developer": "NYC Energy", "zone": "J", "utility": "ConEd", "balancing_authority_code": "NYIS", "technology_normalized": "Battery", "project_id": "0522_nyc_energy", "queue_pos": "0522", "date_of_ir": "2015-12-16T08:00:00.000Z", "capacity_mw_summer": 79.9, "capacity_mw_winter": 79.9, "type_fuel": "ES", "energy_storage_capability": null, "minimum_duration_full_discharge": "4.0", "points_of_interconnection": "Hudson Avenue East 138kV", "affected_transmission_owner_ato": null, "status_detailed": "Accepted Cost Allocation/IA in Progress", "last_updated_date": "2025-01-31T08:00:00.000Z", "availability_of_studies": "FES, SRIS, FS", "ia_tender_date": null, "cy_fs_complete_date": "2024-12-16T08:00:00.000Z", "proposed_in_service_initial_backfeed_date": "2027-05-01T07:00:00.000Z", "proposed_sync_date": "2027-05-01T07:00:00.000Z", "proposed_cod": "2027-06-01T07:00:00.000Z", "withdrawal_date": null } ] } ``` > [!NOTE] > > **Complete upstream data**: Each project includes all 38 database columns from NYISO's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and NYISO-specific raw fields like `queue_pos`, `energy_storage_capability`, and `minimum_duration_full_discharge`. ## Response fields ### Core identification | Field | Type | Description | | - | - | - | | `iso` | string | Always "NYIS" for NYISO data | | `queue_id` | string | Unique NYISO queue identifier (e.g., "0495\_mohawk\_solar") | | `project_id` | string | NYISO project identifier (same as queue\_id) | | `project_name` | string | Official project name in NYISO queue | | `queue_position` | string | Numeric queue position (e.g., "0495", "0522") | | `queue_pos` | string | NYISO original queue position field (same as queue\_position) | | `balancing_authority_code` | string | Always "NYIS" | ### Capacity & technology | Field | Type | Description | | - | - | - | | `capacity_mw` | number | Project nameplate capacity in MW (uses summer rating) | | `capacity_mw_summer` | number | Summer-rated capacity in MW | | `capacity_mw_winter` | number | Winter-rated capacity in MW | | `technology` | string | NYISO technology code (e.g., "S"=Solar, "ES"=Storage, "NG"=Gas) | | `type_fuel` | string | NYISO original fuel/technology type field (same as technology) | | `fuel` | string | Fuel or energy source (same as technology for NYISO) | | `technology_normalized` | string | Standardized technology for cross-ISO filtering | ### Energy storage fields | Field | Type | Description | | - | - | - | | `energy_storage_capability` | string | Energy storage capability designation (typically null) | | `minimum_duration_full_discharge` | string | Storage duration in hours at full discharge rate | ### Project status & dates | Field | Type | Description | | - | - | - | | `status` | string | Standardized status (Planned, Operating, Cancelled) | | `status_detailed` | string | Original NYISO status (e.g., "IA Completed", "SRIS/SIS in Progress") | | `detailed_status` | string | NYISO detailed status (same as status\_detailed) | | `request_date` | date | Interconnection request submission date | | `date_of_ir` | date | Date of interconnection request (same as request\_date) | | `operating_date` | date | Proposed commercial operation date | | `proposed_cod` | date | Proposed commercial operation date (same as operating\_date) | | `proposed_in_service_initial_backfeed_date` | date | Proposed initial backfeed/energization date | | `proposed_sync_date` | date | Proposed synchronization date | | `withdrawal_date` | date | Date project was withdrawn (if applicable) | | `last_updated_date` | date | Last update date in NYISO queue | ### Location | Field | Type | Description | | - | - | - | | `state` | string | Always "NY" for New York | | `county` | string | County name where project is located | | `zone` | string | NYISO load zone (A through K) | ### Study process & interconnection | Field | Type | Description | | - | - | - | | `availability_of_studies` | string | Completed studies (e.g., "FES, SRIS, FS") | | `cy_fs_complete_date` | date | Class Year Facilities Study completion date | | `ia_tender_date` | date | Interconnection Agreement tender date | ### Grid connection | Field | Type | Description | | - | - | - | | `points_of_interconnection` | string | Point of interconnection description and voltage level | | `utility` | string | Transmission Owner (TO) utility | | `affected_transmission_owner_ato` | string | Affected Transmission Owner (typically null) | ### Developer information | Field | Type | Description | | - | - | - | | `developer` | string | Developer name from Cleanview enrichment | | `developer_interconnection_customer` | string | Original NYISO interconnection customer name | > [!NOTE] > > **Data updates**: NYISO queue data is updated based on NYISO's interconnection queue reports. > [!WARNING] > > **Field availability**: Some fields like `energy_storage_capability` and `affected_transmission_owner_ato` are typically null in NYISO data. The `minimum_duration_full_discharge` field is only populated for battery storage projects. ## NYISO queue terminology ### Load zones (A-K) NYISO divides New York State into 11 geographic load zones that reflect transmission constraints and local electricity market conditions. Each zone represents a specific region with distinct pricing and capacity characteristics. | Zone | Description | Primary technologies | | - | - | - | | A | Western NY | Wind, Natural Gas | | B | Genesee | Wind, Solar | | C | Central NY | Wind, Solar | | D | North NY | Wind, Hydro | | E | Mohawk Valley | Solar, Natural Gas | | F | Capital | Solar, Wind | | G | Hudson Valley | Solar, Storage | | H | Millwood | Solar, Storage | | I | Dunwoodie | Solar, Storage | | J | NYC | Solar, Storage, Natural Gas | | K | Long Island | Solar, Storage, Wind (offshore) | ### Study process phases NYISO projects progress through a multi-phase study process to assess technical feasibility and interconnection costs. **FES (Feasibility Study)**: Initial technical and cost assessment to identify major system impacts and preliminary cost estimates. **SRIS (System Reliability Impact Study)**: Detailed reliability analysis to determine required network upgrades for system reliability. This is the standard study path for most projects. **SIS (System Impact Study)**: Alternative streamlined study path available for smaller projects with minimal system impact. **FS (Facilities Study)**: Final engineering and cost estimates for required interconnection facilities and network upgrades. ### Queue positions Projects are assigned numeric queue positions (e.g., "0495", "0522", "1721") when their interconnection request application is accepted as complete by NYISO. Lower numbers indicate earlier queue entry. ### Status types **Planned**: Active projects progressing through studies or awaiting construction. Includes statuses like "SRIS/SIS in Progress", "IA Completed", and "Accepted Cost Allocation". **Operating**: Projects that have achieved commercial operation, marked as "In Service Commercial" in NYISO data. **Cancelled**: Projects withdrawn from the queue, with withdrawal dates tracked for historical reference. ### Technology codes NYISO uses single-letter or two-letter codes for technology types: "S" (Solar), "ES" (Energy Storage), "NG" (Natural Gas), "W" (Wind), "F" (Flywheel), "DC" (DC Transmission), "AC" (AC Transmission), "L" (Load/Data Center). ### Storage duration For battery storage projects, the `minimum_duration_full_discharge` field indicates how many hours the system can discharge at full rated capacity. Common values are "2.0", "4.0", or "8.0" hours. # PJM interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/pjm GET /interconnection/pjm Access real-time PJM interconnection queue data for all power projects ## Overview The PJM interconnection queue endpoint provides access to real-time data from PJM Interconnection's generation interconnection queue. PJM serves 13 states and the District of Columbia in the Mid-Atlantic and Midwest regions. > [!NOTE] > > **PJM coverage**: Contains **9,200+ projects** across 13 states. Top technologies: Solar (4,000+ projects), Natural Gas (1,100+ projects), Storage (1,000+ projects), Wind (700+ projects). ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/interconnection/pjm?limit=50" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/interconnection/pjm?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/pjm?limit=50', headers=headers ) data = response.json() ``` ## Coverage area **States served**: Delaware, Illinois, Indiana, Kentucky, Maryland, Michigan, New Jersey, North Carolina, Ohio, Pennsylvania, Tennessee, Virginia, West Virginia, and Washington D.C. ## 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 (PA, OH, NJ, etc.) - supports comma-separated | | `technology` | string | - | Filter by standardized technology type (derived from fuel\_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. See our [Interconnection Reference](/api-reference/interconnection-codes#technology-classifications) for all available options. | Technology | Count | Description | | - | - | - | | `Solar` | 4,000+ | Solar photovoltaic projects | | `Natural Gas` | 1,100+ | Natural gas generation | | `Storage` | 1,000+ | Battery energy storage systems | | `Wind` | 700+ | Wind turbine projects | | `Solar; Storage` | 500+ | Combined solar and storage projects | | `Methane` | 190+ | Methane/biogas projects | | `Coal` | 140+ | Coal generation | | `Hydro` | 95+ | Hydroelectric projects | | `Offshore Wind` | 80+ | Offshore wind projects | | `Nuclear` | 78+ | Nuclear generation | | `Other` | 300+ | Other technologies | > [!NOTE] > > **Technology mapping**: The `technology` field is standardized from PJM's original `fuel_type` data to provide consistent filtering across all CleanView APIs. ### Status options | Status | Count | Description | | - | - | - | | `Planned` | 1,200+ | Active projects in queue | | `Operating` | 400+ | Commercial operation achieved | | `Cancelled` | 200+ | Withdrawn or terminated | ### Top states by project count | State | Project count | Top technology | | - | - | - | | Pennsylvania | About 400 | Solar, natural gas | | Ohio | About 300 | Solar, wind | | New Jersey | About 250 | Solar | | Illinois | About 200 | Solar, wind | | Virginia | About 180 | Solar | ## Example requests > **Get active solar projects in Pennsylvania** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/pjm?technology=Solar&status=Planned&state=PA&limit=50" > ``` > > Returns active solar projects in Pennsylvania within the PJM territory. > **Get large natural gas projects (>300 MW)** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/pjm?technology=Natural%20Gas&min_capacity=300&limit=50" > ``` > > Finds large-scale natural gas projects in the PJM queue. > **Get projects by multiple states** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/pjm?state=PA,OH,NJ&limit=50" > ``` > > Uses comma-separated values for multi-state filtering in the Mid-Atlantic region. > **Get projects by developer** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/pjm?developer=Invenergy&limit=50" > ``` > > Filters projects that have developer mapping data. Supports partial matching (e.g., "Invenergy" matches "Invenergy LLC"). Projects without developer data are excluded from filtered results. ## Response schema ```json Example Response theme={null} { "iso": "PJM", "summary": { "limit": 50, "offset": 0, "total_results": 1834, "has_more": true, "current_page": 1, "total_pages": 37 }, "filters": { "state": null, "technology": null, "status": null, "min_capacity": null, "max_capacity": null, "developer": null }, "data": [ { "iso": "PJM", "queue_id": "1003606", "project_name": "FE-PJM", "capacity_mw": 200.0, "technology": "Solar", "fuel": "Solar", "status": "Planned", "detailed_status": "Active", "operating_date": "2025-12-01T00:00:00.000Z", "request_date": "2022-03-15T00:00:00.000Z", "county": "Chester", "state": "PA", "queue_position": null, "interconnecting_entity": null, "developer": "Lightsource BP", "feasibility_study_status": "Complete", "system_impact_study_status": "In Progress", "facilities_study_status": "Not Started", "interconnection_agreement_status": null, "construction_service_agreement_status": null, "transmission_owner": "PECO", "project_type": "Generation Interconnection", "balancing_authority_code": "PJM", "technology_normalized": "Solar", "project_number": "1003606", "commercial_name": "Keystone Solar", "maximum_facility_output": 200 }, { "iso": "PJM", "queue_id": "V1-026", "project_name": "Limerick", "capacity_mw": 150.0, "technology": "Wind", "fuel": "Wind", "status": "Operating", "detailed_status": "In Service", "operating_date": "2024-06-15T00:00:00.000Z", "request_date": "2021-08-20T00:00:00.000Z", "county": "Huron", "state": "OH", "queue_position": null, "interconnecting_entity": null, "developer": "EDF Renewables", "feasibility_study_status": "Complete", "system_impact_study_status": "Complete", "facilities_study_status": "Complete", "interconnection_agreement_status": "Executed", "construction_service_agreement_status": "Executed", "transmission_owner": "AEP", "project_type": "Generation Interconnection", "balancing_authority_code": "PJM", "technology_normalized": "Wind", "project_number": "V1-026", "commercial_name": "Buckeye Wind", "maximum_facility_output": 150 } ] } ``` > [!NOTE] > > **Complete upstream data**: Each project includes all 51 database columns from PJM's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and PJM-specific raw fields like `project_number`, `maximum_facility_output`, and `is_behind_meter`. ## Response fields ### Core fields (always present) | Field | Type | Description | | - | - | - | | `iso` | string | Always "PJM" for PJM data | | `queue_id` | string | Unique PJM project number (e.g., "1003606" or "V1-026") | | `project_name` | string | Project name (usually available) | | `capacity_mw` | number | Project capacity in MW | | `technology` | string | Standardized technology type | | `status` | string | Standardized status (Planned, Operating, Cancelled) | | `queue_position` | string | Queue position identifier (null - PJM does not provide queue position data) | | `balancing_authority_code` | string | Always "PJM" | ### Location & timing | Field | Type | Description | | - | - | - | | `state` | string | State code (PA, OH, NJ, etc.) | | `county` | string | County name where project is located | | `operating_date` | date | Expected/actual commercial operation date | | `request_date` | date | Date project entered queue | ### Technology & fuel | Field | Type | Description | | - | - | - | | `fuel` | string | Original fuel type from PJM data | | `technology` | string | Standardized technology type (derived from fuel\_type) | | `technology_normalized` | string | Same as `technology` for consistency | ### PJM-specific fields | Field | Type | Description | | - | - | - | | `transmission_owner` | string | Transmission utility (PECO, PPL, etc.) | | `project_type` | string | Interconnection type (Generation Interconnection, etc.) | ### Study process | Field | Type | Description | | - | - | - | | `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 | | `interconnection_agreement_status` | string | Interconnection agreement execution status | ### Developer information | Field | Type | Description | | - | - | - | | `interconnecting_entity` | string | Always null - PJM queue does not provide interconnecting entity information | | `developer` | string | Developer name (limited availability) | > [!NOTE] > > **Data updates**: PJM queue data is updated monthly based on PJM's New Services Queue reports. The API reflects the most recent interconnection queue data available. > [!NOTE] > > **Study process**: PJM uses a detailed multi-phase study process including feasibility, system impact, and facilities studies. The study status fields track progress through each phase. > [!WARNING] > > **Missing coordinates**: PJM data does not include latitude/longitude coordinates. Use the `county`, `state`, and `transmission_owner` fields for geographic analysis. # Unified power projects Source: https://docs.cleanview.co/api-reference/endpoint/projects GET /projects Access unified power project data combining EIA 860M and interconnection queue sources ## Overview The unified power projects endpoint provides a simplified, consolidated view of power 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 power project landscape. ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/projects?limit=50&technology=Solar&state=CA" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/projects?limit=50&technology=Solar&state=CA', { 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/projects?limit=50&technology=Solar&state=CA', 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 (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 | > [!NOTE] > > **Hybrid project availability**: Hybrid technology classifications are available for interconnection queue data (PJM, MISO, SPP, NE-ISO, NYISO) but not for CAISO, ERCOT, or EIA 860M data sources. ### 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. The `developer` 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** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/projects?technology=Solar&state=CA&limit=50" > ``` > **Get operating projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/projects?status=Operating&limit=50" > ``` > **Get large projects (>100 MW)** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/projects?min_capacity=100&limit=50" > ``` > **Get projects from EIA data only** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/projects?source_table=eia_860m&limit=50" > ``` > **Get projects by specific developer** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/projects?developer=NextEra&limit=50" > ``` ### 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** | > [!WARNING] > > **System limitations**: Our current query system is not optimized for detecting hybrid projects in CAISO, ERCOT, or EIA data sources. ### 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** [**See our complete hybrid project system limitations documentation.**](/known-issues#hybrid-project-system-limitations) ## Response schema ```json Example Response theme={null} { "summary": { "limit": 50, "offset": 0, "total_results": 62222, "has_more": true, "current_page": 1, "total_pages": 1245 }, "filters": { "state": null, "technology": null, "status": "all", "source_table": null, "min_capacity": null, "max_capacity": null, "balancing_authority": null, "developer": null }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [ { "source_table": "eia_860m", "source_id": "57472_CTG", "project_name": "TBE-Montgomery LLC", "capacity_mw": 12, "operating_date": "2039-12-01", "technology": "Biomass", "county": "Orange", "state": "NY", "balancing_authority": "NYIS", "status": "Planned", "latitude": 41.4885, "longitude": -74.2262, "has_ia_signed": null, "under_construction": true, "ir_request_date": null, "developer": null }, { "source_table": "miso_queue", "source_id": "J4004", "project_name": "Other_", "capacity_mw": 392, "operating_date": "2032-10-31", "technology": "Solar", "county": "Peoria", "state": "IL", "balancing_authority": "MISO", "status": "Planned", "latitude": null, "longitude": null, "has_ia_signed": false, "under_construction": false, "ir_request_date": "2025-05-03", "raw_fields": { "project_id": "J4004", "request_status": "Active", "queue_date": "2025-05-03T04:00:00.000Z", "withdrawn_date": null, "done_date": null, "in_service_date": "2032-10-31T04:00:00.000Z", "transmission_owner": "AMEREN TRANSMISSION COMPANY OF ILLINOIS", "county": "Peoria", "state": "IL", "study_cycle": "DPP Cycle Pending", "study_group": "Central", "study_phase": null, "service_type": null, "poi_name": "Other_", "summer_mw": 392, "winter_mw": 392, "fuel_type": "Solar", "facility_type": "Photovoltaic", "post_gia_status": null, "negotiated_in_service_date": null, "dp1_eris_mw": 0, "dp1_nris_mw": 0, "dp2_eris_mw": 0, "dp2_nris_mw": 0 }, "developer": null } ] } ``` > [!NOTE] > > **Raw fields for ISO queue data**: Projects from interconnection queue sources (CAISO, ERCOT, PJM, MISO, NYISO, ISO-NE, SPP) include a nested `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 fields `has_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. > [!NOTE] > > **Milestone vs. current state**: A project with `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 ```json theme={null} { "source_table": "miso_queue", "source_id": "J720", "project_name": "Lakefield - Raun 345 kV line", "status": "Cancelled", "has_ia_signed": true, "under_construction": true, "ir_request_date": "2018-03-12" } ``` This cancelled MISO project shows: * `has_ia_signed: true` — The project secured an Interconnection Agreement * `under_construction: true` — Construction had begun before withdrawal * The `status: Cancelled` indicates the project is no longer active > [!TIP] > > **Attrition analysis**: Query `status=Cancelled` with `has_ia_signed=true` to find projects that failed after securing an IA—these represent late-stage failures with different characteristics than early-stage withdrawals. ### ISO-specific raw fields | Field | Type | Description | | - | - | - | | `raw_fields` | object | Nested object containing all ISO-specific upstream data (interconnection queue sources only) | The `raw_fields` object structure varies by `source_table`: * **CAISO queue**: See [CAISO endpoint documentation](/api-reference/endpoint/caiso) for 47 CAISO-specific fields * **ERCOT queue**: See [ERCOT endpoint documentation](/api-reference/endpoint/ercot) for 45 ERCOT-specific fields * **PJM queue**: See [PJM endpoint documentation](/api-reference/endpoint/pjm) for 38 PJM-specific fields * **MISO queue**: See [MISO endpoint documentation](/api-reference/endpoint/miso) for 41 MISO-specific fields (includes DPP process fields) * **NYISO queue**: See [NYISO endpoint documentation](/api-reference/endpoint/nyiso) for 38 NYISO-specific fields (includes storage fields) * **ISO-NE queue**: See [ISO-NE endpoint documentation](/api-reference/endpoint/iso-ne) for 41 ISO-NE-specific fields (includes five-phase study process) * **SPP queue**: See [SPP endpoint documentation](/api-reference/endpoint/spp) for 43 SPP-specific fields (includes DISIS cluster data) * **EIA 860M**: No raw\_fields object - only standardized fields listed above > [!NOTE] > > **Data consolidation**: This endpoint provides a simplified view of complex power project data. For detailed information, use the specific EIA 860M or interconnection queue endpoints. > [!NOTE] > > **Cross-Reference**: Projects may appear in multiple sources. The `source_table` and `source_id` fields help identify the original data source for each record. # SPP interconnection queue Source: https://docs.cleanview.co/api-reference/endpoint/spp GET /interconnection/spp Access real-time Southwest Power Pool interconnection queue data for all power projects ## Overview The SPP interconnection queue endpoint provides access to real-time data from Southwest Power Pool's interconnection queue. SPP serves the central United States with significant wind resources. > [!NOTE] > > **SPP coverage**: Contains **800+ projects** across the central U.S. Top technologies: Wind (400+ projects), Solar (200+ projects), Battery Storage (100+ projects), Natural Gas (100+ projects). ## Endpoint ```bash cURL theme={null} curl -H "x-api-key: your_api_key_here" \ "https://api.cleanview.co/api/v1/interconnection/spp?limit=50" ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/interconnection/spp?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/spp?limit=50', headers=headers ) data = response.json() ``` ## Coverage area **States served**: Arkansas, Kansas, Louisiana, Missouri, Nebraska, New Mexico, Oklahoma, and Texas, with portions of Iowa, Minnesota, Montana, North Dakota, South Dakota, and Wyoming. ## 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 - 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 distribution | Technology | Count | Description | | - | - | - | | `Wind` | 400+ | Wind turbine projects (dominant in SPP territory) | | `Solar` | 200+ | Solar photovoltaic projects | | `Battery` | 100+ | Battery energy storage systems | | `Natural Gas` | 100+ | Natural gas generation | | `Other` | 50+ | Other technologies | ### Status options | Status | Description | | - | - | | `Planned` | Active projects in queue | | `Operating` | Commercial operation achieved | | `Cancelled` | Withdrawn or terminated | ### Top states by project count | State | Project count | Top technology | | - | - | - | | Oklahoma | 340 | Wind, Solar | | Kansas | 199 | Wind | | Nebraska | 129 | Wind | | Texas | 106 | Wind, Solar | | New Mexico | 75 | Solar, Wind | ## Example requests > **Get wind projects in Kansas** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/spp?technology=Wind&state=KS&limit=50" > ``` > **Get large solar projects (>100 MW)** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/spp?technology=Solar&min_capacity=100&limit=50" > ``` > **Get NextEra Energy projects** > > ```bash theme={null} > curl -H "x-api-key: your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/spp?developer=NextEra&limit=50" > ``` > > Filters for projects developed by NextEra Energy Resources. Uses partial matching to find all NextEra projects in SPP territory. ## Response schema ```json Example Response theme={null} { "iso": "SPP", "summary": { "limit": 50, "offset": 0, "total_results": 2806, "has_more": true, "current_page": 1, "total_pages": 57 }, "filters": { "state": null, "technology": null, "status": null, "min_capacity": null, "max_capacity": null, "developer": null }, "data": [ { "iso": "SWPP", "queue_id": "GEN-2011-019", "project_name": "Woodward County", "capacity_mw": 175, "technology": "Wind", "fuel": null, "status": "Planned", "detailed_status": "IA FULLY EXECUTED/ON SCHEDULE", "operating_date": "2027-12-31", "request_date": "3/31/2011", "county": "Woodward County", "state": "OK", "queue_position": null, "interconnecting_entity": null, "developer": null, "balancing_authority_code": "SWPP", "technology_normalized": "Wind", "generation_interconnection_number": "GEN-2011-019", "ifs_queue_number": null, "current_cluster": "DISIS-2011-001-8", "cluster_group": "04 SOUTHEAST", "nearest_town_or_county": "Woodward County", "to_at_poi": "OGE", "in_service_date": "2012-12-31", "commercial_operation_date": "2027-12-31", "cessation_date": null, "original_generator_commercial_op_date": null, "capacity": 175, "max_summer_mw": 175, "max_winter_mw": 175, "service_type": "ER/NR", "requested_maximum_injection_capability_mw": 0, "requested_network_resource_deliverability_mw": 0, "nameplate_capacity": 0, "generation_type": "Wind", "fuel_type": null, "substation_or_line": "Woodward EHV 345kV", "request_received": "3/31/2011", "date_withdrawn": null, "jtiq_participant": null, "jtiq_commitment": null, "cause_of_delay": null, "status_detailed": "IA FULLY EXECUTED/ON SCHEDULE" } ] } ``` > [!NOTE] > > **Complete upstream data**: Each project includes all 43 database columns from SPP's interconnection queue at the top level. This provides complete transparency with both standardized fields (normalized across all ISOs) and SPP-specific raw fields like `generation_interconnection_number`, `current_cluster`, and `jtiq_participant`. ## Response fields ### Core identification fields | Field | Type | Description | | - | - | - | | `iso` | string | Always "SWPP" for SPP data | | `queue_id` | string | Unique SPP queue identifier (e.g., "GEN-2011-019") | | `generation_interconnection_number` | string | Official SPP Generation Interconnection Request number | | `ifs_queue_number` | string | SPP Integrated Facilities Study queue number (if applicable) | | `project_name` | string | Official project name in SPP queue | | `balancing_authority_code` | string | Always "SWPP" | | `queue_position` | string | Queue position number (typically null in SPP data) | ### Capacity & technology | Field | Type | Description | | - | - | - | | `capacity_mw` | number | Project nameplate capacity in MW | | `capacity` | number | Duplicate of capacity\_mw for compatibility | | `max_summer_mw` | number | Maximum summer capacity rating in MW | | `max_winter_mw` | number | Maximum winter capacity rating in MW | | `nameplate_capacity` | number | Generator nameplate capacity in MW | | `requested_maximum_injection_capability_mw` | number | Requested maximum MW injection to grid | | `requested_network_resource_deliverability_mw` | number | Requested network resource deliverability capacity in MW | | `technology` | string | SPP's technology classification (e.g., "Wind", "Solar") | | `generation_type` | string | Detailed generation type from SPP source | | `technology_normalized` | string | Standardized technology for cross-ISO filtering | | `fuel` | string | Primary fuel source code | | `fuel_type` | string | Detailed fuel type description with hybrid notation | ### Project status & dates | Field | Type | Description | | - | - | - | | `status` | string | Standardized status (Planned, Operating, Cancelled, Inactive) | | `detailed_status` | string | Original SPP detailed status code | | `status_detailed` | string | Duplicate of detailed\_status for compatibility | | `request_date` | string | Interconnection request submission date | | `request_received` | string | Date SPP received interconnection request | | `in_service_date` | string | Originally scheduled in-service date | | `operating_date` | string | Expected or actual commercial operation date | | `commercial_operation_date` | string | Actual commercial operation date when achieved | | `original_generator_commercial_op_date` | string | Original projected commercial operation date | | `date_withdrawn` | string | Date project was withdrawn from queue (if applicable) | | `cessation_date` | string | Date project operations ceased (if applicable) | ### Location | Field | Type | Description | | - | - | - | | `state` | string | State code (OK, KS, NE, TX, NM, MO, ND, AR, SD, LA, MT, IA, MN) | | `county` | string | County name where project is located | | `nearest_town_or_county` | string | Nearest town or county from SPP source | ### Study process & cluster information | Field | Type | Description | | - | - | - | | `current_cluster` | string | Current DISIS cluster assignment (e.g., "DISIS-2011-001-8") | | `cluster_group` | string | SPP transmission zone for cluster studies (e.g., "04 SOUTHEAST") | | `cause_of_delay` | string | Reason for study process delays (if applicable) | ### Grid connection & service | Field | Type | Description | | - | - | - | | `service_type` | string | Interconnection service type (ER, NR, or ER/NR) | | `to_at_poi` | string | Transmission Owner at Point of Interconnection | | `substation_or_line` | string | Specific substation or transmission line for interconnection | | `interconnecting_entity` | string | Interconnecting utility entity (typically null) | ### SPP-specific fields | Field | Type | Description | | - | - | - | | `jtiq_participant` | string | Joint Targeted Interconnection Queue participant (Yes/No/null) | | `jtiq_commitment` | number | JTIQ financial commitment amount (if applicable) | ### Developer information | Field | Type | Description | | - | - | - | | `developer` | string | Developer name from Cleanview enrichment (limited coverage) | ## SPP queue terminology ### DISIS (Definitive Interconnection System Impact Study) SPP's cluster study process where projects are studied in annual cohorts grouped by transmission zone. Projects are studied together to assess cumulative system impacts and allocate network upgrade costs equitably among projects in each cluster. ### Cluster groups SPP divides its territory into transmission zones (e.g., "04 SOUTHEAST", "03 CENTRAL") for organizing DISIS cluster studies. Each annual DISIS cohort (e.g., "DISIS-2011-001") contains projects grouped by these zones for efficient regional analysis. ### Service types * **ER (Energy Resource)**: Energy-only interconnection without transmission network upgrade obligations * **NR (Network Resource)**: Full network service requiring participation in network upgrade costs and providing firm transmission capacity * **ER/NR**: Hybrid service combining both energy resource and network resource interconnection rights ### JTIQ (Joint Targeted Interconnection Queue) Coordinated interconnection study process for projects located at the SPP/MISO seam requiring joint analysis by both ISOs to assess impacts on both systems. ### Generation Interconnection Agreement (GIA) Final contract between generator and SPP governing interconnection terms, cost allocation, operational requirements, and construction milestones. ### Status categories SPP tracks detailed project status through multiple study phases: * **IA FULLY EXECUTED/ON SCHEDULE**: Interconnection Agreement signed and project on schedule * **IA FULLY EXECUTED/COMMERCIAL OPERATION**: Project has achieved commercial operation * **IA FULLY EXECUTED/ON SUSPENSION**: Agreement executed but study process suspended * **IA PENDING**: Interconnection Agreement pending execution * **DISIS STAGE**: In Definitive Interconnection System Impact Study phase * **FACILITY STUDY STAGE**: In Facilities Study phase evaluating specific interconnection facilities * **FEASIBILITY**: In Feasibility Study phase * **ERAS**: In Early Risk Assessment Study phase (optional pre-study) * **WITHDRAWN**: Project withdrawn from queue by developer * **TERMINATED**: Project terminated by SPP > [!NOTE] > > **Data updates**: SPP queue data is updated based on Southwest Power Pool's Generation Interconnection queue reports. # Interconnection queues reference Source: https://docs.cleanview.co/api-reference/interconnection-codes Comprehensive guide to ISO/RTO interconnection queue data, technology mappings, status codes, and field definitions. # 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 | > [!NOTE] > > 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](https://www.eia.gov/electricity/data/eia860m/). > > **Official ISO documentation:** > > * [CAISO Generator Interconnection](https://www.caiso.com/generation-transmission/generation/generator-interconnection) (Official CAISO interconnection process page) > * [CAISO Business Practice Manual for GIDAP](https://bpmcm.caiso.com/BPM%20Document%20Library/Generator%20Interconnection%20and%20Deliverability%20Allocation%20Procedures/BPM_for_GIDAP_V29_redline.pdf) (Detailed procedures manual) > * [ERCOT Planning Guide](https://www.ercot.com/mktrules/guides/planning/current) (Section 5: Generation Resource Interconnection) > * [ERCOT Resource Integration](https://www.ercot.com/services/rq/integration) (Interconnection process guidance) > * [PJM Manual 14C](https://www.pjm.com/directory/manuals/m14c/index.html) (Generation and Transmission Interconnection Process) > * [PJM Interconnection Library](https://www.pjm.com/library/manuals.aspx) (Complete manual library) > * [MISO Business Practices Manual](https://www.misoenergy.org/legal/business-practices-manuals/) (Generator Interconnection procedures) > * For geographic coverage, see [FERC Electric Industry Forms](https://www.ferc.gov/industries-data/electric/general-information/electric-industry-forms/form-no-714-annual/about-form-714) *** ## 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 > [!WARNING] > > **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**: > > ```json theme={null} > { > "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). > [!NOTE] > > **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 **CAISO** **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`. **ERCOT** **Raw Excel structure**: Separate rows for each technology component * Each component has its own INR (Interconnection Request) number * Single "Fuel" and "Technology" column per row * Related projects often share similar naming patterns **API response**: Each technology component appears as a separate record, matching ERCOT's structure. To identify related hybrid components, look for: * Similar project naming patterns (e.g., "Lupinus Solar 1" and "Lupinus Storage 1") * Same POI location * References in the comments field **Example**: A solar + storage project appears as two separate rows in ERCOT's Excel: * Row 1: INR=23INR0035, Project Name="Starling Solar", Fuel="SOL", Capacity=123 MW * Row 2: INR=23INR0181, Project Name="Starling Storage", Fuel="OTH", Capacity=63.6 MW **PJM** **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 **MISO** **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 **SPP** **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" **NYISO** **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" **ISO-NE** **Raw Excel structure**: Single row with space-separated codes * Fuel Type column contains codes like "SUN BAT" (Solar + Battery) * "WND BAT" for Wind + Battery combinations **API response**: Single record with compound codes parsed into appropriate hybrid technology classifications. **Example**: fuel\_type="SUN BAT", technology\_normalized="Hybrid - Solar + Storage" > [!NOTE] > > **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 > [!WARNING] > > When analyzing hybrid projects across ISOs, be aware that: > > 1. **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 > 2. **Project counting**: > * CAISO: One Excel row can become multiple API records > * ERCOT: Already multiple rows in source data > * Others: One-to-one mapping maintained > 3. **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: ```json theme={null} { "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 ```bash theme={null} 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 ```bash theme={null} 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 ```bash theme={null} curl -H "x-api-key: your_api_key" \ "https://api.cleanview.co/api/v1/interconnection/pjm?technology=Solar,Wind&limit=50" ``` > [!TIP] > > For optimal performance, use specific filters to narrow your results. The API works best with targeted queries rather than broad data exports. # Interconnection queue API overview Source: https://docs.cleanview.co/api-reference/interconnection-overview Access power project data from 7 major grid operators. Streamlined parameters designed for data analysis and pipeline applications. # 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/RTO | States served | Project count | Top technologies | | - | - | - | - | | [**CAISO**](/api-reference/endpoint/caiso) | CA, NV, AZ | 3,000+ | Solar, Battery, Wind | | [**ERCOT**](/api-reference/endpoint/ercot) | TX | 2,200+ | Solar, Wind, Hybrid | | [**PJM**](/api-reference/endpoint/pjm) | 13 Mid-Atlantic states | 1,800+ | Solar, Natural Gas, Wind | | [**MISO**](/api-reference/endpoint/miso) | 15 Midwest/South states | 1,500+ | Wind, Solar, Natural Gas | | [**SPP**](/api-reference/endpoint/spp) | 8 Central states | 800+ | Wind, Solar, Battery | | [**NYISO**](/api-reference/endpoint/nyiso) | NY | 400+ | Solar, Wind, Battery | | [**ISO-NE**](/api-reference/endpoint/iso-ne) | 6 New England states | 300+ | 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** ```bash theme={null} # 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: ```json theme={null} { "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 power project 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: ```json theme={null} { "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. # API reference Source: https://docs.cleanview.co/api-reference/introduction Complete reference for all Cleanview API endpoints ## Base URL All API requests should be made to: ``` https://api.cleanview.co/api/v1 ``` ## Authentication All endpoints require authentication using an API key in the x-api-key header: ```bash theme={null} x-api-key: cv_pub_your_api_key_here ``` See the [Authentication guide](/authentication) for detailed information on obtaining and using API keys. ## Try it out You can test API endpoints directly in this documentation using the **"Try it"** feature: 1. Navigate to any endpoint page (e.g., [EIA 860M](/api-reference/endpoint/eia-860m)) 2. Click the **Try it** button 3. Enter your API key in the format: `cv_pub_your_api_key_here` 4. Set your desired parameters 5. Click **Send** to test the endpoint live > [!TIP] > > **Need an API key?** [Contact sales](https://cleanview.co/contact-sales) to request access. ## Response format All API responses follow a consistent structure: ```json theme={null} { "success": true, "summary": { "limit": 50, "offset": 0, "total_results": 1000, "has_more": true, "current_page": 1, "total_pages": 20 }, "filters": { "state": "CA", "technology": "Solar" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [...] } ``` ### Response fields | Field | Type | Description | | - | - | - | | `success` | boolean | Indicates if the request was successful | | `summary` | object | Pagination and result summary information | | `filters` | object | Applied filters for the request | | `customer` | object | Customer information for the API key | | `data` | array/object | The requested data | ## Error handling When a request fails, the API returns an appropriate HTTP status code and error information: ```json theme={null} { "error": "INVALID_API_KEY", "message": "The provided API key is invalid or has been revoked" } ``` ### Common error codes | Error code | HTTP status | Description | | - | - | - | | `API_KEY_MISSING` | 401 | No API key provided | | `INVALID_API_KEY` | 401 | Invalid or revoked API key | | `INVALID_LIMIT` | 400 | Invalid limit parameter (must be 50-5000) | | `INVALID_OFFSET` | 400 | Invalid offset parameter | | `INTERNAL_ERROR` | 500 | Server error | ## Pagination All list endpoints support pagination using `limit` and `offset` parameters: | Parameter | Type | Default | Range | Description | | - | - | - | - | - | | `limit` | integer | 1000 | 50-5000 | Number of records to return | | `offset` | integer | 0 | ≥0 | Number of records to skip | **Example:** ``` GET /api/v1/eia-860m?limit=100&offset=200 ``` ## Available endpoints > **[Data centers](/api-reference/endpoint/data-centers)** > > All data center records with capacity, tenants, and locations > **[Data center campuses](/api-reference/endpoint/data-center-campuses)** > > Data center campuses with status and capacity rolled up from their buildings > **[Gas plants](/api-reference/endpoint/gas-plants)** > > Behind-the-meter gas plants built to power data centers > **[Gas plant units](/api-reference/endpoint/gas-plant-units)** > > The turbines, engines and fuel cells at each plant, by manufacturer and model > **[EIA 860M data](/api-reference/endpoint/eia-860m)** > > Access the latest EIA 860M records for planned and operating power plants > **[ERCOT queue](/api-reference/endpoint/ercot)** > > Real-time interconnection queue data from ERCOT > **[CAISO queue](/api-reference/endpoint/caiso)** > > Real-time interconnection queue data from CAISO > **[PJM queue](/api-reference/endpoint/pjm)** > > Real-time interconnection queue data from PJM > **[MISO queue](/api-reference/endpoint/miso)** > > Real-time interconnection queue data from MISO > **[SPP queue](/api-reference/endpoint/spp)** > > Real-time interconnection queue data from SPP > **[NYISO queue](/api-reference/endpoint/nyiso)** > > Real-time interconnection queue data from NYISO > **[ISO-NE queue](/api-reference/endpoint/iso-ne)** > > Real-time interconnection queue data from ISO-NE > **[Unified power projects](/api-reference/endpoint/projects)** > > Consolidated power project database merging data from all sources ## Data sources The Cleanview API aggregates data from multiple authoritative sources: * **Cleanview data center database**: Data center projects researched from permits, filings, and public records * **EIA 860M**: U.S. Energy Information Administration monthly electric generator inventory * **Grid operator queues**: Real-time interconnection queue data from major ISOs/RTOs * **Cleanview database**: Unified power project records with cross-referencing and data quality improvements > [!NOTE] > > **Data freshness**: Most data is updated daily, with some sources updated more frequently. Check the `last_updated` field in API responses for specific timestamp information. # Authentication Source: https://docs.cleanview.co/authentication Learn how to authenticate with the Cleanview API using API keys ## API key authentication The Cleanview API uses API key authentication. All requests must include a valid API key in the `x-api-key` header. ### API key format API keys follow this format: ``` cv_pub_[32 random characters base64url encoded] ``` **Example:** `cv_pub_KJ3x9mN2pQ8rS7tV5wY6zA1bC4dE0fG2` ### Making authenticated requests Include your API key in the `x-api-key` header: ```bash theme={null} x-api-key: cv_pub_your_api_key_here ``` ## Request examples ```bash cURL theme={null} curl -H "x-api-key: cv_pub_your_api_key_here" \ https://api.cleanview.co/api/v1/eia-860m ``` ```javascript JavaScript theme={null} const response = await fetch('https://api.cleanview.co/api/v1/eia-860m', { headers: { 'x-api-key': 'cv_pub_your_api_key_here' } }); const data = await response.json(); ``` ```python Python theme={null} import requests headers = { 'x-api-key': 'cv_pub_your_api_key_here' } response = requests.get( 'https://api.cleanview.co/api/v1/eia-860m', headers=headers ) data = response.json() ``` ```php PHP theme={null} ``` ## Authentication errors When authentication fails, the API will return a `401 Unauthorized` status code with an error response: ```json theme={null} { "error": "INVALID_API_KEY", "message": "The provided API key is invalid or has been revoked" } ``` ### Common error codes | Error code | Description | | - | - | | `MISSING_API_KEY` | No API key provided in the request | | `INVALID_API_KEY` | API key doesn't exist or is inactive | ## Security best practices > **Keep your API key secure** > > * Never expose your API key in client-side code or public repositories > * Store API keys as environment variables > * Use different API keys for different environments (development, staging, production) > * Regularly rotate your API keys > **Server-side only** > > API keys should only be used in server-side applications. Never include them in: > > * Frontend JavaScript code > * Mobile applications > * Public GitHub repositories > * Configuration files committed to version control > **Monitor usage** > > * Regularly review your API usage patterns > * Watch for unexpected spikes in requests > * Contact support if you notice suspicious activity ## Getting your API key **1. Contact sales** API keys are provisioned by our team. Request access through our [contact sales page](https://cleanview.co/contact-sales). **2. Tell us how you plan to use the API** Let us know if you plan to use the data for internal business use only or want to integrate it into your product. **3. Receive your key** Our team will review your request and provide you with an API key along with any specific usage guidelines. > [!NOTE] > > **Future self-service:** We're working on a self-service API key management portal that will be available in a future version of the API. # Welcome to the Cleanview API Source: https://docs.cleanview.co/index Track data centers and power projects from the first permit to final completion. Use our API to track thousands of data centers and power projects, 500+ developers, and the most important market trends in real-time. ![Map of every data center, behind-the-meter power plant and solar and storage project under construction in the US that Cleanview tracks](https://mintcdn.com/cleanview-77a395e9/0pJaGxVfaK3wb8iz/images/home-hero-map.png?fit=max\&auto=format\&n=0pJaGxVfaK3wb8iz\&q=85\&s=6815b8bf9a4c7f5850a916c55d67ad6a) ## Overview The Cleanview API provides secure, programmatic access to data center and power project data across the United States, including our data center database, EIA records, and interconnection queue information from major grid operators. **Current API version:** v1\ **Base URL:** `https://api.cleanview.co/api/v1`\ **Authentication:** API key required > **[Quick start](/quickstart)** > > Get your API key and make your first request in minutes > **[Authentication](/authentication)** > > Learn how to authenticate your requests with API keys ## Available data sources Access data center and power project datasets through our REST API endpoints. > **[Data centers](/api-reference/endpoint/data-centers)** > > Data center projects with capacity, tenants, and locations > **[Interconnection queues](/api-reference/endpoint/ercot)** > > Real-time queue data from ERCOT, CAISO, PJM, MISO, SPP, NYISO, and ISO-NE > **[EIA 860M data](/api-reference/endpoint/eia-860m)** > > Latest EIA 860M records for planned and operating power plants > **[Unified power projects](/api-reference/endpoint/projects)** > > Consolidated power project database merging data from all sources ## Key features * **Comprehensive coverage:** Thousands of data centers plus 7 major grid operator interconnection queues * **Real-time data:** Up-to-date project information and queue status * **Standardized format:** Consistent API responses across all data sources * **Secure access:** API key authentication with usage tracking * **High performance:** Sub-500ms response times for most endpoints > [!NOTE] > > **Requesting access:** API keys are provisioned by our team. [Contact sales](https://cleanview.co/contact-sales) to request access. # Quick start guide Source: https://docs.cleanview.co/quickstart Start making API requests to Cleanview in under 5 minutes ## Get your API key To access the Cleanview API, you'll need an API key. API keys are provisioned by our team. **1. Request access** Contact our team to request an API key through our [contact sales page](https://cleanview.co/contact-sales), with: * Your name and company * Intended use case for the API * Expected request volume **2. Receive your key** You'll receive your API key in the format: `cv_pub_[32 random characters]` Example: `cv_pub_KJ3x9mN2pQ8rS7tV5wY6zA1bC4dE0fG2` **3. Store securely** Keep your API key secure and never expose it in client-side code or public repositories. ## Make your first request Once you have your API key, you can start making requests to the Cleanview API. > [!NOTE] > > **Quick test**: Use the **"Try it"** feature in our [API reference](/api-reference/introduction#try-it-out) to test endpoints directly in your browser with your API key. ### Authentication Include your API key in the `x-api-key` header of all requests: ```bash theme={null} curl -H "x-api-key: cv_pub_your_api_key_here" \ https://api.cleanview.co/api/v1/eia-860m ``` ### Basic request examples > **Get EIA 860M data** > > ```bash theme={null} > curl -H "x-api-key: cv_pub_your_api_key_here" \ > "https://api.cleanview.co/api/v1/eia-860m?limit=50" > ``` > > ```python theme={null} > import requests > > headers = {'x-api-key': 'cv_pub_your_api_key_here'} > response = requests.get( > 'https://api.cleanview.co/api/v1/eia-860m?limit=50', > headers=headers > ) > data = response.json() > ``` > **Get interconnection queue data** > > ```bash theme={null} > curl -H "x-api-key: cv_pub_your_api_key_here" \ > "https://api.cleanview.co/api/v1/interconnection/ercot?limit=50" > ``` > > ```python theme={null} > import requests > > headers = {'x-api-key': 'cv_pub_your_api_key_here'} > response = requests.get( > 'https://api.cleanview.co/api/v1/interconnection/ercot?limit=50', > headers=headers > ) > data = response.json() > ``` ### Response format All API responses follow a consistent format: ```json theme={null} { "success": true, "summary": { "limit": 50, "offset": 0, "total_results": 1000, "has_more": true, "current_page": 1, "total_pages": 20 }, "filters": { "state": "CA", "technology": "Solar" }, "customer": { "id": "test_user_001", "name": "Test Developer" }, "data": [...] } ``` ## Next steps > **[Authentication details](/authentication)** > > Learn more about API key authentication and security best practices > **[API reference](/api-reference/introduction)** > > Explore all available endpoints and their parameters > **[EIA 860M data](/api-reference/endpoint/eia-860m)** > > Access the latest EIA project records > **[Interconnection queues](/api-reference/endpoint/ercot)** > > Query real-time interconnection queue data