AFE Leaks
Get API Token

AFE Leaks API Documentation

Complete reference for integrating upstream cost data and SEC financials into your applications. RESTful endpoints with JSON responses and comprehensive filtering.

🔑 Get API Token

New: MCP Server for AI Clients

Connect Claude Desktop, Cursor, or Claude Code directly to AFE Leaks data. Ask questions naturally and your AI calls our 14 database tools automatically.

Setup Guide

New: OData v4 Support

All upstream data endpoints now support OData v4 protocol for seamless integration with Excel, Power BI, and other business intelligence tools. Use $filter, $select, $orderby, and more.

Learn More

📋 Table of Contents

Getting Started

API Endpoints

🔐 Authentication

🔑 API Key (Recommended)

Permanent API keys for integrations, scripts, and external tools. No expiration or refresh needed. 

X-API-Key: afe_your_api_key_here

Get your key: Login to API Portal

🔥 Firebase Token

Session-based tokens for web applications. Tokens expire and require refresh. 

Authorization: Bearer <firebase_token>

Get token: Via Firebase Auth in web applications

Need an API Token?

Login to get your personal API access token for authentication.

Get API Token →

🌐 Base URL 

https://api.afeleaks.com

All API endpoints are relative to this base URL.

🛢️ Upstream Data Endpoints

Access well costs, production data, and completion details from 102,000+ wells

💰

Cost Data

Well-level cost summaries

GET /api/cost-data

Returns summarized cost data by well (API-level)

GET /api/cost-breakdown

Returns line-item level cost details

🔍

Wells & Metadata

Well information and details

GET /api/wells

General well metadata with dynamic column selection

GET /api/locations

Well-path or location data (WKT format)

📊

Production & Revenue

Production and revenue data

GET /api/production

Production records by well and date

GET /api/product

Product revenue data with well information

🔧

Technical Details

Completion and geology data

GET /api/casing

Casing design records

GET /api/formations

Formation tops and geology records

GET /api/surveys

Directional survey records

GET /api/welltests

Flow/pressure test data

🏭

Vendor & Files

Vendor costs and regulatory files

GET /api/vendor-costs

Vendor cost data with well information

GET /api/files

Regulatory file links and documents

⚙️ Common Parameters

Pagination

limit Max records (default: 100, max: 10,000)
offset Skip N records for pagination

Well Filters

API API well number
operator Operator name
state State
county County
reservoir Reservoir/formation

Location Filters

lease Lease name
leaseNum Lease number
wellNum Well number
district Regulatory district

Date Range Filters

spudDateMin Min spud date (YYYY-MM-DD)
spudDateMax Max spud date (YYYY-MM-DD)
updateDateMin Min update date (YYYY-MM-DD)
updateDateMax Max update date (YYYY-MM-DD)

📊 Column Reference

Detailed descriptions of all columns returned by upstream data endpoints

🔍 og_data (Well Metadata)

Note: The /api/wells endpoint supports dynamic column selection using the columns parameter. You can specify which columns to return (e.g., ?columns=API,operator,state,spudDate) from any of the columns listed below.

