EPA — U.S. Environmental Protection Agency · Schema

MonitorMethodDTO

MonitorMethodDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name	Type	Description
parameterCode	string	Code used to identify the parameter.
monitoringMethodCode	string	Code used to identify the monitoring methodology.
substituteDataCode	string	Code used to identify the substitute data approach type.
bypassApproachCode	string	Code used to identify the value to be used for an unmonitored bypass stack.
beginDate	string	Date on which information became effective or activity started.
beginHour	number	Hour in which information became effective.
endDate	string	Last date in which information was effective. This date will be null for active records.
endHour	number	Last hour in which information was effective. This value will be null for active records.
id	string	Unique identifier of a monitoring method 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

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-method-dto-schema.json",
  "title": "MonitorMethodDTO",
  "description": "MonitorMethodDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "parameterCode": {
      "type": "string",
      "description": "Code used to identify the parameter.",
      "example": "SO2"
    },
    "monitoringMethodCode": {
      "type": "string",
      "description": "Code used to identify the monitoring methodology.",
      "example": "CEM"
    },
    "substituteDataCode": {
      "type": "string",
      "description": "Code used to identify the substitute data approach type.",
      "example": "SPTS"
    },
    "bypassApproachCode": {
      "type": "string",
      "description": "Code used to identify the value to be used for an unmonitored bypass stack.",
      "example": "BYMAX"
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which information became effective or activity started.",
      "example": "2007-11-27"
    },
    "beginHour": {
      "type": "number",
      "description": "Hour in which information became effective.",
      "example": 17
    },
    "endDate": {
      "format": "date-time",
      "type": "string",
      "description": "Last date in which information was effective.  This date will be null for active records.",
      "example": null
    },
    "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 method record.",
      "example": "MELISSAMAT-7BA7D94FDB4F4D4A8E1161E4B46150F6"
    },
    "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
    }
  },
  "required": [
    "parameterCode",
    "monitoringMethodCode",
    "substituteDataCode",
    "bypassApproachCode",
    "beginDate",
    "beginHour",
    "endDate",
    "endHour",
    "id",
    "locationId",
    "userId",
    "addDate",
    "updateDate",
    "active"
  ]
}

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-method-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.