UnitControlDTO
UnitControlDTO schema from Monitor Plan Management OpenAPI Specification
GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions
Properties
| Name | Type | Description |
|---|---|---|
| controlCode | string | Codes used to identify the type of control equipment. |
| originalCode | string | Code used to identify that the control equipment was installed and operational as part of the original unit design. |
| installDate | string | Approximate date the original control equipment was or will be installed. |
| optimizationDate | string | The approximate date on which optimization of control equipment was completed and the equipment made fully operational if the control equipment was not part of the original installation. |
| seasonalControlsIndicator | string | Code used to identify if the NOx control equipment was used during the ozone season. |
| retireDate | string | Date control equipment was retired. This value will be null for active records. |
| id | string | Unique identifier of a unit control record. |
| unitId | number | Unique identifier of a unit record. |
| userId | string | User account or source of data that added or updated record. |
| addDate | string | Date and time in which record was added. |
| updateDate | string | Date and time in which record was last updated. |
| active | boolean | Flag for active monitor location record |
| parameterCode | string |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-schema/cam-monitor-plan-unit-control-dto-schema.json",
"title": "UnitControlDTO",
"description": "UnitControlDTO schema from Monitor Plan Management OpenAPI Specification",
"type": "object",
"properties": {
"controlCode": {
"type": "string",
"description": "Codes used to identify the type of control equipment.",
"example": "SNCR"
},
"originalCode": {
"type": "string",
"description": "Code used to identify that the control equipment was installed and operational as part of the original unit design.",
"example": "0"
},
"installDate": {
"format": "date-time",
"type": "string",
"description": "Approximate date the original control equipment was or will be installed.",
"example": "2005-01-01"
},
"optimizationDate": {
"format": "date-time",
"type": "string",
"description": "The approximate date on which optimization of control equipment was completed and the equipment made fully operational if the control equipment was not part of the original installation.",
"example": "2006-06-01"
},
"seasonalControlsIndicator": {
"type": "string",
"description": "Code used to identify if the NOx control equipment was used during the ozone season.",
"example": "0"
},
"retireDate": {
"format": "date-time",
"type": "string",
"description": "Date control equipment was retired. This value will be null for active records.",
"example": null
},
"id": {
"type": "string",
"description": "Unique identifier of a unit control record.",
"example": "618"
},
"unitId": {
"type": "number",
"description": "Unique identifier of a unit record.",
"example": "734"
},
"userId": {
"type": "string",
"description": "User account or source of data that added or updated record.",
"example": "abcde"
},
"addDate": {
"type": "string",
"description": "Date and time in which record was added.",
"example": "2009-02-20"
},
"updateDate": {
"type": "string",
"description": "Date and time in which record was last updated.",
"example": "2009-02-20"
},
"active": {
"type": "boolean",
"description": "Flag for active monitor location record",
"example": true
},
"parameterCode": {
"type": "string",
"example": "string"
}
},
"required": [
"controlCode",
"originalCode",
"installDate",
"optimizationDate",
"seasonalControlsIndicator",
"retireDate",
"id",
"unitId",
"userId",
"addDate",
"updateDate",
"active",
"parameterCode"
]
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema 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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cam-monitor-plan-unit-control-dto"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.