API – 10- or 12-digit API well number (unique well identifier)
api12 – 12-digit API number (alternate format)
api14 – 14-digit API number (alternate format)
lease – Lease name
leaseNum – Lease number
wellNum – Well number
district – Regulatory district
county – County name
oilGas – Well type (oil/gas/both)
field – Field name
fieldNum – Field number
spudDate – Date well was spudded (drilling started)
lastSpud – Date of last spud (if re-entered)
operator – Operator name (current or at time of record)
operator_clean – Cleaned operator name (standardized)
compDate – Completion date
first_production – Date of first production
last_production – Date of last production
reservoir – Cleaned/standardized reservoir name
lateral – Lateral length (ft)
tvd – True vertical depth (ft)
md – Measured depth (ft)
perf_top – Top of perforated interval (ft)
perf_bottom – Bottom of perforated interval (ft)
perf_interval – Perforated interval length (ft)
depth – Total depth (ft)
fluid – Total fluid used (gallons)
proppant – Total proppant used (lbs)
prop_per_ft – Proppant per foot (lbs/ft)
location – Well location (legal description or lat/lon)
state – State
plug_date – Plugging date
casing_design – Casing design description
update_date – Date of last update
📊 product (Production/Revenue Data)
TaxpayerNumber – Primary taxpayer number
TaxpayerName – Primary taxpayer name
TaxSubType – Tax subtype (if applicable)
date – Production/revenue date
leaseNum – Lease number
district – Regulatory district
SecondaryTaxpayerNumber – Secondary taxpayer number
SecondaryTaxpayerName – Secondary taxpayer name
APIGravity – API gravity (oil quality measure)
volume – Product volume (e.g., barrels, mcf, etc.)
value – Product value (USD)
marketing – Marketing adjustment or revenue
product – Product type (oil, gas, NGL, etc.)
leaseOil – Lease oil production (bbl)
leaseGas – Lease gas production (mcf)
update_date – Date of last update
💰 cost_data_aggregate (Cost Data Summary)
API – API well number
type – AFE/Actual
capex – Total capital expenditure (USD)
component – Cost component (e.g., drilling, completion)
update_date – Date of last update
operator – Operator name (cleaned)
state – State
county – County
reservoir – Reservoir name
lease – Lease name
wellNum – Well number
spudDate – Spud date
fp_year – First production year
perf_interval – Perforated interval (ft)
tvd – True vertical depth (ft)
afedate – AFE date
💸 cost_breakdown_details (Cost Line Items)
API – API well number
cost_type – AFE/Actual
type – Cost type (e.g., material, service)
component – Cost component (e.g., casing, cement)
code – Cost code or identifier
category – Cost category (e.g., drilling, completion)
value – Cost value (USD)
operator – Operator name (cleaned)
state – State
county – County
reservoir – Reservoir name
lease – Lease name
wellNum – Well number
spudDate – Spud date
fp_year – First production year
perf_interval – Perforated interval (ft)
tvd – True vertical depth (ft)
afedate – AFE date
Note: No update_date column
🔧 casing_data (Casing Design)
API – API well number
type – Casing string type (e.g., surface, production)
segment – Casing segment/interval
hole_size – Hole size (inches)
hole_depth – Hole depth (ft)
size – Casing size (inches)
weight – Casing weight (lbs/ft)
grade – Casing grade
update_date – Date of last update
🛢️ prod_data (Production Data)
API – API well number
date – Production date
oil – Oil produced (barrels)
gas – Gas produced (MCF)
water – Water produced (barrels)
update_date – Date of last update
📍 locs (Well Locations)
API – API well number
geometry_wkt – Well geometry/location (WKT format)
update_date – Date of last update
📐 survey_data (Directional Surveys)
API – API well number
MD – Measured depth (ft)
TVD – True vertical depth (ft)
Inclination – Inclination (degrees)
Azimuth – Azimuth (degrees)
DogLegSeverity – Dog leg severity
N – North coordinate
E – East coordinate
VS – Vertical section
update_date – Date of last update
🧪 test_data (Well Tests)
API – API well number
dateTst – Test date
oilD – Oil rate (barrels/day)
gasD – Gas rate (MCF/day)
waterD – Water rate (barrels/day)
chokeSize – Choke size
tubingPressure – Tubing pressure (psi)
casingPressure – Casing pressure (psi)
testType – Test type
testHours – Test duration (hours)
reservoir – Reservoir tested
update_date – Date of last update
🏔️ formation_data (Formation Tops)
API – API well number
reservoir – Formation/reservoir name
tvd – Top TVD (ft)
md – Top MD (ft)
update_date – Date of last update
📄 file_links (Regulatory Files)
API – API well number
Form – File/form type
url – File download URL
update_date – Date of last update
🏭 vendor_costs (Vendor Cost Data)
API – API well number
date – Cost date
vendor – Vendor name
code – Vendor cost code
type – Cost type
description – Cost description
note – Additional notes
cost – Cost amount (USD)
link – Reference link
cost_type – AFE/Actual
rig – Rig information
phase – Project phase
Note: Joined with og_data for well metadata

💼 SEC Financial Data Endpoints

Access SEC XBRL financial data from 10-K and 10-Q filings with comprehensive filtering

📄

Submissions

Filing metadata

GET /api/financials/sub

Company submission metadata (filing information)

🎨

Presentation

Display information

GET /api/financials/pre

Presentation/display info for financial statement elements

🔢

Numeric Data

Financial values

GET /api/financials/num

Numeric financial data values from SEC filings

📝

Text Data

Narrative content

GET /api/financials/text

Text/narrative financial data

GET /api/financials/textbig

Large text content (MD&A, footnotes) in chunks

📊 SEC Financial Data Tables

