Oil & Gas Drilling
OilPriceAPI Drilling Intelligence - Well Permits
Datadory delivers oilpriceapi drilling intelligence well permits data covering 2.19 million-plus US drilling permits aggregated across 27 state regulators - all-time totals, trailing 30- and 365-day counts, year-over-year change and ranked operator shares for every state, with rig counts, frac spreads and DUC series riding the same feed, delivered daily, weekly, or hourly.
API, files, or your warehouse. Daily, weekly, or hourly.
What is the OilPriceAPI Drilling Intelligence well-permit dataset?
OilPriceAPI Drilling Intelligence - Well Permits is the physical-activity record in OilPriceAPI's three-dataset catalog, aggregating United States drilling-permit data from 27 configured state regulators into one normalized feed of more than 2.19 million historical records. Where a commodity-price feed says what hydrocarbons sold for, this one says who is lining up to drill: all-time permit totals per state, trailing 30-day and 365-day issuance, year-over-year change, and a ranked operator table carrying each company's permit count and market-share percentage.
The wider Drilling Intelligence bundle travels in the same envelope: weekly rig counts for the US, Canada and international markets, Permian, Eagle Ford and Bakken frac-spread differentials, monthly drilled-but-uncompleted (DUC) well analyses, and report feeds drawing on Baker Hughes, EIA and OPEC publications. Permitting leads rigs and rigs lead production, which is why activity desks read this record as the earliest of those three signals rather than the last.
Two properties make it usable at pipeline grade. First, normalization: identical fields return for any of the 27 states, so a multi-basin footprint is one integration instead of 27 portal dialects. Second, verification: Datadory marks the field definitions below as verified, checked against published documentation in the August 2026 research pass, with North Dakota confirmed directly as the reference state.
What do sample rows look like?
The verified North Dakota summary, exactly as it arrives:
# well permits - North Dakota, record as of 2026-08-17
state : North Dakota state_code : ND
total_permits : 41,899 coverage_start : 1904-12-23
latest_record : 2026-08-17 last_30_days : 69
last_365_days : 744 yoy_change : -18.2%Read what one row compresses. 41,899 permits spanning December 23, 1904 to August 17, 2026 is more than a century of state permitting history reduced to a single joinable summary. The activity window sits beside the stock: 69 permits issued in the latest 30 days against 744 across the trailing year, and the year-over-year change of -18.2% turns both into a trend statement - permitting is cooling in the state that anchors the Williston Basin.
Every other state lands in precisely this shape, keyed on state_code. One caveat stated plainly: North Dakota is the summary verified directly at research time, and the remaining 26 states inherit the structure rather than a second independent confirmation. Get a sample cut to the states you actually operate in and check their snapshots against whatever you already hold before wiring anything.
Which fields does the well-permit record include?
Ten fields make up the verified summary record, defined in the table below. Four carry the economics of the dataset - total_permits, last_30_days, last_365_days, year_over_year_change - and together they turn a static archive into an activity indicator: stock, momentum, and direction in one row.
The top_operators array is where competitive reads come from: each entry pairs an operator name with its permit count and percentage share of the ranking window, so concentration in a basin's permitting - who is locking up acreage and who has stepped back - is a sort operation rather than a research project.
The provenance group (data_as_of, source_checked_at, cadence) timestamps the newest underlying record and the state-source handling behind it. Those columns ride along on every delivery deliberately: they let your pipelines assert freshness thresholds themselves instead of trusting an unverified assumption about currency.
What does coverage look like across geography, time and granularity?
Geography - 27 US states with configured state-regulator sources, which spans essentially the whole American onshore drilling map: the Permian pair, the Williston, the Gulf Coast states, the Appalachian plays and the Mountain West. North Dakota was verified directly during research, with New Mexico and Colorado among the linked state pages; the definitive roster confirms with your sample.
Temporal - depth is a property of each state, because each regulator sets its own archive start. North Dakota runs from December 23, 1904 to August 17, 2026 as of the research date, giving 122 years of continuous permitting history; younger regulatory regimes start when their recording started. The feed preserves each state's true span rather than truncating everything to a common window.
Granularity - two levels serve different jobs. The aggregate summary - one row per state, with the ranked operator array beneath it - powers dashboards and screens. Row-level permit records sit underneath the aggregates for work that needs well-level resolution, and both levels normalize to the dictionary above so the switch between them is a filter, not a re-platforming.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
You pick the channel and the cadence; neither is coupled to anything upstream. Take a one-time historical pull of a century of North Dakota permits, or keep a warehouse table current so each new 30-day window and each revised operator share diffs cleanly into yesterday's rows. Deliveries arrive typed and keyed on state_code, so a state summary joins to your own acreage, rig or production tables on one column instead of after a fuzzy-matching project.
Scope is a parameter, not a rebuild: a feed cut to two basins widens to all 27 states without reshaping anything, and the provenance columns survive the trip intact, which means your own freshness alerts fire off data_as_of rather than off hope. Sample first - name your states, check the snapshots, then set the cadence.
Who uses this data, and for what?
- Leading-indicator modeling - permit issuance precedes rig mobilization by weeks, so the 30-day windows and year-over-year changes function as an early signal for activity, service demand and equipment utilization (investors and quants use cases).
- Competitive tracking - the
top_operatorsarray with permit counts and percentage shares shows which companies are adding inventory and which have gone quiet, state by state (market researchers use cases). - Multi-state consolidation - one normalized contract across 27 regulators replaces 27 portal dialects, EBCDIC layouts and shapefile projections, cutting weeks of maintenance out of a data stack (developers and builders use cases).
- Model features - aggregated permit counts and operator concentration feed directly into activity forecasts and basin-level supply models as engineered features (data scientists use cases).
- DUC and completion analysis - paired with the monthly DUC analyses in the same bundle, permitted-but-undrilled inventory becomes readable, separating true activity growth from backlog drawdown.
Which personas get the most value?
- Investors & Quant Researchers - the earliest quantitative signal in the drill-bit chain, with a century-long North Dakota history for backtesting (investors and quants use cases).
- Developers & Data-Product Builders - one schema, 27 states, provenance columns included - the shape a permitting dashboard or alerting product wants on day one (developers and builders use cases).
- Market Researchers & Consultants - defensible state-level permitting baselines and operator-share tables underneath market-sizing and entry work (market researchers use cases).
- Data Scientists & ML Engineers - stable-schema activity features with explicit timestamps, suitable as targets and regressors alike (data scientists use cases).
- Strategy and land teams at operators - read competitors' permitting tempo in the basins you hold acreage in, without building a state-by-state collection effort.
Which datasets sit next to this one?
This record owns the normalized multi-state permitting layer. Its neighbours own single jurisdictions and adjacent altitudes. The Texas Railroad Commission oil and gas data sets go deeper inside the largest single state - weekly Full Wellbore files and a monthly drilling-permit master straight from the regulator. The NDIC Oil & Gas Division well and rig data serves the Williston Basin well-by-well from the very state whose permit summary anchors this feed's verified sample. The Colorado ECMC data portal covers another linked state at full regulatory depth, and the USGS aggregated drilling and production data adds a national produced-volumes perspective - we maintain a direct Texas RRC vs USGS comparison for teams weighing regulator depth against national breadth. The Sondio Data Platform is the nearest commercial peer, delivering wells and monthly production histories from 27 regulatory sources.
The honest trade: regulators give maximum depth in one jurisdiction for the cost of learning each one; this record gives uniformity across 27 for the cost of going through a commercial layer. Pick by whether your question is how deep in Texas or how wide across the country. The OilPriceAPI source profile covers the vendor's full catalog, and the best oil and gas drilling datasets ranking places it among the alternatives.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
state | string | Full name of the state whose permits are summarized. | North Dakota |
state_code | string | Two-letter USPS code identifying the state; the join key across deliveries. | ND |
total_permits | integer | Count of all historical drilling permit records held for the state. | 41899 |
last_30_days | integer | Number of permits issued in the most recent 30-day window. | 69 |
last_365_days | integer | Number of permits issued in the trailing 365 days. | 744 |
year_over_year_change | number | Percentage change in permitting activity versus the prior comparable period. | -18.2 |
top_operators[].name | string | Operator name within the ranked top-operators list. | |
top_operators[].permits | integer | Permit count attributed to that operator over the ranking window. | |
top_operators[].pct_share | number | Operator's share of permits in the window as a percentage. | |
data_as_of / source_checked_at / cadence | datetime | Provenance group: timestamp of the newest underlying record, when the state source was last handled, and the configured handling frequency. | 2026-08-17 |
Questions buyers ask
What is OilPriceAPI Drilling Intelligence - Well Permits?
A normalized feed of United States oil and gas drilling permits aggregated from 27 configured state regulators, holding more than 2.19 million historical records. Each state summary carries all-time totals, trailing 30- and 365-day counts, year-over-year change and a ranked operator table with market-share percentages, delivered by Datadory on your chosen cadence.
How many US states does the permit coverage span?
Twenty-seven states with configured state-regulator sources, spanning the major onshore plays: the Permian, the Williston, the Gulf Coast, Appalachia and the Mountain West. North Dakota was verified directly during the August 2026 research pass; the definitive state roster confirms with your sample.
How far back does the permit history reach?
Depth varies by state because each regulator sets its own archive start. The verified reference case is North Dakota: 41,899 permits spanning December 23, 1904 through August 17, 2026 - 122 years of continuous permitting history. Younger regulatory regimes begin when their record-keeping began.
Does the data identify individual operators?
Yes. Each state summary carries a ranked top_operators array pairing every listed operator's name with its permit count over the ranking window and its percentage share of that window. Operator concentration - who is adding permits and who has stepped back - reads directly off the array without extra derivation.
What else comes in the Drilling Intelligence bundle?
Beyond well permits, the bundle carries weekly rig counts for the US, Canada and international markets, frac-spread differentials for the Permian, Eagle Ford and Bakken, monthly drilled-but-uncompleted (DUC) well analyses, and report feeds drawing on Baker Hughes, EIA and OPEC publications - the full physical-activity picture alongside the permitting layer.
How fresh is each delivered record?
Every record carries its own provenance columns: data_as_of timestamps the newest underlying permit record for the state, and companion fields record when the state source was last handled. Your pipelines read those stamps directly and set their own freshness thresholds, so currency is asserted per record rather than assumed globally.
Notes on this record
- Compiled from 27 state regulators OilPriceAPI aggregates the statistics programs of 27 configured US state regulators into one response shape - the normalization is the product, not an afterthought.
- Verified, not reconstructed All ten summary fields were checked against published documentation during the August 2026 research pass, and North Dakota was confirmed directly as the reference state.
- Activity, not prices Within OilPriceAPI's catalog this record sells physical activity - permits, operator share, rigs, frac spreads, DUCs. Price benchmarks live on the sibling commodity-price records.
- Freshness travels with the row Each summary timestamps its newest underlying record and its source handling, so downstream pipelines enforce currency thresholds themselves.
- 122 years in one state North Dakota's archive runs from December 23, 1904 to August 17, 2026 - a century of permitting history that survives as a single joinable summary.
- Sample policy Samples ship in the exact schema shown above, cut to whichever states and windows you name; the definitive state roster and row-level options confirm with the sample.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.