Menu
Developers

EnergyNetWatch API reference

Reference material for approved server-side integrations using EnergyNetWatch oil and gas data endpoints for operators, permits, wells, production, and infrastructure records.

Request API accessView coverageOpenAPI JSON

Base URL

Approved customers receive targeted 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"
Launch handoff

What an approved integration needs

Request account setup

Approved account

API access is provisioned for approved customer accounts. The same account controls billing, active entitlement, key status, and support context.

Key lifecycle

Generate keys only from authenticated account workflows, store them server-side, and revoke or rotate a key when an integration changes owners.

Limits and scopes

Every protected request is checked against endpoint scope, active entitlement, daily allowance, and shared rate-limit windows.

Contract first

Use the OpenAPI schema as the integration contract, then preserve response metadata for source freshness, coverage, and request traceability.

Smoke tests

Copy-paste checks before production use

Check

Health

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

Expected: HTTP 200 for an active scoped key, request id header, rate-limit headers, and entitlement details in the response body.

Check

Unauthenticated control

curl -i https://api.energynetwatch.com/api/public/health

Expected: HTTP 401 with WWW-Authenticate: X-API-Key. Protected data endpoints should fail closed without a valid key.

Check

Operators sample

curl -i "https://api.energynetwatch.com/api/public/operators?search=Civitas&limit=5" \
  -H "X-API-Key: $ENERGYNETWATCH_API_KEY"

Expected: HTTP 200 when the key has operator read scope, paged records, and metadata suitable for logging the integration check.

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.
Response controls

Headers, errors, and metadata to retain

401 Unauthorized

No key, malformed key, revoked key, or paused key. The integration should stop and prompt for credential review.

403 Forbidden

Valid key but missing entitlement, inactive commercial state, unsupported endpoint scope, or daily allowance exceeded.

429 Rate limit exceeded

The shared request window has been consumed. Respect Retry-After and X-RateLimit-Reset before retrying.

X-Request-ID

Log this header with customer support tickets and failed jobs so the request can be traced safely.

X-RateLimit-*

Use limit, remaining, and reset headers for backoff, monitoring, and deployment health checks.

meta.freshness / meta.coverage

Retain source dates, loaded-through values, state coverage, and caveats in downstream displays and reports.