> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cleanview.co/llms.txt
> Use this file to discover all available pages before exploring further.

# 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/demo) to add it.
</Note>

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

<AccordionGroup>
  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Response Schema

<ResponseExample>
  ```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"
      }
    ]
  }
  ```
</ResponseExample>

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


## OpenAPI

````yaml GET /gas-plant-units
openapi: 3.0.0
info:
  title: Cleanview Public API
  version: 0.1.0
  description: >-
    RESTful API for tracking data centers and power projects, including
    Cleanview's data center database, EIA records, and ISO interconnection queue
    data
  contact:
    name: Cleanview Energy
    url: https://cleanview.co/demo
servers:
  - url: https://api.cleanview.co/api/v1
    description: Production server
security:
  - ApiKeyAuth: []
paths:
  /gas-plant-units:
    get:
      tags:
        - BTM Gas Plants
      summary: Get all units at behind-the-meter gas plants
      description: >-
        Returns every unit at the plants in /gas-plants as a single JSON
        response: one record per equipment model (and stage) at a plant, with
        the plant's developer and location repeated so the table stands on its
        own. Canceled units are included with status Canceled. This is a
        download link style endpoint with no pagination. Requires the gas-plants
        scope.
      parameters: []
      responses:
        '200':
          description: Successful response with all gas plant units
          content:
            application/json:
              schema:
                type: object
                required:
                  - success
                  - metadata
                  - customer
                  - data
                properties:
                  success:
                    type: boolean
                    description: Always true for successful responses
                    example: true
                  metadata:
                    type: object
                    properties:
                      total_count:
                        type: integer
                        description: Total number of records
                        example: 209
                      generated_at:
                        type: string
                        format: date-time
                        description: Timestamp when the response was generated
                        example: '2026-10-15T16:00:00.000Z'
                  customer:
                    type: object
                    description: Customer information for the API key
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/GasPlantUnit'
                    description: Array of all gas plant units
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: The API key doesn't include the gas-plants scope
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    GasPlantUnit:
      type: object
      description: >-
        One equipment model (and stage) at a behind-the-meter gas plant: its
        count, rated version, nameplate capacity, status and year, with the
        plant's developer and location repeated
      properties:
        id:
          type: integer
          description: Unique identifier for the unit
        plant_id:
          type: integer
          description: The plant, as `id` in Gas Plants
        plant_name:
          type: string
          description: Name of the plant
        developer:
          type: string
          nullable: true
          description: Company that builds and owns the plant
        campus_id:
          type: integer
          nullable: true
          description: >-
            The data center campus the plant powers, as `id` in Data Center
            Campuses
        county:
          type: string
          nullable: true
          description: County where the plant's generation equipment is
        state:
          type: string
          nullable: true
          pattern: ^[A-Z]{2}$
          description: Two-letter state code
        latitude:
          type: number
          nullable: true
          description: >-
            Latitude of the plant's generation equipment, not the data center
            campus
        longitude:
          type: number
          nullable: true
          description: >-
            Longitude of the plant's generation equipment, not the data center
            campus
        oem:
          type: string
          nullable: true
          description: Equipment manufacturer, like Siemens Energy or Caterpillar
        model:
          type: string
          nullable: true
          description: >-
            Model as the manufacturer sells it, like SGT-800. `null` when a
            document names only the manufacturer
        model_family:
          type: string
          nullable: true
          description: >-
            The machine the model is built on: GE's TM2500 and LM2500XPRESS are
            both LM2500
        version:
          type: string
          nullable: true
          description: The model's rated version, when a document identifies it
        equipment_type:
          type: string
          nullable: true
          enum:
            - Gas turbine
            - Steam turbine
            - Reciprocating engine
            - Fuel cell
            - null
          description: >-
            Kind of machine: `Gas turbine`, `Steam turbine`, `Reciprocating
            engine` or `Fuel cell`
        configuration:
          type: string
          nullable: true
          enum:
            - simple_cycle
            - combined_cycle
            - steam_turbine
            - reciprocating_engine
            - fuel_cell
            - null
          description: >-
            How it generates: `simple_cycle`, `combined_cycle`, `steam_turbine`,
            `reciprocating_engine` or `fuel_cell` (see Configuration)
        unit_count:
          type: integer
          nullable: true
          description: Number of machines in the unit
        iso_rating_mw:
          type: number
          nullable: true
          description: >-
            One machine's rating from the manufacturer's data sheet, at standard
            conditions (MW). `null` when the version isn't known
        nameplate_capacity_mw:
          type: number
          nullable: true
          description: Nameplate capacity of all the unit's machines together (MW)
        capacity_basis:
          type: string
          nullable: true
          enum:
            - rating
            - stated
            - estimate
            - null
          description: >-
            Where the capacity comes from: `rating`, `stated` or `estimate` (see
            Capacity)
        status:
          type: string
          enum:
            - Announced
            - Permitted
            - Under Construction
            - Operating
            - Canceled
          description: >-
            `Announced`, `Permitted`, `Under Construction`, `Operating` or
            `Canceled` (see Status)
        operating_year:
          type: integer
          nullable: true
          description: >-
            Year the unit began generating, or Cleanview's estimate of when it
            will
        source_1:
          type: string
          nullable: true
          format: uri
          description: Cleanview's archived copy of a document behind the record
        source_2:
          type: string
          nullable: true
          format: uri
          description: Cleanview's archived copy of a document behind the record
        source_3:
          type: string
          nullable: true
          format: uri
          description: Cleanview's archived copy of a document behind the record
      example:
        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
    Error:
      type: object
      description: Standardized error response structure
      required:
        - error
        - message
      properties:
        error:
          type: string
          description: Error code identifier for programmatic handling
          enum:
            - INVALID_API_KEY
            - API_KEY_NOT_FOUND
            - INVALID_LIMIT
            - INVALID_OFFSET
            - INVALID_STATUS
            - INVALID_CAPACITY
            - INVALID_TECHNOLOGY
            - INVALID_STATES
            - INVALID_DATE
            - INVALID_DATE_RANGE
            - INVALID_BOOLEAN
            - DATABASE_ERROR
            - INTERNAL_ERROR
          example: INVALID_LIMIT
        message:
          type: string
          description: Human-readable error description
          example: Limit must be at least 50 records per request
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: API key authentication using x-api-key header

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.