📋 sub (Company Submissions)
cik – Central Index Key (company identifier)
name – Company name
adsh – Accession number (filing identifier)
sic – Standard Industrial Classification
fye – Fiscal year end (MMDD)
form – SEC form type (10-K, 10-Q, etc.)
period – Reporting period end date
filed – Filing date
accepted – SEC acceptance date
prevrpt – Previous report indicator
detail – Detail level
instance – XBRL instance document
🎨 pre (Presentation Data)
adsh – Accession number
tag – XBRL tag name
version – Taxonomy version
plabel – Presentation label
negating – Negating multiplier
stmt – Statement type (BS, IS, CF, EQ)
inpth – Presentation path
rfile – R file reference
rorder – Report order
tbl – Table identifier
🔢 num (Numeric Financial Data)
adsh – Accession number
tag – XBRL tag name
version – Taxonomy version
enddate – Period end date
qtrs – Number of quarters
uom – Unit of measure
value – Numeric value
footnote – Footnote reference
filed – Filing date
axis – Dimensional axis
segment – Dimensional segment
📝 text (Text Financial Data)
adsh – Accession number
tag – XBRL tag name
version – Taxonomy version
enddate – Period end date
qtrs – Number of quarters
value – Text value
footnote – Footnote reference
filed – Filing date
axis – Dimensional axis
segment – Dimensional segment
📄 textbig (Large Text Content)
adsh – Accession number
tag – XBRL tag name
version – Taxonomy version
enddate – Period end date
qtrs – Number of quarters
chunk_order – Chunk sequence number
value – Large text chunk
footnote – Footnote reference
filed – Filing date
axis – Dimensional axis
segment – Dimensional segment

⚡ OData v4 Access

All upstream data endpoints support OData v4 protocol, enabling direct integration with Excel, Power BI, Tableau, and other business intelligence tools. Query data using standard OData operators like $filter, $select, $orderby, $top, and $skip.

Base URL

https://api.afeleaks.com/api/odata/

Authentication

OData endpoints use HTTP Basic Authentication. Use apikey as the username and your API key as the password.

Excel / Power Query: When prompted for credentials, select "Basic" authentication, enter apikey as username, and paste your API key as the password.

Available Endpoints

Endpoint Description
Upstream Data (Wells with Cost Data)
/api/odata/Wells Well metadata (API, operator, county, state, reservoir, depths, etc.)
/api/odata/CostData Summarized well cost data (AFE and Actual totals)
/api/odata/CostBreakdown Detailed line-item cost breakdowns
/api/odata/Production Monthly production data (oil, gas, water volumes)
/api/odata/Casing Casing string details and specifications
/api/odata/Locations Well location coordinates
/api/odata/Surveys Directional survey data
/api/odata/WellTests Well test results and measurements
/api/odata/Formations Formation tops and geological data
/api/odata/Files Available document files for wells
Product Revenues & Vendor Costs
/api/odata/Product Product revenues by lease (oil, gas, NGL sales and GPT costs)
/api/odata/VendorCosts Vendor cost data with breakdown by phase, type, and vendor
SEC Financial Data (XBRL)
/api/odata/FinancialsSub SEC filing submissions metadata
/api/odata/FinancialsNum Raw XBRL numeric values from filings
/api/odata/FinancialsPre Presentation linkbase (statement line items)
/api/odata/FinancialsText Text/footnote data from filings
/api/odata/FinancialsTextBig Large text blocks (chunked for performance)
/api/odata/FinancialsStandardized Standardized financial metrics (revenue, EBITDA, etc.)

Query Examples

Filter wells by state:

/api/odata/Wells?$filter=state eq 'TX'

Filter by operator and select specific columns:

/api/odata/Wells?$filter=operator_clean eq 'DIAMONDBACK'&$select=API,wellName,county,reservoir

Get production with pagination:

/api/odata/Production?$top=1000&$skip=0&$orderby=prod_date desc

Filter by multiple conditions:

/api/odata/Wells?$filter=state eq 'TX' and county eq 'REEVES' and perf_interval gt 5000

Using with Excel Power Query

  1. Open Excel and go to Data → Get Data → From Other Sources → From OData Feed
  2. Enter the OData URL: https://api.afeleaks.com/api/odata/Wells
  3. When prompted for authentication, select Basic
  4. Enter apikey as the username
  5. Paste your API key as the password
  6. Click Connect to load the data

Tip: For large datasets, use $filter to narrow down results before loading (e.g., filter by state or operator).

💡 API Examples

Get Cost Data for Texas Wells

🔑 Using API Key

curl -H "X-API-Key: afe_your_key" \
  "https://api.afeleaks.com/api/cost-data?state=TX&limit=100"

🔥 Using Firebase Token

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.afeleaks.com/api/cost-data?state=TX&limit=100"

Get Production Data with Pagination

🔑 Using API Key

curl -H "X-API-Key: afe_your_key" \
  "https://api.afeleaks.com/api/production?limit=1000&offset=5000"

🔥 Using Firebase Token

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.afeleaks.com/api/production?limit=1000&offset=5000"

Get Financial Data for Specific Company

🔑 Using API Key

curl -H "X-API-Key: afe_your_key" \
  "https://api.afeleaks.com/api/financials/num?cik=0000078003&form=10-K"

🔥 Using Firebase Token

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.afeleaks.com/api/financials/num?cik=0000078003&form=10-K"

📝 Programming Language Examples

📊 R (with API Key) 

library(httr)
library(jsonlite)

# Using permanent API key
api_key <- "afe_your_generated_key_here"

