What it returns
Oil and gas well records from 17 US state regulators, Alberta, British Columbia, Saskatchewan, the UK, the Netherlands, Norway, Brazil and Australia (offshore, Queensland, South Australia, Northern Territory, Victoria and Western Australia onshore), in one schema: country, API number (wellbore name outside the US), well name, operator, status, well type, field, county, surface latitude and longitude, spud, completion, plugging and status dates, depth and a link to the regulator's own record.
| State | Source | Wells |
|---|---|---|
| Kansas | Kansas Geological Survey well database | 520k |
| Oklahoma | Corporation Commission RBDMS well file | 457k |
| Colorado | Energy and Carbon Management Commission | 124k |
| New York | DEC oil, gas and other regulated wells (from 1860) | 47k |
| Texas | Railroad Commission wellbores: bottom-hole location, completion date and depth from casing records, plugging date (no operator or lease name in RRC open data) | 1.02M |
| California | CalGEM WellSTAR | 243k |
| New Mexico | EMNRD Oil Conservation Division permitting database | 142k |
| Kentucky | Energy and Environment Cabinet, Division of Oil and Gas (permit number as KY-<permit>, no API number or county) | 117k |
| Arkansas | Oil and Gas Commission | 38k |
| Florida | DEP Oil and Gas Program permitted wells (FL-<permit>) | 1.5k |
| Wyoming | Oil and Gas Conservation Commission wells via the state GeoHub (status codes as published; the layer's newest spud is 2022-07) | 69k |
| Utah | Division of Oil, Gas and Mining wells (via the Utah Trust Lands Administration GIS) | 40k |
| Alaska | Oil and Gas Conservation Commission well surface locations (via Alaska DNR) | 10k |
| Ohio | DNR Division of Oil and Gas Resources (no dates in the public layer) | 242k |
| West Virginia | DEP Office of Oil and Gas, all wells (well name is farm name and number) | 154k |
| Pennsylvania | DEP Office of Oil and Gas Management statewide well inventory (operator blank where DEP lists an individual) | 280k |
| North Dakota | Industrial Commission, Oil and Gas Division public well layer (production data is subscription-only there and not included) | 44k |
Alberta, Canada (CA, state AB) | Alberta Energy Regulator ST37 well licences: licensee, licence status, spud and final drill date, surface-hole coordinates; api is AB-<licence>, well name is the DLS surface location | 541k |
British Columbia, Canada (CA, state BC) | BC Energy Regulator well surface holes (via the BC Geographic Warehouse); api is WA-<well authorization>, operator is the BCER abbreviation | 34k |
Saskatchewan (CA, state SK) | Ministry of Energy and Resources wells (Saskatchewan GIS Petroleum service), one row per well; API number is the Saskatchewan well id (CWI), operator is the licensee, county the rural municipality, field the pool, depth converted from metres | 150k |
Norway (NO) | Norwegian Offshore Directorate (Sodir) FactPages, exploration and development wellbores; county is the sea area (North Sea, Norwegian Sea, Barents Sea), depth converted from metres, licence NLOD 2.0 | 8.5k |
United Kingdom (GB) | North Sea Transition Authority wellbores, offshore UKCS and onshore England; API number is the well registration number, operator is the responsible designated operator, county is Offshore or the onshore county, licence OGL v3.0 | 15.5k |
Netherlands (NL) | NLOG (TNO for the Ministry of Economic Affairs) boreholes and sidetracks, onshore and offshore; operator is the current owner, county is Onshore or Offshore, depth converted from metres (along hole); salt, coal and geothermal boreholes left out | 5.8k |
Brazil (BR) | ANP Tabela de Poços (BDEP technical archive, ANP open data), onshore and offshore; status and category in Portuguese as published, county is the sedimentary basin, field the field or block, depth converted from metres | 30.6k |
Australia (AU) | NOPTA petroleum wellbores (NOPIMS), mostly Commonwealth offshore, CC BY 4.0; no status published, field is the title (permit or licence), county the basin, spud is the kick-off date and completion the rig release date | 8.0k |
Australia: Queensland (AU, state QLD) | Geological Survey of Queensland boreholes (open data, CC BY 4.0), petroleum and coal seam gas wells; well_type is the subtype and result, field the tenure, completion the rig release date, record_url the GSQ borehole page. 20,000 wells. | |
Australia: Western Australia (AU, state WA) | WA Department of Energy, Mines, Industry Regulation and Safety onshore petroleum wells (DMIRS-025, data.wa.gov.au, CC BY 4.0); api is the UWI, well_type the well class, field the field or lease, county the basin, completion the rig release date; status is the department's code (P&A, O, ...). 4,300 wells. Offshore WA wells are in the AU offshore set. | |
Australia: South Australia (AU, state SA) | Department for Energy and Mining petroleum wells (SARIG, CC BY 4.0); api is the SARIG well id, well_type the class and result, field the licence, county the basin, completion the rig release date. 4,000 wells. | |
Australia: Victoria (AU, state VIC) | Geological Survey of Victoria petroleum wells (Vicmap open data WFS, CC BY 4.0), onshore wells only; api is the UWI, well_type the class code, field the licence, county the basin, completion the rig release date. 440 wells; offshore Gippsland and Otway wells are in the AU offshore set. | |
Australia: Northern Territory (AU, state NT) | Northern Territory Geological Survey petroleum wells (STRIKE, CC BY), onshore; api is the well name (no id is published), well_type the purpose and hydrocarbon shows, field the title, county the basin, completion the rig release date, record_url a GEMIS search. 300 wells. |
Refreshed weekly. Oklahoma's file carries no dates. Kansas and Colorado give the field and New York and Oklahoma the county. Status and type codes are as each state publishes them; Colorado and New York codes are expanded to words.
Request
POST https://api.pushbuild.com/oil-gas-wells/run with a JSON body. Send your key in the X-API-Key header.
| Field | Type | Description |
|---|---|---|
apiNumbers | list of strings | Well API numbers, with or without dashes; a prefix matches all sidetracks. |
operator | string | Operator name contains this text. |
wellName | string | Well or lease name contains this text. |
countries | list of strings | ISO country codes: US, CA (Canada: Alberta, British Columbia, Saskatchewan), GB (United Kingdom), NL (Netherlands), NO (Norway), BR (Brazil), AU (Australia: offshore titles, Queensland, South Australia, Northern Territory, Victoria and Western Australia onshore). Leave empty for all. |
states | list of strings | US states: TX, KS, OK, CO, NY, CA, NM, KY, AR, FL, WY, UT, AK, OH, WV, ND, PA. Canadian provinces: AB, BC, SK. Australian states: QLD, SA, NT, VIC, WA. |
county | string | County contains this text (OK and NY). |
field | string | Oil or gas field contains this text (KS and CO). |
status | string | Status contains this text, e.g. Producing, Plugged. |
wellType | string | Well type or class contains this text, e.g. OW, GW, Oil. |
spudFrom | string | Spud date on or after (YYYY-MM-DD). |
spudTo | string | Spud date on or before (YYYY-MM-DD). |
latitude | number | Find wells near this point (with longitude). |
longitude | number | Find wells near this point (with latitude). |
radiusKm | number | Search radius around the point. Default: 5. |
sort | string: api, newest, oldest | Sort by state and API number (default), newest or oldest spud date; nearest first when a point is given. Default: "api". |
groupBy | string: country, state, operator, status, wellType, county, field, spudYear | Return well counts per group instead of wells. |
maxItems | integer | Maximum items to return (1-500). Default: 100. |
Example
curl -X POST https://api.pushbuild.com/oil-gas-wells/run \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"maxItems": 20}'Response
{"count": 20, "truncated": false, "seconds": 1.4, "items": [ { ... } ]}Each call returns up to 500 items. Records that fail validation or are not found are flagged in the items and not charged.
Pricing
Pay only for results returned: $0.80 per 1,000 records. No charge for errors or empty searches.
Use it from Claude, ChatGPT or Cursor
This API is also an MCP server: https://api.pushbuild.com/mcp/oil-gas-wells. Add it to any assistant that supports remote MCP servers, with your key in the X-API-Key header. Same prices. Setup for each app.
Tell us what you need built.
Questions about this API, higher volumes, or a data source you need that we don't cover yet.
hello@pushbuild.comJordan at PushbuildAsk anything. I usually reply within minutes during business hours.
Hi, I'm Jordan. Tell me what you're trying to build, or ask anything about how we work.
Want this data inside your own app or CRM? API integrations and data sync