1
Create or sign in
Create an EnergyNetWatch account or sign in, then open Settings → API Access to buy credits and activate API-only access.
Oil and gas data API access
Oil and Gas Data API for Wells, Permits, Production, Operators, and Infrastructure Signals
EnergyNetWatch gives developers, analysts, and commercial teams API access to structured public oil and gas records covering operators, permits, wells, production, facility permits, infrastructure signals, TX/NM source-signal reports, source dates, and coverage notes.
Prepaid API credits start at $50 for 10,000 units. Use the OpenAPI schema, API keys, request IDs, rate-limit headers, and usage controls to build internal dashboards, CRMs, enrichment jobs, and AI workflows.
- Prepaid API credits from $50 for 10,000 units
- Operators, permits, wells, official Texas regulatory records, production, physical midstream, and TX/NM signals
- API documentation for developers
- API keys, usage limits, request IDs, and rate-limit headers
- Source dates, coverage notes, and caveats where they matter
- Built for dashboards, AI tools, CRMs, enrichment jobs, and recurring reports
Getting started
From account to first API request
This is the shortest path for a developer or analyst testing EnergyNetWatch API access from a new workspace.
2
Buy API credits
Create an account, open Settings → API Access, and complete prepaid checkout. API-only access does not require a Premium app subscription. Request help separately for custom delivery or licensing.
3
Create an API key
After payment is processed and access is active, create a key in API Access or use your existing active key. Save it privately and store it server-side.
4
Run the health check
Confirm the key, account state, rate-limit headers, request id, and remaining usage before larger requests.
5
Run a small operator request
Use a simple Civitas/operator lookup before running permit, well, production, or signal workflows.
6
Open the schema
Use the OpenAPI JSON to inspect endpoint parameters, response fields, error responses, and unit costs.
Oil and gas data integration: from API to CSV or an AI workflow
Start with one county and one dataset before connecting a larger dashboard or CRM. The Texas county drilling permit export example includes a downloadable script, CSV and JSON output, pagination checks, and a dated sample. It shows how to retain operator names and source dates without treating a permit as proof that drilling has started.
For AI-assisted review, follow the county export and MCP workflow. The current MCP permit tool does not filter by county: use the REST export first, then review the file in a file-capable client. For official Texas production, use the separate well-to-lease production API workflow; lease totals are not individual-well production.
Compare oil and gas API pricing and unit costs before scaling. These examples support internal research and integration; ask about licensing before redistribution or resale.
Developer API for oil and gas data
A practical oil and gas data API for targeted workflows
Most teams do not need a full enterprise data platform just to test an API connection, enrich a CRM, monitor permit activity, feed an internal dashboard, or support an AI workflow. EnergyNetWatch API access is designed for specific oil and gas data jobs: start with the records and endpoints you need, then expand as the workflow proves value.
Operators
Search operator records, fetch operator profiles, and connect operator names to permit, well, production, and activity context.
Permits
Query drilling permits by state, county, text search, date window, or reported spud date. Text search can match operator names; available filters vary by endpoint.
Wells
Start with four-unit normalized search or well detail, then use Texas regulatory calls when the workflow needs official operator, district, lease, completion, inactive-status, or test context.
Production
Keep supported modeled well history separate from official filed Texas lease production. A multi-well lease total is not official individual-well production.
Facility permits
Preview facility permit records with source caveats and filing context.
Infrastructure signals
Rank operators by infrastructure lead signals and related permit activity where available.
Physical midstream
Query bounded Texas pipeline GIS, T-4 route evidence, and regulator-derived Texas or New Mexico facility records.
TX/NM signal endpoints
Call live TX PS-48, NM APD, and combined TX/NM signal summary endpoints for reporting workflows.
Data availability
Search grouped evidence for a company or operator across profiles, state mappings, permits, wells, production rollups, and facility records.
API pricing
Prepaid API credits from $50
Start small, validate the workflow, then expand by dataset, usage volume, geography, or delivery model. Access may vary by coverage, endpoint family, and plan.
API Starter Credits
$50
For developers, analysts, and small teams testing a targeted oil and gas data workflow.
- 10,000 prepaid API units
- API key access
- Selected endpoint access
- API reference
- Usage and rate-limit controls
Premium App + API
From $150/month
For users who want the EnergyNetWatch app plus API access for exports, review, validation, and recurring workflows.
- Premium app access
- Maps, filters, exports, and reports
- Included API access
- Larger usage allowance
- Commercial workflow fit
Custom API / Data Delivery
Custom
For teams needing higher volume, commercial use, recurring delivery, custom CSV/API workflows, or broader coverage.
- Higher usage limits
- Dataset and geography scoping
- Custom reporting or delivery cadence
- Internal dashboard support
- AI workflow support
API use case guides
High-intent API workflows
These pages break the API surface into the searches buyers actually use: permits, operators, production, wells, infrastructure signals, CRM enrichment, dashboards, and AI agents.
Example responses
What comes back from the API
Responses include structured JSON and should preserve request ids, pagination, source context, and coverage notes where the endpoint provides them. These abridged examples use illustrative values, not current search results; additional fields are omitted.
Health response
{
"success": true,
"data": {
"ok": true,
"service": "oandg-public-api",
"now": "2026-09-13T12:00:00.000Z"
}
}Operator search response
{
"success": true,
"data": {
"items": [
{"operator_id": 123, "operator_name": "Example Energy LLC"}
],
"pagination": {"page": 1, "limit": 5, "returned": 1}
}
}No-key response
{
"success": false,
"error": "Unauthorized"
}Workflows
Built for developers, analysts, and AI workflows
The API is useful when oil and gas data needs to move into another system instead of staying inside a web app.
- Internal dashboards
- CRM enrichment
- Permit monitoring
- Operator activity scoring
- County and state watchlists
- AI agents and MCP/tool-calling workflows
- Recurring CSV or API delivery
- Business development lead scoring
- Infrastructure and midstream signal tracking
Source notes
Why source dates and caveats matter
Oil and gas data varies by state, source cadence, filing type, record quality, and loaded-through date. EnergyNetWatch API responses are designed to keep source freshness, coverage context, request IDs, and caveats visible where they matter.
Examples
Example API requests
Health check
curl https://api.energynetwatch.com/api/public/health \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"Operator search
curl "https://api.energynetwatch.com/api/public/operators?search=Civitas&limit=5" \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"Permit search
curl "https://api.energynetwatch.com/api/public/permits?state=TX&search=Civitas&limit=10" \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"Data availability
curl "https://api.energynetwatch.com/api/public/data-availability?search=Civitas&state=TX&includeCounty=true" \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"TX/NM signal summary
curl "https://api.energynetwatch.com/api/public/reports/tx-nm-signal-summary" \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"Texas PS-48 signal sample
curl "https://api.energynetwatch.com/api/public/signals/tx/ps48?limit=2" \
-H "X-API-Key: $ENERGYNETWATCH_API_KEY"Fit
Who should use the EnergyNetWatch API?
Developers
Build oil and gas data into internal tools, dashboards, agents, or customer workflows.
Business development teams
Track operators, permits, production context, and infrastructure signals for lead generation.
Analysts
Automate recurring data pulls instead of repeating state-site searches and manual exports.
AI and automation teams
Give AI tools structured, source-aware oil and gas data instead of unstructured web pages.
Small teams
Start with a focused API plan before committing to a broader platform subscription.
Use the app
Search, filter, map, export, and review oil and gas records interactively.
Use API access
Deliver records into your own system, dashboard, AI workflow, CRM, report process, or data pipeline.
Use custom reports
Have EnergyNetWatch package recurring signals without maintaining an API connection.
FAQ
Oil and gas data API questions
What is an oil and gas data API?
An oil and gas data API lets software systems request structured energy records such as operators, wells, permits, production history, facility permits, and infrastructure signals. Instead of manually downloading files or searching state portals, an API can deliver records into dashboards, CRMs, reports, AI tools, and internal workflows.
Does EnergyNetWatch API access require the full app?
No. EnergyNetWatch can support API-only access with prepaid unit packs. Starter API credits begin at $50 for 10,000 units.
What records can I access through the API?
Available API records may include operators, drilling permits, wells, Texas RRC operator/district/lease identity, completion and inactive-well context, modeled well history, official filed Texas lease production, facility permits, physical pipeline/T-4 records, TX/NM signals, data availability checks, and source notes. Access depends on dataset, geography, endpoint, and plan.
Can I look up a well by API number?
Yes. General well search and detail are four units each. For Texas, a separate 24-unit regulatory identity call resolves official operator, district, and lease fields; the 40-unit completion call and 48-unit official lease-production call are separate so integrations request only the depth they need.
Can I use the API with AI tools or an MCP server?
Yes. EnergyNetWatch API access is suitable for server-side AI workflows, tool-calling systems, MCP-style tools, and internal automation when keys are stored securely and source context stays visible.
Is this public-source data?
EnergyNetWatch focuses on making public energy records more usable by normalizing records, preserving source context, and exposing structured workflows through the app, reports, exports, API access, and MCP workflows.
How is usage controlled?
API access uses endpoint permissions, rate limits, prepaid units, request IDs, and clear error responses for missing keys, invalid keys, exhausted usage, unsupported endpoints, and rate limiting.
Can I redistribute API data?
Internal dashboards, enrichment, monitoring, and workflow automation are the usual starting points. Contact EnergyNetWatch before using API data in a public-facing or resold product.
What is the difference between the API and MCP server?
The API is best when software systems need direct endpoint access to structured records. The MCP server is best when an AI tool or agent needs to query EnergyNetWatch data through natural-language workflows and tool calls.