EnergyNetWatch
Menu
API reference

Oil and Gas API Endpoint Coverage

Review the endpoint families EnergyNetWatch exposes for approved API customers and how each family should be interpreted with state, source, and workflow context.

View API pricingPublic coverage notes
State coverage by API family

Coverage is route-specific, not one blanket state list

Some endpoints are global, some accept the core state filter set, and some are intentionally narrower because the source data is state-specific. Use this table before building workflows or describing a customer integration.

API family
Operators
Covered state scope
Global
Status
Global route

Operator search and profile endpoints are available as global routes. Some returned fields depend on state-backed source coverage.

API family
Permits
Covered state scope
TX, NM, CO, CA, UT, WV, WY, AK, PA, NY, ND, OH, LA
Status
Core state filters

Use these state filters for standard permit workflows. Freshness and depth vary by state and source cadence.

API family
Wells and production
Covered state scope
TX, NM, CO, CA, UT, WV, WY, AK, PA, NY, ND, OH, LA
Status
Core state filters

Well lookup, well search, latest production month, and supported production context depend on loaded well and production rows.

API family
Oklahoma
Covered state scope
OK
Status
Limited / verify first

Current automation metadata treats OK as deferred for standard well-level production and permit automation. Use data availability before selling or automating OK workflows.

API family
Texas RRC regulatory data
Covered state scope
TX
Status
TX official-source routes

Operator identity, well-to-lease identity, completion context, inactive status, tests/allowables, UIC profiles and reports, lease search, and official filed lease production are Texas-only. Use general well search/detail first when a low-cost normalized lookup is sufficient.

API family
Physical midstream
Covered state scope
TX, NM
Status
Route-specific

Pipeline GIS and T-4 route evidence are Texas-only. The facilities route contains regulator-derived Texas and New Mexico records and does not imply construction, capacity, ownership, or current operation.

API family
Facility permits
Covered state scope
TX
Status
TX only

The public facility-permits endpoint currently reads Texas facility permit records and rejects non-TX state requests.

API family
Infrastructure operator leads
Covered state scope
TX
Status
TX only

The operator-leads endpoint currently combines Texas drilling permit demand with Texas facility registration evidence.

API family
Source signal routes
Covered state scope
TX, NM
Status
Route-specific

TX PS-48 notices are Texas-only. NM APD signals are New Mexico-only. The TX/NM signal summary combines those route-specific signals.

States not listed for a route family should be treated as not publicly supported for that API workflow unless the data availability endpoint returns usable evidence for the specific company, operator, or county.

Operators
/api/public/operators

Operator search and profile context where operator records are loaded and normalized.

Permits
/api/public/permits

Permit records by supported state, operator, county, search term, date window, and endpoint scope.

Wells
/api/public/wells

Well search and API-number lookup where well records support the requested geography.

Production
/api/public/wells/{api}/production

Supported well-level production history and latest production month metadata.

Facility permits
/api/public/facility-permits

Facility permit records and source caveats where EnergyNetWatch has loaded coverage.

Infrastructure signals
/api/public/infrastructure/operator-leads

Operator-level infrastructure lead context where facility or infrastructure source coverage supports it.

TX PS-48 signals
/api/public/signals/tx/ps48

Texas RRC PS-48 pipeline construction-start notice records with county, operator, timing, mileage, and T-4 status context.

NM APD signals
/api/public/signals/nm/apds

New Mexico APD permit and surface-activity records with county, operator, coordinates, issue dates, and spud context.

TX/NM signal summary
/api/public/reports/tx-nm-signal-summary

Executive summary across TX PS-48, TX large-load leads, NM APDs, NM facilities, and NM midstream gas context.

Data availability
/api/public/data-availability

Grouped evidence checks before running deeper operator, county, or company workflows.

Texas RRC operators
/api/public/regulatory/tx/operators

Search official operator names and organization numbers.

Texas RRC operator detail
/api/public/regulatory/tx/operators/{operatorNo}

