Navigation menu

Department of Public Service

The NYS Code Rule 753 Enforcement Request Management API provides secure, authenticated access to submission, retrieval, and status-tracking services for consumer protection enforcement requests. Query historical records, fetch individual request details, monitor enforcement status, and submit new requests with supporting documentation. All endpoints require Bearer token authentication and are restricted to authorized users and organizations operating under NYS Code Rule 753 (Protection of Underground Facilities).

Browse APIs

Showing 0 matching API(s)

This API guides users through the process of creating and submitting a new Enforcement Request under NYS Code Rule 753. It allows for the inclusion of structured metadata and optional file attachments, ensuring all necessary information and supporting documentation are provided.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request
POST Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Request Body Example

multipart/form-data
enforcementRequestObject Required string
{ "CreatedBy": "abc@example.com", "SubmitterEntityName": "XYZ Test - 1", "SubmitterStreetAddress": "123 Submitter Address", "SubmitterCity": "Submitter City", "SubmitterState": "Submitter State", "SubmitterZipcode": "12345", "SubmitterContactFName": "Contact First Name", "SubmitterContactMName": "Contact Middle Name", "SubmitterContactLName": "Contact Last Name", "SubmitterContactEmail": "submitteremail@example.com", "SubmitterContactPhone": null, "AllegedEntityName": "XYZ Test - 1", "AllegedEntityStreetAddress": "123 Alleged Address", "AllegedEntityCity": "Alleged City", "AllegedEntityState": "Alleged State", "AllegedEntityZipcode": "12345", "AllegedEntityContactFName": "Alleged First Name", "AllegedEntityContactMName": "Alleged Middle Name", "AllegedEntityContactLName": "Alleged Last Name", "AllegedEntityContactEmail": "allegedemail@example.com", "AllegedEntityContactPhone": null, "DateOfViolation": "2026-01-01", "ViolationCounty": "Violation County", "ServiceTerritory": "XYZ Test - 1", "ViolationLocationLat": 1, "ViolationLocationLong": 1, "ViolationLocationStreet": null, "ViolationLocationCity": null, "ViolationLocationState": null, "ViolationLocationZipcode": null, "WasExcavationOccurring": "1", "ExcavationMethod": "Dredger", "ExcavationMethodOther": null, "ExcavatorType": "Private", "ProjectDescription": null, "OneCallTicketNumber": null, "RegulationCodes": "753-3.5, 753-4.2", "ImpactedFacilities": [ { "IndustryType": "Gas", "IsDamaged": "1", "Diameter": "0.5", "LineTypeDescription": "Distribution", "IsHighPressure": "1", "IsLowPressure": null, "IsPsig": "1", "LineValue": "15.7", "LineMaterialOther": "Impacted Facility Description", "Description": "Impacted Facility Description", "InstallationType": null, "ConductorType": null, "CircuitCount": 0, "Depth": null, "ConductorSize": null, "IsBlowingGas": "1", "Duration": "0.5", "GasLoss": "3800", "LineMaterial": null, "IsExcessFlowValve": null, "BleedByRate": null } ], "Attachments": [ { "DocumentType": "Orders", "AttachmentTitle": "first", "AttachmentExtn": "doc", "FileName": "01_first.doc", "Sno": 1 } ] }
JSON string representing the enforcement request object
files File
File Upload: Select one or more files.
e.g., document1.pdf, image.jpg
One or more files to attach (e.g., PDF, DOCX, TXT)
One or more files to attach (e.g., PDF, DOCX, TXT)

Request Body Parameters

Parameter Type Default Description
enforcementRequestObject required
string (JSON) - A valid JSON string representing the enforcement request payload. This object contains all the structured details for the enforcement request, including:Submitter and alleged entity details, Violation information, Impacted facilities, Metadata for any associated attachments, and other relevant request data.
Example: { "CreatedBy": "createdby@example.com", "SubmitterEntityName": "National Fuel Gas Distribution Corporation ", ... }
files
file (binary) - One or more files to attach (e.g., evidence documents, photos, reports). Each file must be uploaded as a separate files form field. File names and types are inferred from the multipart boundary.
Example: 01_first.doc (Content-Type: application/msword)

Response Example

