PCTQualificationDTO

PCTQualificationDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name Type Description
qualificationYear number The calendar year during which activity occurred.
averagePercentValue number The average percent capacity or heat input usage.
yr1QualificationDataYear number The first year corresponding to the qualification data.
yr1QualificationDataTypeCode string Code used to identify the type qualification in the first year.
yr1PercentageValue number The percent capacity or heat input usage in the first year.
yr2QualificationDataYear number The second year corresponding to the qualification data.
yr2QualificationDataTypeCode string Code used to identify the type qualification in the second year.
yr2PercentageValue number The percent capacity or heat input usage in the second year.
yr3QualificationDataYear number The third year corresponding to the qualification data.
yr3QualificationDataTypeCode string Code used to indicate type of data for year (actual or projected) used to determine peaking or gas-fired qualification.
yr3PercentageValue number The percent capacity or heat input usage in the third year.
id string Unique identifier of a monitoring qualification percentage record.
qualificationId string Unique identifier of a monitoring qualification 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.
View JSON Schema on GitHub

JSON Schema

cam-monitor-plan-pctqualification-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-pctqualification-dto-schema.json",
  "title": "PCTQualificationDTO",
  "description": "PCTQualificationDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "qualificationYear": {
      "type": "number",
      "description": "The calendar year during which activity occurred.",
      "example": 2020
    },
    "averagePercentValue": {
      "type": "number",
      "description": "The average percent capacity or heat input usage.",
      "example": 100
    },
    "yr1QualificationDataYear": {
      "type": "number",
      "description": "The first year corresponding to the qualification data.",
      "example": 2018
    },
    "yr1QualificationDataTypeCode": {
      "type": "string",
      "description": "Code used to identify the type qualification in the first year.",
      "example": "A"
    },
    "yr1PercentageValue": {
      "type": "number",
      "description": "The percent capacity or heat input usage in the first year.",
      "example": 100
    },
    "yr2QualificationDataYear": {
      "type": "number",
      "description": "The second year corresponding to the qualification data.",
      "example": 2019
    },
    "yr2QualificationDataTypeCode": {
      "type": "string",
      "description": "Code used to identify the type qualification in the second year.",
      "example": "A"
    },
    "yr2PercentageValue": {
      "type": "number",
      "description": "The percent capacity or heat input usage in the second year.",
      "example": 100
    },
    "yr3QualificationDataYear": {
      "type": "number",
      "description": "The third year corresponding to the qualification data.",
      "example": 2020
    },
    "yr3QualificationDataTypeCode": {
      "type": "string",
      "description": "Code used to indicate type of data for year (actual or projected) used to determine peaking or gas-fired qualification.",
      "example": "A"
    },
    "yr3PercentageValue": {
      "type": "number",
      "description": "The percent capacity or heat input usage in the third year.",
      "example": 100
    },
    "id": {
      "type": "string",
      "description": "Unique identifier of a monitoring qualification percentage record.",
      "example": "02227-BSGR-56EB0D4D400642A4860D6402698BBE16"
    },
    "qualificationId": {
      "type": "string",
      "description": "Unique identifier of a monitoring qualification record.",
      "example": "02022-614W-608B84AEDB8148C7B3935EE935AB835F"
    },
    "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": "2021-04-01"
    },
    "updateDate": {
      "type": "string",
      "description": "Date and time in which record was last updated.",
      "example": "2021-04-01"
    }
  },
  "required": [
    "qualificationYear",
    "averagePercentValue",
    "yr1QualificationDataYear",
    "yr1QualificationDataTypeCode",
    "yr1PercentageValue",
    "yr2QualificationDataYear",
    "yr2QualificationDataTypeCode",
    "yr2PercentageValue",
    "yr3QualificationDataYear",
    "yr3QualificationDataTypeCode",
    "yr3PercentageValue",
    "id",
    "qualificationId",
    "userId",
    "addDate",
    "updateDate"
  ]
}

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