Fetch one official operator identity plus latest filed-production context.

Texas RRC operator production
/api/public/regulatory/tx/operators/{operatorNo}/production

Official filed lease-production totals for one Texas RRC operator number.

Texas RRC well identity
/api/public/regulatory/tx/wells/{api}

Official operator number, district, oil/gas class, and lease number resolved from an API number.

Texas official lease production by API10
/api/public/regulatory/tx/wells/{api}/production

Convenience call that resolves the current high-confidence lease identity internally. Multi-well APIs return the same official lease history, not individual-well production.

Texas RRC completion
/api/public/regulatory/tx/wells/{api}/completion

Full Wellbore formation/perforation context plus retained approved W-2/G-1 measured depth and TVD when available.

Texas inactive-well status
/api/public/regulatory/tx/wells/{api}/inactive-status

Latest loaded official IWAR status and factual snapshot transitions; no-longer-listed is not proof of reactivation.

Texas OLTDW status/tests
/api/public/regulatory/tx/wells/{api}/oltdw-status

Only unique high-confidence API matches; test and potential values are not actual individual-well production.

Texas Oil Masters tests/allowables
/api/public/regulatory/tx/wells/{api}/tests-allowables

Only unique high-confidence API matches; allowable and test values are not actual individual-well production.

Texas UIC well search
/api/public/regulatory/tx/uic/wells

Bounded injection/disposal-well lookup requiring an exact UIC control number, API number, or operator number.

Texas UIC well profile
/api/public/regulatory/tx/uic/wells/{uicControlNumber}

Current UIC inventory and permit context keyed by the native nine-digit control number.

Texas UIC monthly reports
/api/public/regulatory/tx/uic/wells/{uicControlNumber}/monthly

H-10 and H-10H records kept separate by report month and report type; public history excludes source months before 1900-01 or after the latest completed source period; values are not hydrocarbon production or real-time telemetry.

Texas RRC leases
/api/public/regulatory/tx/leases

Search official oil/gas lease identities by district, lease, operator, or text.

Texas official lease production
/api/public/regulatory/tx/leases/{oilGasCode}/{districtNo}/{leaseNo}/production

Official filed production at lease grain; multi-well lease totals are not official individual-well volumes.

Texas official production summary
/api/public/regulatory/tx/production/summary

Official filed statewide or district lease-production totals with source-filing context.

Texas pipeline GIS coverage
/api/public/midstream/tx/pipelines/coverage

Loaded county and source coverage for the bounded Texas pipeline GIS route.

Texas pipeline GIS segments
/api/public/midstream/tx/pipelines/segments

Bounded mapped segments with geometry-derived length and source caveats.

Texas T-4 route evidence
/api/public/midstream/tx/t4/{permitNumber}/route

Mapped route evidence for one T-4 permit number; a mapped segment does not prove current operation or ownership.

TX/NM regulator facilities
/api/public/midstream/facilities

Regulator-derived Texas R-3 and New Mexico OCD facility records with route-specific source coverage.

Coverage caveats to preserve

  • Coverage varies by state, source, record type, and load cadence.
  • A valid record can be useful for one workflow and still be inappropriate for another workflow.
  • Production records can lag permits and well records because source reporting calendars differ.
  • Operator labels may differ across state records, filings, and normalized workflows.
  • Infrastructure and facility signals should be reviewed with source caveats before commercial action.
  • PS-48 and APD records are signal records. They should not be described as confirmed completion, in-service, or production evidence.
  • UIC permits and H-10/H-10H reports are regulatory context, not proof of current commercial capacity, connectivity, disposal pricing, remaining pore space, or third-party acceptance.
  • For UIC responses, source and meta.freshness describe the latest completed dataset check; rowProvenance describes when the individual row was introduced or corrected.
  • Downstream systems should retain loaded-through dates, source dates, coverage notes, and request ids.

Operators

Permits

Wells

Official TX regulatory

Texas UIC

Modeled and official production

Physical midstream

TX/NM Signals