Status: 200 application/json 
{
  "data": {
    "enforcementRequestNumber": "26-0252",
    "submitterEntityName": "XYZ Test - 1",
    "submitterStreetAddress": "123 Submitter Address",
    "submitterCity": "Submitter City",
    "submitterState": "Submitter State",
    "submitterZipcode": "12345",
    "submitterContactFName": "Contact First Name",
    "submitterContactMName": "Contact Middle Name",
    "submitterContactLName": "Contact Last Name",
    "submitterContactEmail": "submitteremail@example.com",
    "submitterContactPhone": null,
    "allegedEntityName": "XYZ Test - 1",
    "allegedEntityStreetAddress": "123 Alleged Address",
    "allegedEntityCity": "Alleged City",
    "allegedEntityState": "Alleged State",
    "allegedEntityZipcode": "12345",
    "allegedEntityContactFName": "Alleged First Name",
    "allegedEntityContactMName": "Alleged Middle Name",
    "allegedEntityContactLName": "Alleged Last Name",
    "allegedEntityContactEmail": "allegedemail@example.com",
    "allegedEntityContactPhone": null,
    "dateOfViolation": "2026-01-01T00:00:00",
    "violationCounty": "ALBANY",
    "serviceTerritory": "XYZ Test - 1",
    "violationLocationLat": 1,
    "violationLocationLong": 1,
    "violationLocationStreet": null,
    "violationLocationCity": null,
    "violationLocationState": null,
    "violationLocationZipcode": null,
    "wasExcavationOccurring": "1",
    "excavationMethod": "Dredger",
    "excavationMethodOther": null,
    "excavatorType": "Private",
    "excavatorTypeOther": null,
    "projectDescription": null,
    "oneCallTicketNumber": null,
    "regulationCodes": "753-3.5, 753-4.2",
    "impactedFacilities": [
      {
        "enforcementRequestNumber": "26-0252",
        "industryType": "Gas",
        "isDamaged": "1",
        "diameter": "0.5",
        "lineValue": "15.7",
        "lineTypeDescription": "Distribution",
        "isHighPressure": "1",
        "isLowPressure": null,
        "isPsig": "1",
        "lineMaterial": null,
        "lineMaterialOther": "Impacted Facility Description",
        "description": "Impacted Facility Description",
        "installationType": null,
        "conductorType": null,
        "circuitCount": 0,
        "depth": null,
        "conductorSize": null,
        "isBlowingGas": "1",
        "duration": "0.5",
        "gasLoss": "3800.00",
        "isExcessFlowValve": null,
        "bleedByRate": null
      }
    ],
    "attachments": [
      {
        "sno": 1,
        "enforcementRequestNumber": "26-0252",
        "attachmentSeq": 650,
        "documentType": "Orders",
        "attachmentRefNo": "fa443124-bd19-4de8-80fa-5065a1e3c838",
        "attachmentTitle": "first",
        "attachmentExtn": "doc",
        "attachmentSize": 100352,
        "fileName": "01_first.doc"
      }
    ]
  },
  "error": null,
  "errorMessage": null,
  "errors": null
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request

This API guides users through the process of updating an existing Enforcement Request under NYS Code Rule 753. It allows for the modification of structured metadata and the inclusion of optional file attachments, ensuring all necessary information and supporting documentation are up-to-date.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/revise
PUT Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Request Body Parameters

Parameter Type Default Description
enforcementRequestObject required
string (JSON) - A valid JSON string representing the full enforcement request payload. This includes the enforcementRequestNumber, submitter/alleged entity details, violation information, impacted facilities, attachments metadata, etc. The JSON must be stringified (i.e., double-quoted JSON embedded within a string), not provided as raw JSON.
Example: { "enforcementRequestNumber": "26-0056", "submitterEntityName": "Consolidated Edison... ", ... }
files required
file (binary) - One or more files to attach or replace (e.g., updated orders, evidence, reports). Each file must be uploaded as a separate files form field.
Example: 01_first.doc (Content-Type: application/msword) 10mb.pdf (Content-Type: application/pdf)

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/revise

This API retrieves a specific Enforcement Request using its unique enforcement number. Access is secured via Bearer token authentication, and the enforcement number is provided as a query parameter in the URL.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/{enforcementNumber}
GET Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Query Parameters

Parameter Type Default Description
enforcementNumber required
string - The unique enforcement request identifier (e.g., 26-0080). This identifier is required to retrieve the record.
Example: 26-0080

Response Example

Status: 200 application/json 
{
  "data": [
    {
      "enforcementRequestNumber": "26-0001",
      "submitterEntityName": "XYZ Test - 2",
      "submitterStreetAddress": "",
      "submitterStreetAddress": "59-17 Junction Boulevard",
      "submitterCity": "Elmhurst",
      "submitterState": "New York",
      "submitterZipcode": "11373",
      "submitterContactFName": "Dushyant",
      "submitterContactMName": null,
      "submitterContactLName": "Thakar",
      "submitterContactEmail": "dmmuser01@dev.dps.ny.gov",
      "submitterContactPhone": "973-223-3597",
      "allegedEntityName": "Village of Endicott",
      "allegedEntityStreetAddress": "1009 East Main Street",
      "allegedEntityCity": "Endicott",
      "allegedEntityState": "NY",
      "allegedEntityZipcode": "13760",
      "allegedEntityContactFName": "Dushyant",
      "allegedEntityContactMName": "V",
      "allegedEntityContactLName": "Thakar",
      "allegedEntityContactEmail": "xyz@dev.dps.ny.gov",
      "allegedEntityContactPhone": "973-223-3597",
      "dateOfViolation": "2026-02-19T00:00:00",
      "violationCounty": "ALBANY",
      "serviceTerritory": "Central Hudson Gas & Electric Corporation",
      "violationLocationLat": 46,
      "violationLocationLong": 46,
      "violationLocationStreet": "1706 Infamous Graphics LTD",
      "violationLocationCity": "Albany",
      "violationLocationState": "NY",
      "violationLocationZipcode": "13340",
      "wasExcavationOccurring": "1",
      "excavationMethod": "Other",
      "excavationMethodOther": "DVT Testing Custom Website 01/14",
      "excavatorType": "Contractor",
      "excavatorTypeOther": null,
      "projectDescription": "DVT Testing Custom Website 11/26",
      "oneCallTicketNumber": "12345-123-789",
      "regulationCodes": "753-2.1, 753-3.5, 753-5.3(c), 753-3.8, 753-3.14",
      "impactedFacilities": [
            {
                "enforcementRequestNumber": "26-0080",
                "industryType": "Gas",
                "isDamaged": "1",
                "diameter": "0.5",
                "lineValue": "15.7",
                "lineTypeDescription": null,
                "isHighPressure": "1",
                "isLowPressure": null,
                "isPsig": "1",
                "lineMaterial": "",
                "lineMaterialOther": "Impacted Facility Description",
                "description": "Impacted Facility Description",
                "installationType": null,
                "conductorType": null,
                "circuitCount": 0,
                "depth": null,
                "conductorSize": null,
                "isBlowingGas": "1",
                "duration": "0.5",
                "gasLoss": "3800.00",
                "isExcessFlowValve": null,
                "bleedByRate": null
            }
        ],
        "attachments": [
            {
                "sno": 1,
                "enforcementRequestNumber": "26-0080",
                "attachmentSeq": 462,
                "documentType": "Orders",
                "attachmentRefNo": "{4020779C-0000-C612-BEC8-B134402C4C29}",
                "attachmentTitle": "10mb",
                "attachmentExtn": "pdf",
                "attachmentSize": 10490314,
                "fileName": "10mb.pdf"
            }
        ]
    }
  ]
"error": null,
"errorMessage": null,
"errors": null
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/-54

This API retrieves the current status of a specific Enforcement Request using its unique enforcement number. Access is secured via Bearer token authentication, with the enforcement number provided as a query parameter in the URL.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/{enforcementNumber}/status
GET Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Query Parameters

Parameter Type Default Description
enforcementNumber required
string - The unique enforcement request identifier (e.g., 26-0080). This identifier is required to retrieve the status.
Example: 26-0080

Response Example

Status: 200 application/json 
{
  "data": [
    {
      "enforcementRequestNumber": "26-0001",
      "status": "Pending Review",
      "submitterEntityName": "XYZ Test - 2",
      "citation": "26-0001-01",
      "createdDate": "2026-01-01",
      "rejectReason": null,
      "violationDate": "2025-12-01",
      "matterCases": [
        {
          "matterNumber": "26-00001",
          "caseNumber": "26-m-0001"
        }
      ]
    }
  ]
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-request/-54/status

This API retrieves all consumer Enforcement Requests submitted under NYS Code Rule 753 (Protection of Underground Facilities). Access is secured via Bearer token authentication only.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests
GET Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Response Example

Status: 200 application/json 
{
  "data": [
    {
      "enforcementRequestNumber": "26-0001",
      "status": "Pending Review",
      "submitterEntityName": "XYZ Test - 2",
      "citation": "26-0001-01",
      "createdDate": "2026-01-01",
      "rejectReason": null,
      "violationDate": "2025-12-01",
      "matterCases": [
        {
          "matterNumber": "26-00001",
          "caseNumber": "26-m-0001"
        }
      ]
    }
  ]
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests

This API searches for consumer Enforcement Requests submitted under NYS Code Rule 753 within a specified Created Date range. It returns all matching records from the start date to the end date, inclusive, and supports searches spanning multiple years. Access is secured via Bearer token authentication, with the date range provided in the request body as JSON.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests/search
POST Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Request Body Example

application/json 
{
  "fromDate": "2026-02-01",
  "toDate": "2026-02-26"
}

Request Body Parameters

Parameter Type Default Description
fromDate required
date-only - Start date for the search range. Format: YYYY-MM-DD. Must be valid calendar date and not later than toDate.
Example: 2024-01-01
toDate required
date-only - End date of the search range (inclusive). Format: YYYY-MM-DD. Must be a valid calendar date and not earlier than fromDate. Can span multiple years (e.g., from 2020-01-01 to 2026-12-31).
Example: 2026-02-26

Response Example

Status: 200 application/json 
{
  "data": [
    {
      "enforcementRequestNumber": "26-0001",
      "status": "Pending Review",
      "submitterEntityName": "XYZ Test - 2",
      "citation": "26-0001-01",
      "createdDate": "2026-01-01",
      "rejectReason": null,
      "violationDate": "2025-12-01",
      "matterCases": [
        {
          "matterNumber": "26-00001",
          "caseNumber": "26-m-0001"
        }
      ]
    }
  ]
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests/search

This API searches for consumer Enforcement Requests submitted under NYS Code Rule 753 within a specified Violation Date range. It returns all matching records from the start date to the end date, inclusive, and supports searches spanning multiple years. Access is secured via Bearer token authentication, with the date range provided in the request body as JSON.

HTTP Request

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests-search-by-violation-date
POST Requires Bearer Token authentication

Headers

Name Type Required Description & Example
Authorization string Yes

Bearer token required for authentication. Format: Bearer <your-access-token>

Example: Bearer abc123xyz

Request Body Example

application/json 
{
  "fromDate": "2026-02-01",
  "toDate": "2026-02-26"
}

Request Body Parameters

Parameter Type Default Description
fromDate required
date-only - Start date for the search range (inclusive). Format: YYYY-MM-DD. Must be a valid calendar date and not later than 'toDate'.
Example: 2026-02-01
toDate required
date-only - End date of the search range (inclusive). Format: YYYY-MM-DD. Must be a valid calendar date and not earlier than 'fromDate'. Can span multiple years (e.g., from 2020-01-01 to 2026-12-31).
Example: 2026-02-26

Response Example

Status: 200 application/json 
{
  "data": [
    {
      "enforcementRequestNumber": "26-0001",
      "status": "Pending Review",
      "submitterEntityName": "XYZ Test - 2",
      "citation": "26-0001-01",
      "createdDate": "2026-01-01",
      "rejectReason": null,
      "violationDate": "2026-02-15",
      "matterCases": [
        {
          "matterNumber": "26-00001",
          "caseNumber": "26-m-0001"
        }
      ]
    }
  ]
}

Example Query

https://api.ny.gov/753Enforcement1.0/api/v1/EnforcementRequest/enforcement-requests-search-by-violation-date

📄 Hard copy of the API documentation?
Download API Documentation