Automate Your Exports

In today’s oil and gas arena, no one is handing out medals for spreadsheet gymnastics. Data bottlenecks like endless downloads, tedious formatting, and the soul-crushing manual import into reservoir software can drain even the most enthusiastic engineer. That is where the WellDatabase API steps in as your secret weapon, eliminating busywork and putting you back in the analysis driver’s seat. Now, landmen and analysts get to swap herding spreadsheets for tackling the meaningful insights that really move the needle.

Why Automate?

Manual exports are perfectly fine for the occasional report or a quick one-off deep dive. But if you find yourself updating economics models in PHDwin, reserves in Aries, or decline analyses in Whitson+ on a regular basis, let’s just say automation is the friendly colleague who helps reclaim your calendar—and possibly your sanity.

With the WellDatabase API, you can:

• Automate exports using any of our built in export formats

• Schedule recurring jobs so your team always has up-to-date datasets.

• Integrate WellDatabase with your internal tools, creating seamless workflows across your entire organization.

Example: PHDwin

PHDwin simplifies integration by fully supporting the WellDatabase .wdb import format. This format is designed to deliver extensive well, completion, and production data in one efficient transfer. There is no need to worry about partial imports or complicated mapping; your data arrives ready for immediate use in PHDwin.

Below is a concise Python example that exports every well in Reeves County to a neatly zipped .wdb file, so you can spend less time tracking down files and more time focusing on actionable insights.

import httpx
from zipfile import ZipFile
import os

headers = {
    'Content-Type': 'application/json',
    'User-Agent': 'Sample Python Application',
    'Api-Key': 'Your API Key'
}

data = {
    'Filters': {
        'CountyIds': {'Included': [2928]}, # Reeves County
    },
    'ExportFormat': 'wdb',
}

response = httpx.post(
    "https://app.welldatabase.com/api/v2/wells/export",
    headers=headers,
    json=data,
    timeout=httpx.Timeout(5, read=None)
)

if response.status_code != httpx.codes.OK:
    response.raise_for_status()

fileName = "./reeves.zip"
with open(fileName, "wb") as f:
    f.write(response.content)

# Extract the zip file
with ZipFile(fileName, 'r') as zObject:
    zObject.extractall("./extracted")

# Optionally, delete the zip after extraction
os.remove(fileName)

The extracted folder will contain a .wdb file that can be imported directly into PHDwin.

Scheduling Exports

In practice, the real power comes from scheduling exports so your team always has the most current data. WellDatabase provides sample scripts that make this simple.

For example, the Scheduled Bulk Export Python sample demonstrates how to:

• Authenticate against the API

• Kick off an export job

• Save the .wdb file to disk on a recurring schedule (e.g., via cron or Task Scheduler)

This ensures your PHDwin models are always refreshed without requiring manual steps.

Beyond PHDwin

The same workflow can be extended to other platforms. For example:

• Aries reserves system exports

• Whitson+ decline analysis and forecasting imports

• Internal BI dashboards like PowerBI, Tableau, or Spotfire

• Cloud storage syncs (S3, Azure Blob, Google Drive)

If the platform supports file imports or can ingest data from a database, you can wire WellDatabase straight into it with minimal effort.

Putting It All Together

Automating exports goes beyond saving time. It transforms your workflow from a juggling act into a smooth, well-executed machine. With WellDatabase at the center, every tool in your stack pulls together with precision.

Whether you are refining decline curves in PHDwin, finalizing reserves in Aries, or unlocking new insights in Whitson+, the API takes care of the heavy lifting so you can focus on what matters. Say goodbye to spreadsheet rodeos and hello to a process that just works.

Useful Links

• API Help Console – test endpoints directly in your browser.

• Open API Specification – for generating client libraries and exploring the full schema.

• Support Center: Using the API – knowledge base articles and best practices.

• GitHub Code Samples – including the Scheduled Bulk Export Sample.