The permit data you need —
with a transparent data frontier
Search 2.2M+ historical well-permit records by county, operator, and API number across 27 configured state sources. Latest record dates, fields, and coordinate availability vary by regulator.
Sound familiar?
Common permit-review workflows create the same three problems.
Tired of checking the RRC website manually?+
The Texas Railroad Commission website works, but checking it manually every Monday morning for multiple counties is tedious. OilPriceAPI pulls that data for you and delivers it as structured JSON you can query by county, operator, or date range — automatically.
Need to track competitor permits across multiple states?+
Comparing operators across counties can mean checking multiple state portals with different interfaces. OilPriceAPI normalizes historical permit records from 27 configured state sources into a common schema, while retaining per-state date and field limitations.
Want to automate your Monday morning permit review?+
Use the API to pull returned permit records by county or operator and route them into your own workflow on whatever schedule you choose.
Data features built for land work
Every field a landman needs. County code, legal description, API number, operator name, formation, and coordinates — all in one response.
County-Level Search
Query permits by county name or FIPS code. Pull everything filed in Midland, Reeves, or McKenzie County last week in a single API call. Combine with state filter for multi-state coverage.
API Number Lookup
Look up any well by its 14-digit API number. Get the full permit record including operator history, well type, formation, and location. Essential for due diligence and title work.
Operator Filtering
Filter permits by operator name across configured permit states. Track what Pioneer, Devon, EOG, or any independent operator has filed recently. Spot new entry into your acreage area before the competition does.
Lat/Lon Where Available
Decimal degree coordinates are returned where the state filing provides them. Plot available coordinates in ArcGIS, QGIS, or any mapping tool without manually re-keying state records.
27 Configured State Sources
Texas, North Dakota, Oklahoma, Colorado, Wyoming, New Mexico, Pennsylvania, Ohio, West Virginia, Montana, Utah, and 16 more configured sources. Historical depth, latest record dates, and fields vary by regulator.
Competing Permit Detection
Use the proximity search to find permits filed near a specific lat/lon. Check for competing permits within a defined radius of your lease before committing to acreage — a workflow no state portal supports natively.
Query permits by county in one line
Replace your Monday morning manual check with a scheduled script
# Get permits filed in Midland County, TX in the last 7 days
curl "https://api.oilpriceapi.com/v1/drilling-intelligence/well-permits?state=TX&county=Midland&days=7" \
-H "Authorization: Token YOUR_API_KEY"Section, township, and range are included where available from the state filing. Not all states include STR in permit filings.
A focused permit-monitoring workflow
Historical permit search supports research and repeated county/operator checks from your own code. It is not presented as a replacement for title, production, or subsurface workflows.
Pricing: Drilling Intelligence is on the Scale plan
Well permits, rig counts, DUC wells, and frac spreads are Drilling Intelligence endpoints, included in one tier — Scale.
Scale
For developers, operators, and analytics teams
or $2,870.40/yr billed annually
- ✓ Drilling Intelligence: well permits, rig counts, DUC wells, frac spreads
- ✓ 1,000,000 API requests/month
- ✓ Futures data and WebSocket real-time
- ✓ Dedicated support + Slack
Need a commodity-price plan without drilling data? Compare all plans.
Common questions from landmen
Which state sources are configured?+
The historical database is configured for Texas, North Dakota, Oklahoma, Colorado, Wyoming, New Mexico, Montana, Utah, West Virginia, Pennsylvania, Ohio, Louisiana, Kansas, Mississippi, California, Alaska, Arkansas, Illinois, Kentucky, Michigan, Nebraska, Tennessee, Virginia, Alabama, Indiana, Florida, and New York. This list is historical breadth, not uniform freshness or alert readiness.
Is section-township-range data included?+
STR data is included where the state provides it in the permit filing. Texas (RRC) and several other states do include STR. However, not every state includes STR in machine-readable format. The API returns it when available and omits the field when not present.
How current is the permit data?+
Permit freshness and completeness vary by state source and filing lag. State pages report the latest returned permit-record date separately from the configured source-check schedule.
Can I search by proximity to a specific location?+
The API can filter returned records with coordinates by latitude, longitude, and radius. Coordinate availability and completeness vary by state filing, so radius results must not be treated as a complete territory inventory without a coverage check.
Does the API include mineral rights ownership data?+
No. Well permit data covers the regulatory filing — operator, well location, formation, permit type, and status. Mineral rights ownership (royalty owners, working interest owners) is not included and isn't available via public permit filings.
Stop checking state portals manually
Explore 2.2M+ historical permit records, then pull them programmatically on the Scale plan.
Start Free TrialFree trial included · No credit card · Cancel anytime