Can I fetch production by well API number?
Yes, where EnergyNetWatch has supported production coverage for that well.
Oil and gas data API
Production data API
Oil and Gas Production Data API for Well and Operator Context
EnergyNetWatch production API workflows are built for teams that need production context in dashboards, reports, operator reviews, and AI-assisted workflows. Coverage varies by state and source cadence, so responses should keep loaded-through dates and coverage notes visible.
Access model
API keys, endpoint access, usage units, request IDs, rate limits, and hard-stop billing controls.
Pricing
Prepaid API credits start at $50 for 2,500 units, with larger packs or custom plans for heavier use.
Source context
Responses should keep source dates, coverage notes, and caveats visible when they are available.
Example: a Texas well identifier to filed lease production
Reviewed September 12, 2026; June 2026 filed production. This is a retained example, not a claim about the latest available month today.
Send authenticated requests to https://api.energynetwatch.com with your X-API-Key header. Keep the key in a server-side environment or secret store, never browser code or an AI prompt.
GET /api/public/regulatory/tx/wells/4230137185GET /api/public/regulatory/tx/leases/O/08/63759/production?start=2026-06&end=2026-06&limit=1Selected results from the dated review
A readable summary, not the complete JSON response or a live query.
- Resolved reporting identity
- Oil code O; RRC district 08; lease 63759
- Lease / filed operator
- BOWEN DAVIS UNIT / EOG RESOURCES, INC. (253162)
- Production month
- June 2026
- Filed volumes
- 12,339 bbl oil; 21,478 Mcf casinghead gas
- Source basis
- official_filed_lease; reportFiledFlag Y
Resolve the lease identity first; do not copy this lease key for another well. Texas oil production is filed at lease grain and can include several wells. Do not call it official individual-well production or sum the same lease series once per well. The general well-production endpoint supplies supported modeled history under a different source contract. Missing months are not filed zeros; keep production month, source basis and retrieval date together.
Open the authenticated request example and Texas reporting guideRecords
What this API workflow can support
well production history
latest production month
operator production summaries
well profiles
coverage notes
Workflows
Common use cases
- Check latest loaded production month before downstream reporting.
- Add well-level production context to internal dashboards.
- Summarize operator production where supported by coverage.
- Combine production context with permits and wells for operator review.
Caveats
Use source records with context
- Production data availability and freshness vary by state.
- Production records can lag source publication and normalization.
- Production summaries should not be treated as reserve or economics estimates.
FAQ
Questions this page answers
Can I check the latest loaded production month?
Yes. The API includes latest-month information so jobs can avoid assuming stale data is current.
Next step
Start with prepaid API credits
Create an account, verify your email when required, then buy credits and create a key after access activates. Standard MCP uses the same API credits; no Premium subscription is required. AI-provider charges are separate. Ask about custom delivery or redistribution separately.
Related Texas and developer guides