# California CEQA Construction Project Leads (`scrapesignal_labs/california-ceqa-project-leads`) Actor

Find planned California construction and development projects in official CEQAnet filings—with applicants, consultants, contacts, locations, documents, and opportunity scores.

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

## Pricing

from $3.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 CEQA Construction Project Leads

Find planned California construction, infrastructure, energy, housing, and commercial projects while they are still moving through environmental review. This Actor turns official CEQAnet filings into ranked, source-linked leads with applicants, consultants, agency contacts, project locations, and documents.

This Actor searches the California Governor's Office of Land Use and Climate Innovation CEQAnet database, normalizes the official CSV data, classifies each project, calculates an opportunity score, and optionally visits each project page to collect all published agency, consultant, and project-applicant contacts and document links.

### Why this is different from a permit list

CEQA filings can appear during planning and environmental review—before a building permit or construction award exists. That makes them useful for identifying projects early enough to influence vendor selection, partnerships, bids, insurance, financing, and professional-service engagements.

Use the filing stage, recency, project category, location, applicant, consultant, and contactability filters to separate high-intent opportunities from routine notices.

### Built for

- contractors, subcontractors, surveyors, and material suppliers
- environmental, civil, traffic, geotechnical, and planning consultants
- solar, battery, utility, water, telecom, and infrastructure vendors
- commercial real-estate, title, insurance, legal, and finance teams
- market-intelligence products, CRMs, AI agents, and scheduled lead feeds

### Why this data is useful

CEQA filings often appear while projects are being planned, reviewed, or approved—before many construction and vendor decisions have been finalized. They can surface potential demand for:

- environmental, civil, geotechnical, traffic, and planning consultants
- general contractors, specialty subcontractors, surveyors, and material suppliers
- commercial real-estate, title, insurance, legal, and financing teams
- solar, water, utility, telecom, and infrastructure vendors
- market-intelligence and lead-generation workflows

### What you get

Each result can include:

- SCH number, project title, filing type, and received date
- project description and automatically detected categories
- 0–100 lead score with human-readable scoring signals
- lead agency and primary official contact
- every published project applicant, consultant, and agency contact
- emails, phone numbers, job titles, organizations, and addresses
- city, county, coordinates, acreage, parcels, highways, and waterways
- development type, local action, project issues, and review dates
- official attachment URLs and a direct CEQAnet source link

### Recommended inputs

#### Latest high-intent statewide projects

```json
{
  "lookbackDays": 30,
  "maxItems": 100,
  "enrichDetails": true,
  "sortBy": "leadScore"
}
```

#### Los Angeles housing and commercial leads

```json
{
  "lookbackDays": 90,
  "county": "Los Angeles",
  "projectCategories": ["housing", "commercial"],
  "minimumLeadScore": 45,
  "requireContactEmail": true,
  "maxItems": 250
}
```

#### Solar and battery-storage pipeline

```json
{
  "lookbackDays": 365,
  "keywords": ["solar", "battery", "energy storage"],
  "documentTypes": ["NOP", "EIR", "MND", "NOD"],
  "enrichDetails": true,
  "maxItems": 500
}
```

### CEQA stages

- `NOP`: Notice of Preparation—a useful early signal for a planned Environmental Impact Report.
- `EIR`, `MND`, `NEG`, `SCA`: active environmental-review documents.
- `NOC`, `NOI`: completion or intent notices associated with review activity.
- `NOD`: Notice of Determination, generally a later approval-stage signal.
- `NOE`: Notice of Exemption. It is available as an option but excluded from the default selection because many NOE records represent smaller or routine work.

### Lead score

The score is a transparent prioritization aid, not a prediction or legal conclusion. It weights filing stage, recency, project detail, location data, development information, contactability, and whether an applicant or consultant is identified. The contributing reasons are returned in `leadSignals`.

### Scheduling and change monitoring

For a recurring lead feed, schedule the Actor daily with a short lookback window. Use `recordId` as the stable deduplication key in Airtable, a CRM, a webhook consumer, or an Apify automation.

### Data source and limitations

Data comes from the public [California CEQAnet portal](https://ceqanet.lci.ca.gov/). CEQAnet states that its database is not comprehensive because not every CEQA document is submitted to the State Clearinghouse. A filing is not proof that a project will proceed, receive approval, or purchase any particular product or service. Verify important facts in the linked official filing.

This Actor is independently maintained and is not affiliated with or endorsed by the State of California, CEQAnet, or the Governor's Office of Land Use and Climate Innovation. Use public contact information responsibly and comply with applicable outreach, privacy, and anti-spam laws.

# Actor input Schema

## `lookbackDays` (type: `integer`):

Search filings received during the last N days. Ignored when Received from is supplied.

## `receivedFrom` (type: `string`):

Optional exact start of the received-date window (YYYY-MM-DD).

## `receivedTo` (type: `string`):

Optional end of the received-date window (YYYY-MM-DD). Defaults to today.

## `documentTypes` (type: `array`):

Keep selected filing stages. Defaults focus on higher-intent planning and approval signals while excluding routine exemption notices.

## `county` (type: `string`):

Exact California county name, for example Los Angeles or San Diego. Leave blank for statewide.

## `city` (type: `string`):

Exact project city. Leave blank for all cities.

## `leadAgency` (type: `string`):

Exact CEQAnet lead-agency name. Leave blank for every agency.

## `keywords` (type: `array`):

Keep projects whose title, description, applicant, agency, development type, or issues contain at least one keyword.

## `projectCategories` (type: `array`):

Keep projects in selected automatically classified categories. Leave empty for all categories.

## `minimumLeadScore` (type: `integer`):

Keep only records at or above this 0–100 opportunity score.

## `requireContactEmail` (type: `boolean`):

Keep only projects with at least one published contact email.

## `enrichDetails` (type: `boolean`):

Visit each official project page to capture every public agency, consultant, and applicant contact plus attachment links.

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

Maximum matching project filings saved to the dataset.

## `sortBy` (type: `string`):

Ordering applied before the result limit.

## `includeRaw` (type: `boolean`):

Attach the complete unmodified CEQAnet CSV row under raw.

## Actor input object example

```json
{
  "lookbackDays": 30,
  "receivedFrom": "",
  "receivedTo": "",
  "documentTypes": [
    "NOP",
    "EIR",
    "MND",
    "NEG",
    "NOD",
    "NOC",
    "NOI",
    "SCA",
    "FIN"
  ],
  "county": "",
  "city": "",
  "leadAgency": "",
  "keywords": [],
  "projectCategories": [],
  "minimumLeadScore": 0,
  "requireContactEmail": false,
  "enrichDetails": true,
  "maxItems": 100,
  "sortBy": "newest",
  "includeRaw": false
}
```

# Actor output Schema

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

Normalized development projects, contacts, locations, filing stages, and lead signals.

# 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/california-ceqa-project-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/california-ceqa-project-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/california-ceqa-project-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesignal_labs/california-ceqa-project-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/WsNAE1EsFd9oap7T3/builds/u2StWllKTJJGThplh/openapi.json