Cam Monitor Plan Unit Dto Structure

UnitDTO schema from Monitor Plan Management OpenAPI Specification

Type: object Properties: 18 Required: 8
GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

UnitDTO is a JSON Structure definition published by EPA — U.S. Environmental Protection Agency, describing 18 properties, of which 8 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

nonLoadBasedIndicator id unitid facilityId beginDate endDate sourceCategoryCd commOpDate comrOpDate userId addDate updateDate opStatusCd statusBeginDate unitTypeCd auditUser auditDate active

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-structure/cam-monitor-plan-unit-dto-structure.json",
  "name": "UnitDTO",
  "description": "UnitDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "nonLoadBasedIndicator": {
      "type": "double",
      "description": "Indicator that represents whether the unit is non-load based.",
      "example": "1"
    },
    "id": {
      "type": "double",
      "description": "Unique identifier for the unit.",
      "example": "1001"
    },
    "unitid": {
      "type": "string",
      "description": "ID of the unit.",
      "example": "UNIT_123"
    },
    "facilityId": {
      "type": "double",
      "description": "The Facility ID code assigned by the Department of Energy's Energy Information Administration. The Energy Information Administration Plant ID code is also referred to as the \"ORIS code\", \"ORISPL code\", \"Facility ID\", or \"Facility code\", among other names. If a Plant ID code has not been assigned by the Department of Energy's Energy Information Administration, then plant code means a code beginning with \"88\" assigned by the EPA's Clean Air Markets Division for electronic reporting.",
      "example": 3
    },
    "beginDate": {
      "type": "datetime",
      "description": "Date on which information became effective or activity started.",
      "example": "2018-05-01"
    },
    "endDate": {
      "type": "datetime",
      "description": "Last date in which information was effective.  This date will be null for active records.",
      "example": null
    },
    "sourceCategoryCd": {
      "type": "string",
      "description": "Category code for the source of the unit.",
      "example": "SRC123"
    },
    "commOpDate": {
      "type": "string",
      "description": "The date when the unit began commercial operation.",
      "example": "01/01/2020"
    },
    "comrOpDate": {
      "type": "string",
      "description": "The date when the unit began compliance operation.",
      "example": "01/01/2020"
    },
    "userId": {
      "type": "string",
      "description": "The ID of the user who created or updated the record.",
      "example": "jdoe"
    },
    "addDate": {
      "type": "string",
      "description": "The date when the unit record was added.",
      "example": "2024-08-29"
    },
    "updateDate": {
      "type": "string",
      "description": "The date when the unit record was last updated.",
      "example": "2024-08-30"
    },
    "opStatusCd": {
      "type": "string",
      "description": "The operational status code of the unit.",
      "example": "OP"
    },
    "statusBeginDate": {
      "type": "string",
      "description": "The date when the current operational status of the unit began.",
      "example": "01/01/2020"
    },
    "unitTypeCd": {
      "type": "string",
      "description": "The type code of the unit.",
      "example": "UBT"
    },
    "auditUser": {
      "type": "string",
      "description": "The user ID of the person who performed the last audit on the unit record.",
      "example": "user@example.com"
    },
    "auditDate": {
      "type": "string",
      "description": "The date and time when the last audit was performed on the unit record.",
      "example": "2023-01-01T00:00:00Z"
    },
    "active": {
      "type": "boolean",
      "description": "Indicates whether the unit is currently active.",
      "example": true
    }
  },
  "required": [
    "nonLoadBasedIndicator",
    "id",
    "unitid",
    "facilityId",
    "beginDate",
    "endDate",
    "userId",
    "addDate"
  ]
}

Work with this as data

Every JSON Structure here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Structure
curl "https://apis.io/api/v1/json-structures/cam-monitor-plan-unit-dto-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.