Texas RRC Oil & Gas Well Permit (W-1) Scraper
Pricing
from $8.32 / 1,000 permit records
Texas RRC Oil & Gas Well Permit (W-1) Scraper
Export Texas Railroad Commission W-1 drilling permits: API number, operator, lease, field, county, RRC district, wellbore profile, total depth, status, spud & completion dates, GPS and survey location. JSON, CSV or Excel.
Pricing
from $8.32 / 1,000 permit records
Rating
0.0
(0)
Developer
Scrapers Lat
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
0.038 hours
Issues response
7 days ago
Last modified
Categories
Features
Share
Texas RRC Oil & Gas Well Permit (W-1) Scraper
The most complete Texas oil and gas drilling permit scraper available. It returns every field the Railroad Commission W-1 Drilling Permit Query exposes (API number, operator, lease, field, county, RRC district, wellbore profile, total depth, status and dates), plus per-permit detail (spud, drilling-completed and surface-casing dates, completed well type, GPS coordinates, survey and legal location, permit restrictions) and lease summary (lease well type, field number and current operator status), and gives you 8 filters to target exactly the permits you need.
Here is one real result, with every field the actor returns:
{"apiNumber": "47538447","apiNumberFormatted": "475-38447","district": "08","rrcDistrict": "08","leaseName": "MI DIA 48 WD1","leaseNumber": "62302","wellNumber": "901H","operatorName": "XTO ENERGY INC.","operatorNumber": "945936","county": "WARD","submittedDate": "07/18/2024","approvedDate": "01/21/2025","statusNumber": "881636","wellboreProfile": "Horizontal","filingPurpose": "New Drill","amendment": true,"totalDepth": 10800,"stackedLateralParentDp": null,"status": "APPROVED","universalDocNo": "497523671","permitDetailUrl": "https://webapps2.rrc.texas.gov/EWA/drillingPermitDetailAction.do?methodToCall=searchByUniversalDocNo&universalDocNo=497523671","leaseDetailUrl": "https://webapps2.rrc.texas.gov/EWA/leaseDetailAction.do?searchType=apiNo&apiNo=47538447&distCode=08&leaseNo=62302&methodToCall=displayLeaseDetail","gisViewerUrl": "https://gis.rrc.texas.gov/GISViewer/index.html?api=47538447","imagesUrl": "https://rrcsearch3.neubus.com/esd3-rrc/api.php?function=GetImage&api_no=47538447","sourceUrl": "https://webapps2.rrc.texas.gov/EWA/drillingPermitsQueryAction.do"}
The example above shows the first 25 of 55 fields.
What it does
This actor searches the Texas Railroad Commission (RRC) public W-1 Drilling Permit Query and returns clean, structured permit records for landmen, mineral and royalty investors, and title shops. Every permit comes back with the operator, lease, field, county, RRC district, wellbore profile, total depth, permit status and the submitted and approved dates.
Turn on permit details and each record is enriched from the permit detail page with spud, drilling-completed and surface-casing dates, completed well type, SWR reference, surface location (nearest town, distance, direction), GPS coordinates and datum, survey and legal location (section, block, survey, abstract number) and any permit restrictions. Turn on lease summary to add the lease well type, field number and current operator status.
You can filter by operator name or number, county, RRC district, field name or number, lease name or number, API number, wellbore profile, and approved or submitted date ranges.
Quickstart
Run this input to pull recent horizontal permits approved in Ward County, District 08, with full permit details:
{"county": "WARD","district": "08","approvedDateFrom": "01/01/2025","approvedDateTo": "01/31/2025","maxItems": 100,"withDetails": true}
Billing and limits
This actor is pay per result. You are charged one result event per permit returned. Optional add-on events: details (permit detail enrichment, on by default), lease (lease summary), ai_summary and ai_extract. Add-on events are charged only when they return usable data, and paid add-ons are disabled for free Apify accounts. Free accounts are capped at 10 results per run. When you set a spend limit, the actor stops returning and charging once the limit is reached. Failed fetches are never charged.
