API Number Lookup Tool
Search available well production records using an API-10, API-12, or API-14 identifier. Review the reported operator, source periods, and monthly oil, gas, and water values when a match is available.
Need this data in a production workflow?
Compare API limits, history, and support before you build.
Search by API Number
Look up a well by its API number and get the operator, well name, state, and the monthly oil and gas the operator reported to the state regulator.
Try a real one: 42-161-00101-00-00 — QUANICO OIL & GAS, INC., “WILSON, W. D. & WIFE”, Texas, 397 monthly filings back to 1993.
What is an API Number?
The historical API Well Number has a 10-digit state, county, and well-code core. A 12-digit form adds a wellbore code, and the familiar historical 14-digit form adds an event-sequence field. Source systems and historical records do not all expose the same length.
Need the full code table and source caveats? Read the sourced API Well Number format guide.
14-Digit Format Breakdown
SSCCCNNNNNSSEEExample: 42-329-34567-00-00
Texas (42), Midland County (329), Well #34567, Original bore (00), Original event sequence (00)
Why Use API Number Lookup?
Production Records
Review the operator, well name, reporting periods, sources, and monthly production held for a matching identifier.
Normalized Input
Paste API-10, API-12, or API-14 with or without dashes. The lookup validates and normalizes the identifier before querying.
Source-Aware Results
Monthly rows retain their source label and period so you can evaluate provenance and reporting freshness.
Honest Missing Values
An unreported value remains unknown instead of being converted to zero, preserving the distinction for analysis.
Explicit No-Record State
If no production record is held, the page says that directly without claiming the well itself does not exist.
Sourced Format Guide
Decode historical API and successor US Well Number fields using regulator and standards-body references.
Who Uses API Number Lookup?
Landowners & Mineral Rights Owners
Match identifiers from lease or royalty documents to available reported production without treating the lookup as a payment audit.
Energy Analysts & Investors
Review available monthly filings and source periods before incorporating a well into portfolio research.
Petroleum Engineers
Join available production histories to separately sourced technical, completion, and regulator datasets.
Compliance & Legal Teams
Use the identifier as a join key, then verify compliance and legal conclusions against the responsible regulator.
Access This Data via API
Dereference an API number programmatically. Returns the operator, well name, state, and every monthly oil, gas and water figure the operator filed with the state regulator. A month with no reported value comes back as null, not as zero.
/v1/well-production/wells/:api_numbercurl -X GET "https://api.oilpriceapi.com/v1/well-production/wells/:api_number"
Sample Response
{
"status": "success",
"data": {
"api_number": "42161001010000",
"operator": "QUANICO OIL & GAS, INC.",
"well_name": "WILSON, W. D. & WIFE",
"state": "TX",
"count": 397,
"data": [
{
"period": "1993-01",
"oil_bbl": 5,
"gas_mcf": 1,
"water_bbl": 0,
"boe": 5,
"days_producing": 31,
"source": "tx_rrc"
}
]
}
}Frequently Asked Questions About API Number Lookup
An API well number is the historical US identifier whose 10-digit core contains a state or pseudo-state code, county code, and unique well code. Source systems commonly expose 10-, 12-, or 14-digit forms. The PPDM US Well Number is the official successor to the historical API standard.
In the historical API-14 format, the first 2 digits identify the surface state or pseudo-state, the next 3 identify the surface county or equivalent, the next 5 are the unique well code, digits 11 and 12 identify the wellbore or sidetrack, and the last 2 are an event-sequence field. Texas is API code 42; Oklahoma is API code 35. See the linked API Well Number guide for the complete sourced code table.
API numbers are public record and can be found on: state oil and gas commission websites, well permit applications, drilling completion reports, production records, mineral lease documents, and well file databases. If you know the well location, you can search geographic databases. If you know the operator name, you can filter their permits. Our tool allows you to search by API number or browse permits by location.
When a matching production record is available, OilPriceAPI returns the reported operator, well name, state, first and latest reporting periods, source labels, cumulative reported oil and gas, and monthly oil, gas, water, BOE, and days-producing values. This lookup does not claim to return a permit record.
The historical API format uses a shared state and pseudo-state code list, but regulator implementations and record lengths vary. The first fields describe the surface location, even if the bottom-hole location crosses a boundary. Keep identifiers as text so leading zeroes are preserved.
Use the newest period and the source labels returned with the monthly production records. Reporting cadence and lag depend on the source regulator. OilPriceAPI does not replace a missing source period with today's date or describe an unavailable month as zero.
The browser lookup is available without signup. Programmatic access to the well-production endpoint requires an API key and the applicable dataset entitlement; review current product and plan details before building a production workflow.
It returns the well's monthly production record as filed with the state regulator: operator name, well name, state, the first and most recent month reported, the number of monthly filings, cumulative reported oil and gas, and the month-by-month oil, gas, water and days-producing figures. Well-level production coverage is deepest in Texas. If we hold no production filings for an API number, the lookup says so — it does not return a blank or a zero.
Because a dash and a zero mean different things and we will not blur them. A dash means the operator reported no value for that month. A zero means the operator reported that the well produced nothing. Showing an unknown as a zero would be silently actionable — you could act on a production decline that never happened — so we never do it. The production sparkline breaks the line across unreported months for the same reason.
No. It means we hold no monthly production filings for it. The well may be permitted but never have reported production, or it may be in a state whose well-level production we do not yet carry. A drilling permit is not a production record, and we do not present one as the other.