EnergyNetWatch
Menu
API reference

Oil and Gas API Workflow Examples

Use these patterns to test EnergyNetWatch API access with real business workflows: operator activity reports, permit monitoring, CRM enrichment, and AI tool integrations.

View pricingSecurity guidance

Build a 12-month Texas operator activity report

Pull operator matches, permit activity, production context, and available infrastructure evidence for a short commercial report.

GET https://api.energynetwatch.com/api/public/data-availability?search=OPERATOR_NAME&state=TX&includeCounty=true
GET https://api.energynetwatch.com/api/public/operators?search=OPERATOR_NAME&limit=5
GET https://api.energynetwatch.com/api/public/operators/{id}/permits-summary?months=12
GET https://api.energynetwatch.com/api/public/operators/{id}/production-summary
GET https://api.energynetwatch.com/api/public/infrastructure/operator-leads?operatorId={id}

Monitor new permit activity for a sales territory

Run a scheduled server-side job for counties or operators and send only changed records into a CRM or dashboard.

GET https://api.energynetwatch.com/api/public/permits?state=TX&county=REEVES&limit=100
GET https://api.energynetwatch.com/api/public/permits/top-operators?state=TX&county=REEVES
GET https://api.energynetwatch.com/api/public/permits/operator-growth?state=TX

Enrich CRM accounts with source-aware context

Match company names to operator records, then attach permitted activity and coverage notes to internal account records.

GET https://api.energynetwatch.com/api/public/data-availability?search=ACCOUNT_NAME
GET https://api.energynetwatch.com/api/public/operators?search=ACCOUNT_NAME&limit=3
GET https://api.energynetwatch.com/api/public/operators/{id}/permits-summary

Give an AI agent guarded oil and gas tools

Use the API directly or through MCP so the agent can ask targeted questions without seeing database credentials.

GET https://api.energynetwatch.com/api/public/health
GET https://api.energynetwatch.com/api/public/data-availability?search=Civitas&state=TX
GET https://api.energynetwatch.com/api/public/operators?search=Civitas&limit=5

Workflow guardrails

  • Store ENERGYNETWATCH_API_KEY server-side.
  • Log X-Request-ID for support and failed jobs.
  • Keep source dates, loaded-through values, and caveats in generated reports.
  • Handle 402, 403, and 429 without retry loops.
  • Use data availability checks before broad pulls on unknown account lists.