Menu
Developers

EnergyNetWatch API reference

Reference material for approved server-side integrations using EnergyNetWatch operator, permit, well, and production endpoints.

Request API accessView coverage

Base URL

Approved customers receive API access through the public EnergyNetWatch API domain.

https://api.energynetwatch.com

Authentication

Send an API key with every protected request. Keep keys server-side and rotate them if a key may have been exposed.

X-API-Key: enw_live_or_test_key

Example request

curl https://api.energynetwatch.com/api/public/health \
  -H "X-API-Key: $ENERGYNETWATCH_API_KEY"
Endpoint catalog

Public API surface

Request credentials
Method
GET
Path
/api/public/health
Purpose

Authenticated health and entitlement check.

Method
GET
Path
/api/public/openapi.json
Purpose

OpenAPI 3.1 contract for approved integrations.

Method
GET
Path
/api/public/operators
Purpose

Search and page operator records.

Method
GET
Path
/api/public/operators/{id}
Purpose

Fetch one operator profile.

Method
GET
Path
/api/public/operators/{id}/production-summary
Purpose

Operator production summary where supported by coverage.

Method
GET
Path
/api/public/operators/{id}/permits-summary
Purpose

Operator permit activity summary.

Method
GET
Path
/api/public/permits
Purpose

Search and page permits.

Method
GET
Path
/api/public/permits/top-operators
Purpose

Rank operators by permit activity.

Method
GET
Path
/api/public/facility-permits
Purpose

Preview facility permit records with source caveats.

Method
GET
Path
/api/public/wells
Purpose

Search and page well records.

Method
GET
Path
/api/public/wells/{api}
Purpose

Fetch one well profile by API number.

Method
GET
Path
/api/public/wells/{api}/production
Purpose

Fetch production history for a supported well.

Method
GET
Path
/api/public/production/latest-month
Purpose

Return the latest production month known to the API.

Access details

How access works

Base URL

https://api.energynetwatch.com

Authentication

Send an API key in the X-API-Key header on every protected request.

Authorization

Endpoint access is scoped by account entitlement and approved use case.

Coverage metadata

Responses may include source freshness and coverage context where it is relevant to interpretation.

OpenAPI

A machine-readable OpenAPI schema is provided for approved API customers and partners.

Integration guidance

Recommended practices

  • Keep API keys in server-side environments or managed secret stores.
  • Use the health endpoint during deployment checks and monitor setup.
  • Retain coverage and source context when displaying API results to end users.
  • Use pagination and filters for recurring data synchronization jobs.
  • Contact EnergyNetWatch before using API responses in public-facing or redistributed products.