Track drilling activity before it becomes production
Use well permits as a forward supply signal. Query recent records by state and lookback window, then inspect the returned operator, county and record dates before acting on the data.
Query patterns for upstream intelligence
Start with the permit fields that answer where activity is moving, who is filing, and which formations or counties are seeing new work.
27-State Permit Coverage
Track public permit records from official state regulatory datasets, including Texas RRC, Oklahoma OCC, New Mexico OCD, and Alaska AOGCC.
Operator Search
Filter by operator where the source provides it, then compare activity across states, counties, and recent filing windows.
Formation And Basin Context
Use formation and basin fields where available to track activity in plays such as the Permian, Eagle Ford, Bakken, Marcellus, and DJ Basin.
County And Geography
Build market maps and business-development lists by county, state, and available location fields without scraping separate state portals.
Recent Activity Windows
Query latest and search endpoints for recent permit filings. Coverage and cadence vary by state source, so do not assume one global refresh interval.
Source And Freshness Fields
Use source and fetched_at metadata in API responses to keep internal dashboards honest about provenance and data recency.
First call: recent Texas permits
The documented endpoint requires the Scale plan. Read records from data.well_permits, counts from data.summary, and paging from data.pagination. Missing record fields may be null; source dates and completeness vary by state.
curl "https://api.oilpriceapi.com/v1/drilling-intelligence/well-permits?state_code=TX&days=30&per_page=1" \
-H "Authorization: Token YOUR_API_KEY"Evaluate coverage before you integrate
Start with a small request and inspect the returned records. Account entitlement, state coverage and the latest source dates determine whether the dataset fits your workflow.
Verified for public copy
- Canonical endpoint family: /v1/drilling-intelligence/well-permits
- State-specific coverage; inspect the returned record dates
- Recent-record API queries; confirm deeper history separately
- Official state regulatory datasets
- Documented state and lookback filters, with bounded pagination
- Check record dates and missing fields before relying on an observation
Keep these caveats visible
- Coverage and update cadence vary by state source
- Many core sources are checked daily; others publish weekly, monthly, or quarterly
- Historical coverage varies by state
- Permits are a forward signal, not a guarantee of production timing or volume
- Production and lifecycle linkage are adjacent pilots, not nationwide promises
- No public display, resale, or redistribution rights are implied
Upstream Intelligence
Track where operators are filing permits and which formations are seeing activity before volumes show up in production data.
Oilfield Services BD
Prioritize accounts and regions where permit activity suggests crews, equipment, acreage, or services may be moving.
Land And Data Products
Feed structured permit records into internal maps, asset screens, mineral workflows, and oil-and-gas software products.
Build from permit activity, not portal scraping
Use structured well-permit records to validate upstream intelligence, services, land, and data-product workflows.
Free trial available | Month-to-month | Internal API workflows