A guide to reading drilling permit API numbers accurately
Drilling records often contain several identifiers that look interchangeable. A permit number, API number, lease number, well name, and operator reference may all appear in the same file, yet each serves a different purpose. Treating them as the same identifier can lead to incorrect well matches, duplicated records, or a mistaken view of a property’s drilling history.
The American Petroleum Institute number, commonly called an API number, is primarily a standardized well identifier. It is designed to identify a particular wellbore and, in extended formats, sidetracks and completion events. A drilling permit number is issued by a state regulatory agency and usually tracks the authorization to drill rather than the well throughout its entire life.
For analysts, landmen, mineral-rights investors, and landowners, the distinction matters. Reliable research requires reading the API structure, checking the issuing jurisdiction, and comparing the identifier against location, operator, formation, and permit status. A clean workflow can turn a confusing permit export into dependable development intelligence.
What an API number identifies
A conventional API well number begins with a geographic code. The first two digits identify the state, and the next three identify the county or equivalent jurisdiction. The final five digits generally identify the well within that state and county. Together, these first ten digits are often called the API-10 or original well identifier.
For example, an identifier beginning with a state code followed by a county code can provide an immediate geographic clue, but it should not be treated as a substitute for coordinates. County boundaries, offshore areas, tribal jurisdictions, and agency coding practices can create exceptions. The code is a useful validation signal, not a complete location record.
Longer API forms add information about a wellbore or completion. The additional digits may identify a sidetrack, recompletion, or other event associated with the original well. This means two records can share the same first ten digits while representing different well paths or regulatory events.
Reading the digit groups
The common 14-digit convention can be read as four groups: state, county, well sequence, and event information. The first group contains two digits, the second contains three, the third contains five, and the final four are commonly divided into a two-digit sidetrack code and a two-digit completion or event code.
The 10-digit base identifies the original well. Digits 11 and 12 are frequently used for a sidetrack or wellbore extension, while digits 13 and 14 can identify a completion or event. A base code ending in “00” in the sidetrack position may represent the original wellbore, although users should verify the convention used by the relevant regulator or data provider.
Formatting can obscure the structure. Some systems remove leading zeroes, insert hyphens, or store the number as a numeric field rather than text. An API ending in zero can be damaged when a spreadsheet automatically converts it to a number. Preserve the identifier as text and retain every digit when importing or exporting records.
API numbers versus permit numbers
A permit number answers a different question from an API number. It usually tells you which application or authorization the regulator approved, while the API number is intended to follow the well identity. A single well may have a permit, a drilling status, a completion record, a plugging record, and later production reports that all use related but different references.
Permit numbering systems vary substantially by state. Some include a year, district, county, sequential application number, or permit type. Others use a compact sequence with little visible geographic meaning. A permit number may also be reused in agency-specific reports or replaced when an application is amended, transferred, or reissued.
When reviewing a record, label the fields explicitly rather than assuming that the longest number is the API. Look for names such as “API,” “API-U,” “well number,” “permit number,” “file number,” or “application ID.” If a source provides only one identifier, compare it with the agency’s documentation before assigning it a meaning.
| Identifier | Primary purpose | Typical persistence | Best cross-check |
|---|---|---|---|
| API-10 | Identifies the original well | Usually follows the well across records | State, county, coordinates |
| API-12 | Identifies a wellbore or sidetrack | Persists for that well path | Parent API and directional data |
| API-14 | Distinguishes completion or event records | Depends on reporting convention | Completion, production, or status |
| Permit number | Tracks a regulatory application or authorization | May change or be replaced | Permit date, operator, status |
| Lease or tract number | Identifies mineral or surface rights | Follows an agreement or parcel | Legal description and owner |
How to validate a permit record
Start by normalizing the API number. Remove unnecessary punctuation only after saving the original value, then restore the expected digit length with leading zeroes. Keep separate fields for the raw identifier, normalized API-10, API-12, and API-14 forms. This approach makes both auditing and later reconciliation easier.
Next, compare the code with the reported county and coordinates. A mismatch does not automatically prove an error: a well may be near a county line, use an offshore code, or appear in a neighboring county’s permit dataset. Still, an unexplained mismatch deserves investigation before the record is used in valuation, title work, or development analysis.
Check the operator, well name, lease, formation, permit date, and current status as a group. Names can change after an acquisition, and operators may use abbreviations or punctuation inconsistently. Location and API relationships are generally stronger matching evidence than text alone, particularly when multiple wells have similar names.
Regulatory records should remain the authoritative source for legal status. Commercial mapping and reporting platforms can make cross-source research faster by bringing permits, wells, pipelines, leases, mineral rights, and property information into a common geographic view. Shale Navigator’s interactive mapping platform can help users inspect these relationships spatially while retaining the need to verify material findings with the applicable agency.
Common sources of inaccurate matches
Duplicate wells are a frequent problem in permit research. A horizontal well may appear under an initial permit, a revised permit, a drilling report, and a production record. If a workflow matches on well name alone, it can count one development multiple times or attach production to the wrong permit.
Sidetracks create another source of confusion. The shared API-10 indicates a relationship, but the extended API can distinguish the original wellbore from a later path. In a pad development, several wells may share a surface location or lease while having different API identifiers and separate permits.
Data-entry errors also matter. Transposed digits, missing zeroes, incorrect county codes, and copied API numbers can move a record to a different well. A practical quality check should flag API numbers with the wrong length, impossible state codes, duplicate full identifiers with conflicting locations, and records where the API county conflicts with the reported county.
Shale geology adds another interpretive issue. A well’s formation label may be updated, generalized, or reported differently by separate sources. Regional context can change as development expands; for example, research on the Deep Basin’s rise illustrates why play boundaries and development narratives should not be inferred from one field in one permit file.
A practical review workflow
Create a source hierarchy before comparing records. Use the state oil and gas regulator for permit status, official API assignments, well events, and legal reporting. Use county or land records for parcel and ownership questions, and use commercial datasets for discovery, visualization, and cross-reference. Record the source date because permit and production statuses can change.
A repeatable workflow can follow these steps:
- Preserve the original API and permit strings before cleaning or reformatting them.
- Parse the API into state, county, well sequence, sidetrack, and event components where supported.
- Match the normalized identifier against coordinates, operator, well name, lease, and formation.
- Separate applications, amendments, wellbores, completions, and production records instead of counting them as one category.
- Save the source agency, retrieval date, and any assumptions used to resolve a discrepancy.
For large datasets, automated validation is useful, but exceptions should be reviewed manually. A script can identify malformed lengths and duplicate identifiers; it cannot always determine whether an agency intentionally assigned a special code. Keep a change log when correcting records so another analyst can reproduce the decision.
Using verified identifiers in development research
Accurate API interpretation improves more than permit searches. It supports offset analysis, spacing reviews, production comparisons, mineral-rights screening, infrastructure planning, environmental review, and title-related research. Once the well identity is stable, users can connect it to nearby pipelines, roads, leases, surface parcels, and other development constraints.
The strongest analysis combines identifier accuracy with geographic context. A permit that appears active may be irrelevant to a target tract if its surface location, bottomhole location, or unit boundary lies elsewhere. Conversely, nearby permits with different operators may reveal gathering infrastructure, competing development, or a broader play trend.
Before relying on a result in a transaction or formal report, verify the latest agency record and preserve supporting evidence. Users who need expanded datasets, historical coverage, or additional reporting tools can review subscription options for deeper research workflows.
A carefully read API number is a starting point, not a final answer. Preserve its formatting, distinguish it from the permit identifier, validate it against geography and regulatory records, and document every reconciliation. Those habits make drilling data easier to trust and turn scattered permit files into a defensible view of shale development. Start with a verified well identifier and use the available mapping and reporting tools to investigate the surrounding opportunity with greater precision.