Texas Railroad Commission data

RRC Wellbore Query & API Number Lookup

Use the RRC Wellbore Query workflow to look up a Texas well by API number, then pull identity, completion, and filed lease production.

EnergyNetWatch normalizes the relationships between Texas regulatory datasets while preserving source dates, reporting grain and important regulatory context.

Explore API Reference Get an API key — $50 View API Pricing

Identifier relationship

API Number

RRC Well

Lease Identity

Filed Production

The well identifier starts the workflow. The lease identity establishes the applicable production-reporting grain.

How the Texas RRC API workflow works

EnergyNetWatch lets a developer start with a Texas API number, resolve the corresponding Railroad Commission well and lease identity, optionally retrieve completion context, and request official filed production for the resolved lease. Texas production reporting grain matters because official oil production can represent multiple wells on the same lease rather than production from one individual well.

Verified workflow check — September 5, 2026

Five live completion requests through the published MCP package returned in 79–426 milliseconds after a query-performance repair. Their data payloads matched the pre-change results, excluding request metadata. This is a five-well check, not a response-time guarantee or a complete coverage audit.

General Texas well responses identify available official lease context and differences from legacy estimates. Use the official filed-lease route for lease production; modeled well estimates remain a separate measure. Start with well numbers you already know and check each response’s source date and availability.

Four-step workflow

From Texas API Number to Filed Production

The Texas RRC API workflow connects the wellbore identifier to the regulatory lease relationship needed for source-aware production retrieval.

API Number

RRC Well

Lease Identity

Filed Production

Step 1
Find the well
Search or validate the Texas API number against EnergyNetWatch's normalized well index.
Step 2
Resolve RRC identity
Connect the API number to official Railroad Commission operator, district, classification and lease information.
Step 3
Add completion context
Retrieve supported formation, perforation, depth and completion information when the workflow requires it.
Step 4
Retrieve filed production
Use the resolved lease identity to retrieve official reported production while preserving the source reporting grain.

Verified September 12, 2026

Worked example: API 4230137185 to Bowen Davis Unit

Both requests returned 200 in the dated check. Resolve the well identity first, then request one production month using the returned lease key.

# Server-side only; set ENW_API_KEY securely before running.
curl --fail-with-body \
  'https://api.energynetwatch.com/api/public/regulatory/tx/wells/4230137185' \
  --header "X-API-Key: $ENW_API_KEY"

# Use the O / 08 / 63759 identity returned above.
curl --fail-with-body --get \
  'https://api.energynetwatch.com/api/public/regulatory/tx/leases/O/08/63759/production' \
  --header "X-API-Key: $ENW_API_KEY" \
  --data-urlencode 'start=2026-06' \
  --data-urlencode 'end=2026-06' \
  --data-urlencode 'limit=1'

Check these response fields

The identity response returned regulatoryIdentity oilGasCode O, districtNo 08 and leaseNo 63759. The production response returned one series row for 2026-06-01: BOWEN DAVIS UNIT, EOG RESOURCES, INC. (253162), reportFiledFlag Y, oilBbl 12,339 and casingheadGasMcf 21,478.

Keep the reporting grain

productionBasis is official_filed_lease. wellCount was 1 in this response, but the source remains a lease total. Never sum repeated copies of the same lease month when several API numbers resolve to it. June 2026 was this lease's latest available filed month at retrieval, not a statewide freshness claim.

The identity request uses 24 units and the lease-series request uses 48: 72 units for this pair. Optional completion, search and additional requests cost separately. Review current API pricing before a larger run. Keep your key out of browser code, shared notebooks and AI prompts.

A valid lease can return no rows for a selected month; do not convert that absence into zero production. A 401, quota error or server failure is an access/request problem, not a production observation. See the production source guide and missing-data checklist for interpretation. Later filings or identity corrections can change this example.

The integration problem

Texas Well and Production Records Don't Live in One Clean Workflow

Texas regulatory records are distributed across multiple Railroad Commission datasets, identifiers and query systems. A usable production workflow must connect those record families without erasing their different grains.

EnergyNetWatch handles these relationships and exposes the resulting records through a consistent API so customers do not have to build and maintain the Texas regulatory-data pipeline themselves.

API number: identifies the wellbore.
RRC well record: can connect the API number with district, operator and lease information.
Production lookup: may require the corresponding district, classification and lease identity.
Reporting grain: is not necessarily the same as the well-identity grain.

Official source fact

The Texas RRC Wellbore Query guidance documents searches by API number and returns related operator, district, lease and well fields.

Available records

Texas Well and Production Data Available Through the API

EnergyNetWatch exposes supported well, completion, production and source-context records as separate, structured parts of the workflow.

Well identity

API number
operator
county
RRC district
oil or gas classification
lease identity
well information where supported

Completion context

completion records
formation information
perforation context
depth information where supported
retained W-2/G-1 context where supported

Filed production

monthly filed production
lease-production history
latest available filed month
reporting status and context
oil and gas volumes where applicable

Source context

originating source
loaded-through date
reporting grain
source and update context
coverage notes
regulatory caveats

Reporting grain

Texas Production Data Requires the Correct Reporting Grain

Official Texas production should not automatically be labeled as individual-well production. Railroad Commission guidance states that production is reported by lease rather than individual well; an oil lease can include production from multiple wells.

Incorrect interpretation

API Number → Production Record → “Well Production”

Source-aware workflow

