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.
Record family
Representative endpoint
Coverage read
Operators
/api/public/operatorsOperator search and profile context where operator records are loaded and normalized.
Permits
/api/public/permitsPermit records by supported state, operator, county, search term, date window, and endpoint scope.
Wells
/api/public/wellsWell search and API-number lookup where well records support the requested geography.
Production
/api/public/wells/{api}/productionSupported well-level production history and latest production month metadata.
Facility permits
/api/public/facility-permitsFacility permit records and source caveats where EnergyNetWatch has loaded coverage.
Infrastructure signals
/api/public/infrastructure/operator-leadsOperator-level infrastructure lead context where facility or infrastructure source coverage supports it.
Data availability
/api/public/data-availabilityGrouped evidence checks before running deeper operator, county, or company workflows.
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.
- Downstream systems should retain loaded-through dates, source dates, coverage notes, and request ids.