EPA — U.S. Environmental Protection Agency · Schema

MonitorSystemDTO

MonitorSystemDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name	Type	Description
monitoringSystemId	string	The three digit code used by the source to identify the monitoring system.
systemTypeCode	string	Code used to identify the type (parameter) of the system.
systemDesignationCode	string	Code used to indicate designation of monitoring system as primary, backup etc.
fuelCode	string	Code used to identify the type of fuel.
beginDate	string	Date on which information became effective or activity started.
endDate	string	Last date in which information was effective. This date will be null for active records.
beginHour	number	Hour in which information became effective or activity started.
endHour	number	Last hour in which information was effective. This value will be null for active records.
id	string	Unique identifier of a monitoring system record.
locationId	string	Unique identifier of a monitoring location 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
monitoringSystemComponentData	array
monitoringSystemFuelFlowData	array

View JSON Schema on GitHub

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-monitor-system-dto-schema.json",
  "title": "MonitorSystemDTO",
  "description": "MonitorSystemDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "monitoringSystemId": {
      "type": "string",
      "description": "The three digit code used by the source to identify the monitoring system.",
      "example": "C42"
    },
    "systemTypeCode": {
      "type": "string",
      "description": "Code used to identify the type (parameter) of the system.",
      "example": "FLOW"
    },
    "systemDesignationCode": {
      "type": "string",
      "description": "Code used to indicate designation of monitoring system as primary, backup etc.",
      "example": "P"
    },
    "fuelCode": {
      "type": "string",
      "description": "Code used to identify the type of fuel.",
      "example": "NFS"
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which information became effective or activity started.",
      "example": "2007-11-28"
    },
    "endDate": {
      "format": "date-time",
      "type": "string",
      "description": "Last date in which information was effective.  This date will be null for active records.",
      "example": null
    },
    "beginHour": {
      "type": "number",
      "description": "Hour in which information became effective or activity started.",
      "example": 17
    },
    "endHour": {
      "type": "number",
      "description": "Last hour in which information was effective.  This value will be null for active records.",
      "example": null
    },
    "id": {
      "type": "string",
      "description": "Unique identifier of a monitoring system record.",
      "example": "CAMD-4B0DC37051224A7AA9D8CA1E5BE6B4D4"
    },
    "locationId": {
      "type": "string",
      "description": "Unique identifier of a monitoring location record.",
      "example": "5770"
    },
    "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
    },
    "monitoringSystemComponentData": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/SystemComponentDTO"
      },
      "example": [
        "string"
      ]
    },
    "monitoringSystemFuelFlowData": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/SystemFuelFlowDTO"
      },
      "example": [
        "string"
      ]
    }
  },
  "required": [
    "monitoringSystemId",
    "systemTypeCode",
    "systemDesignationCode",
    "fuelCode",
    "beginDate",
    "endDate",
    "beginHour",
    "endHour",
    "id",
    "locationId",
    "userId",
    "addDate",
    "updateDate",
    "active",
    "monitoringSystemComponentData",
    "monitoringSystemFuelFlowData"
  ]
}

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.

All 92 tools →

Call it yourself

curl for this page

This JSON Schema

curl "https://apis.io/api/v1/json-schemas/cam-monitor-plan-monitor-system-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.

GitHub Google LinkedIn

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