API Number → RRC Well Identity → Lease Identity → Filed Lease Production → Reporting-Grain Context

EnergyNetWatch preserves this distinction in analytics, dashboards, AI-generated research, CRM enrichment, internal reporting and automated data workflows. The identifier path remains visible so downstream systems can describe the record accurately.

Primary source

See the Railroad Commission of Texas Production Data Query FAQ for the Commission's explanation of lease-level reporting.

Working endpoints

Example Texas RRC API Workflow

The endpoints keep normalized well lookup, official RRC identity, completion context and filed production as explicit operations.

For authentication, schemas, parameters, response contracts and current usage pricing, see the EnergyNetWatch API Reference.

Find a Texas well

GET /api/public/wells?search={api}&state=TX

Retrieve normalized well detail

GET /api/public/wells/{api}?state=TX

Resolve official RRC identity

GET /api/public/regulatory/tx/wells/{api}

Retrieve completion context

GET /api/public/regulatory/tx/wells/{api}/completion

Retrieve filed lease production

GET /api/public/regulatory/tx/leases/{type}/{district}/{lease}/production

Use cases

Built for Texas Oil and Gas Data Workflows

Each workflow uses the same source-aware identifier relationships for a different application job.

Data enrichment

Attach official Texas regulatory context to existing well, operator or asset records.

Internal applications

Bring Texas well and production records into dashboards, internal tools and governed reporting workflows.

Operator intelligence

Connect regulatory well records with EnergyNetWatch operator, permit and infrastructure datasets.

Data pipelines

Use structured responses for recurring enrichment, monitoring and analytics jobs.

AI and agent workflows

Allow authorized AI applications to query source-aware Texas regulatory records through EnergyNetWatch API or MCP interfaces.

MCP access

Query Texas RRC Data Through MCP

Compatible AI clients can access supported EnergyNetWatch workflows using the customer's authorized API access. MCP uses the same read-only source boundaries as the underlying API.

Explore MCP Server View MCP Setup

Example agent request

“Look up Texas API number 42XXXXXXXX, identify the official RRC operator and lease, and return available filed production while clearly stating the reporting grain and latest source date.”

Direct answers

Texas RRC API Frequently Asked Questions

These answers distinguish the wellbore identifier, regulatory lease identity, completion context and production-reporting grain.

Does the Texas Railroad Commission provide an API?

The Railroad Commission of Texas publishes regulatory information through public query systems, research pages and downloadable datasets. EnergyNetWatch provides a normalized, authenticated API layer designed for application, enrichment and automation workflows while keeping the relevant Railroad Commission identifiers and source context visible.

Can I look up a Texas well by API number?

Yes. EnergyNetWatch can search a normalized Texas well index by API number and, through the official Texas regulatory route, resolve supported operator, district, oil or gas classification, lease identity and well context. Available fields depend on the underlying source records and endpoint coverage.

How do I find a Texas lease number from an API number?

Start with the API number, then resolve the corresponding Railroad Commission well identity. The official RRC identity response can provide the district, classification and lease relationship needed for the applicable lease-production request. EnergyNetWatch performs that identifier handoff through a consistent API workflow.

Can I retrieve Texas production data using an API number?

Yes, when the well resolves to a supported Railroad Commission lease identity. EnergyNetWatch uses the API number to find the relevant district, oil or gas classification and lease number, then retrieves applicable filed production. The response should be interpreted at the reporting grain supplied by the source.

Is Texas oil production reported by individual well or by lease?

Official Texas oil production is reported at lease grain, and one oil lease can contain multiple producing wells. A production record reached from an API number should therefore not automatically be labeled as official individual-well production. EnergyNetWatch keeps the lease relationship and reporting-grain context visible.

What is the difference between a Texas API number and an RRC lease number?

A Texas API number identifies a wellbore. An RRC lease number identifies the regulatory lease used for applicable production reporting and related records. A well can be connected to a lease, but the well identifier and production-reporting identifier describe different record grains.

Can I retrieve Texas completion data?

Yes, where supported records are available. The separate completion workflow can return formation, perforation, depth and retained approved W-2/G-1 context. Completion information provides regulatory well context; it does not by itself establish current production, reserves, economics or present drilling activity.

Can an AI agent query Texas oil and gas data?

Yes. An authorized AI application can use the EnergyNetWatch API directly or invoke supported read-only tools through an MCP-compatible client. The agent should preserve the official identifiers, latest source date, reporting grain and regulatory caveats returned with the records.

Evidence and navigation

Sources and Methodology

Official RRC sources establish the regulatory facts. EnergyNetWatch normalizes the identifiers and relationships needed for programmatic use while preserving source context.

Primary Railroad Commission sources

Texas RRC Wellbore Query — search Texas wells by API number and other regulatory identifiers.
Texas RRC API-number lookup guidance — official Wellbore Query search and result-field documentation.
Railroad Commission of Texas Production Data Query — general and specific-lease production searches.
Production reporting-grain guidance — official explanation of Texas lease-level production reporting.
Railroad Commission oil and gas well-record documentation — well-record and lease-production context.

Related EnergyNetWatch guides

Build with Texas regulatory data

Build With Texas Regulatory Data

Connect Texas API numbers with regulatory well identity, completion, lease and filed production records without building and maintaining the underlying Texas regulatory-data pipeline yourself.

Explore API Reference Get an API key — $50 Custom or team access View API Pricing