resp <- GET(
  url = "https://api.afeleaks.com/api/wells",
  query = list(limit = 10, state = "TX"),
  add_headers(`X-API-Key` = api_key)
)

if (status_code(resp) == 200) {
  data <- content(resp, "parsed")
  wells_df <- data$data
} else {
  print(paste("Error:", status_code(resp)))
}

🐍 Python (with API Key) 

import requests
import pandas as pd

# Using permanent API key
api_key = "afe_your_generated_key_here"
headers = {"X-API-Key": api_key}

response = requests.get(
    "https://api.afeleaks.com/api/wells",
    params={"limit": 10, "state": "TX"},
    headers=headers
)

if response.status_code == 200:
    data = response.json()
    wells_df = pd.DataFrame(data["data"])
else:
    print(f"Error: {response.status_code}")

⚡ JavaScript (with API Key) 

// Using permanent API key
const apiKey = "afe_your_generated_key_here";

fetch('https://api.afeleaks.com/api/wells?limit=10&state=TX', {
  headers: {
    'X-API-Key': apiKey
  }
})
.then(response => response.json())
.then(data => {
  console.log(`Retrieved ${data.data.length} wells`);
  console.log('Wells:', data.data);
})
.catch(error => console.error('Error:', error));

📈 Excel/Power BI 

// Power Query M code
let
    apiKey = "afe_your_generated_key_here",
    url = "https://api.afeleaks.com/api/wells?limit=1000",
    headers = [#"X-API-Key" = apiKey],
    response = Web.Contents(url, [Headers = headers]),
    json = Json.Document(response),
    data = json[data],
    table = Table.FromList(data, Splitter.SplitByNothing(), null, null, ExtraValues.Error)
in
    table

🤖 MCP Server AI Client Integration

Corporate and API subscribers can connect AI tools directly to AFE Leaks data using the Model Context Protocol (MCP). Once connected, just ask questions naturally — your AI calls our database tools automatically.

Supported Clients

Claude Desktop
Cursor
Claude Code

Works with any MCP-compatible client.

Setup Instructions

Claude Desktop Settings → Developer → Edit Config 

{
  "mcpServers": {
    "afeleaks": {
      "url": "https://mcp.afeleaks.com/sse?api_key=YOUR_API_KEY"
    }
  }
}

Cursor Settings → MCP Servers → Add Server

Type
SSE
URL
https://mcp.afeleaks.com/sse?api_key=YOUR_API_KEY

Claude Code Terminal command 

claude mcp add afeleaks --transport sse "https://mcp.afeleaks.com/sse?api_key=YOUR_API_KEY"

Available Tools (14 total)

search_operators Fuzzy operator name search
query_well_costs Well cost data (AFE vs Actual, grouped/aggregated)
query_production Oil/gas/water production data
query_financials SEC financials for 10 key E&Ps (EOG, DVN, OXY, etc.)
compare_costs Side-by-side cost comparisons across operators/basins/years
lookup_well Single well detail (metadata + costs + production)
get_basin_info Basin geographic reference data
query_well_tests IP / well test results
query_cost_details Line-item cost breakdowns (casing, stimulation, cement, etc.)
query_formations Formation tops / reservoir depths
query_casing Casing program details
query_surveys Directional survey data
search_xbrl_companies Find companies in SEC database (~146 companies)
query_xbrl_raw Raw XBRL query for any SEC filing

Example Prompts

Once connected, just ask your AI client questions like these:

"What's the average well cost in the Delaware Basin since 2023?"

"Compare Diamondback vs Devon drilling costs for 2-mile laterals"

"Show me EOG's revenue and EBITDA trend over the last 2 years"

"Look up well 42-461-40916"

"What formations is Pioneer drilling in Midland County?"

"Cheapest wells drilled in Reeves County in 2024"

Requirements

  • Corporate or API subscription tier
  • API key (generate from Account Settings, starts with afe_)
  • Subject to plan-specific rate limits, quotas, and endpoint restrictions
  • API credentials are confidential and may not be shared or redistributed

🚀 Quick Start Guide

Get up and running with the AFE Leaks API in minutes

1

Get Your API Credentials

Choose your authentication method and get your credentials.

🔑 Generate API Key (Recommended) → 🔥 Get Firebase Token →
2

Make Your First Request

Test the API with a simple request to get well data.

🔑 With API Key

curl -H "X-API-Key: afe_your_key" \
  "https://api.afeleaks.com/api/wells?limit=10"

🔥 With Firebase Token

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.afeleaks.com/api/wells?limit=10"
3

Integrate Into Your Workflow

Use the API clients or build custom integrations for your specific needs.

Upstream Client → Financial Client →

Need Help with Integration?

Our team can help you integrate AFE Leaks data into your existing systems and provide custom solutions.

Contact Support Consulting Services