MonitorPlanCommentDTO

MonitorPlanCommentDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name Type Description
monitoringPlanComment string Comment on a monitoring plan
beginDate string Date and time in which an activity started or ended.
endDate string Last date in which information was effective. This date will be null for active records.
id string Unique identifier of a monitoring plan comment record.
planId string Unique identifier of a monitoring plan 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

cam-monitor-plan-monitor-plan-comment-dto-schema.json Raw ↑
{
  "$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-plan-comment-dto-schema.json",
  "title": "MonitorPlanCommentDTO",
  "description": "MonitorPlanCommentDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "monitoringPlanComment": {
      "type": "string",
      "minLength": 1,
      "maxLength": 4000,
      "description": "Comment on a monitoring plan",
      "example": "DAHS was updated for GT-1 on 11/10/2016 by a previous owner, but the component ID was not updated on the gas system. This was corrected on 9/8/2020."
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date and time in which an activity started or ended.",
      "example": "2020-09-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
    },
    "id": {
      "type": "string",
      "description": "Unique identifier of a monitoring plan comment record.",
      "example": "V-APPWORK--66020554D3C844E78730052AC3808151"
    },
    "planId": {
      "type": "string",
      "description": "Unique identifier of a monitoring plan record.",
      "example": "MDC-2483BA898490441B97B7D7CFB1BE6D9A"
    },
    "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": "2020-10-28"
    },
    "updateDate": {
      "type": "string",
      "description": "Date and time in which record was last updated.",
      "example": "2020-10-28"
    },
    "active": {
      "type": "boolean",
      "description": "Flag for active monitor location record",
      "example": true
    }
  },
  "required": [
    "monitoringPlanComment",
    "beginDate",
    "endDate",
    "id",
    "planId",
    "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-plan-comment-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.