# California Oil & Gas Well Permit Leads (`scrapesignal_labs/calgem-well-permit-leads`) Actor

Turn official weekly CalGEM drilling, rework, sidetrack, deepening, and abandonment reports into searchable operator and well-activity leads.

- **URL**: https://apify.com/scrapesignal\_labs/calgem-well-permit-leads.md
- **Developed by:** [ScrapeSignal Labs](https://apify.com/scrapesignal_labs) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## California Oil & Gas Well Permit Leads — CalGEM

See where California operators are preparing to drill, rework, deepen, sidetrack, or abandon wells. This Actor automatically converts the newest official CalGEM weekly workbook into searchable operator and well-activity leads—ready for CSV, Excel, JSON, API, or CRM workflows.

The Actor automatically discovers the newest CalGEM Excel workbook and extracts Notices of Intention and issued permits for new drilling, rework, redrilling, deepening, sidetracking, abandonment, and re-abandonment.

### Why this data matters

Well activity creates time-sensitive demand for field services, equipment, engineering, environmental work, plugging and abandonment, remediation, transportation, inspection, insurance, and compliance support. Weekly notices provide an early signal; issued permits provide a stronger near-term activity signal.

### Built for

- oilfield service and equipment companies
- environmental, engineering, and compliance consultants
- plugging, abandonment, remediation, and reclamation contractors
- insurers, infrastructure providers, logistics teams, and market analysts
- recurring operator-monitoring feeds and AI-agent workflows

### What makes it useful

- Automatically finds the newest official weekly workbook.
- Supports the latest week or current year-to-date report.
- Separates submitted notices from issued permits.
- Normalizes new-drill, rework, deepen, sidetrack, abandon, and re-abandon activity.
- Filters by activity, operator, district, field, and well type.
- Includes stable well and permit identifiers for deduplication.

### Example

```json
{
  "recordTypes": ["notices-submitted", "permits-issued"],
  "permitTypes": ["new-drill", "rework", "abandon"],
  "district": "Central",
  "reportScope": "latest-week",
  "maxItems": 500
}
```

### Output

Each item can include the operator, activity and permit type, permit number, well designation, API number, district, field, well type, section/township/range, report date, and a simple opportunity score. Issued permits receive a modest score premium over submitted notices; scores prioritize new drilling, rework, and abandonment events.

### Source and limitations

The source is the California Geologic Energy Management Division's official weekly application and permit workbook. CalGEM notes that an issued permit does not necessarily correspond to a new well because permits also cover abandonment, rework, deepening, and other activity.

The workbook identifies the operator but generally does not contain sales contacts. It should be combined with operator websites, CRM enrichment, or other lawful business-data sources for outreach. This Actor is independently maintained and is not affiliated with or endorsed by CalGEM or the State of California.

# Actor input Schema

## `recordTypes` (type: `array`):

Choose submitted work notices, issued permits, or both.

## `reportScope` (type: `string`):

Use the newest weekly sheets or the larger current year-to-date sheets.

## `permitTypes` (type: `array`):

Leave empty for all activities.

## `district` (type: `string`):

Exact or partial district name, for example Central or Northern.

## `operatorQuery` (type: `string`):

Case-insensitive operator company search.

## `fieldQuery` (type: `string`):

Case-insensitive field-name search, for example Midway-Sunset.

## `wellType` (type: `string`):

Case-insensitive well-type search, such as Oil & Gas, Steamflood, or Waterflood.

## `maxItems` (type: `integer`):

Stop after saving this many matching well-activity records.

## `sourceWorkbookUrl` (type: `string`):

Optional CalGEM .xlsx URL. Leave blank to discover the latest official workbook automatically.

## Actor input object example

```json
{
  "recordTypes": [
    "notices-submitted",
    "permits-issued"
  ],
  "reportScope": "latest-week",
  "permitTypes": [],
  "district": "",
  "operatorQuery": "",
  "fieldQuery": "",
  "wellType": "",
  "maxItems": 500,
  "sourceWorkbookUrl": ""
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesignal_labs/calgem-well-permit-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapesignal_labs/calgem-well-permit-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call scrapesignal_labs/calgem-well-permit-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesignal_labs/calgem-well-permit-leads"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/eZAjtTeWUiXUmxpuH/builds/mqJSPK55mcRjBO92x/openapi.json