# New Business Filings Watch (multi-state) (`socosupply/new-business-filings-watch`) Actor

Scheduled monitor of newly registered business entities from official state open-data portals. Returns only entities new or changed since the last run.

- **URL**: https://apify.com/socosupply/new-business-filings-watch.md
- **Developed by:** [Soco Supply](https://apify.com/socosupply) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 filings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## New Business Filings Watch (multi-state)

Monitor **newly registered business entities** from official state open-data portals. Built for B2B vendors who sell to brand-new businesses: commercial insurance, business banking, accounting, payroll, signage, and coworking.

Each scheduled run returns only filings that are **new or changed** since the last run (tracked in a named Apify key-value store). The actor pages through the full `registeredFrom` window with stable ordering; **`maxResults` caps only emitted rows**, and only emitted rows advance the cursor. Use **Emit all** to ignore that cursor and export everything in the date window (still subject to `maxResults`).

**New York** rows include `filingType` (e.g. `CERTIFICATE OF INCORPORATION`) from the filing document; `status` is the entity status when the source provides one, otherwise `null`.

**Supported states today:** Colorado (CO), New York (NY).

We normalize output across states and **never include** registered-agent names, officers, owners, organizers, or street addresses—only city, state, and ZIP for the principal location when the source provides them.

### Input example

```json
{
  "states": ["CO", "NY"],
  "registeredFrom": 3,
  "entityTypes": [],
  "nameKeywords": [],
  "cities": [],
  "zipPrefixes": [],
  "statuses": [],
  "maxResults": 50,
  "emitAll": false
}
```

### Output example (real record from local test)

```json
{
  "state": "CO",
  "entityId": "20268078805",
  "entityName": "Company 1485, LLC",
  "entityType": "DLLC",
  "status": "Good Standing",
  "formationDate": "2026-11-01",
  "jurisdiction": "domestic",
  "principalCity": "Boulder",
  "principalState": "CO",
  "principalZip": "80303",
  "sourceDataset": "https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h",
  "changeType": "new"
}
```

### Pricing

**$4.00 per 1,000 filings** returned, plus **$0.003 per run**. Platform usage is included, so a daily run with no new filings costs $0.003.

### Sample run vs. monitoring

The example input in Console returns up to 10 current matching records so you can see the output right away ("Emit all matches" on, max results 10). For a scheduled monitor, turn "Emit all matches" off and clear the max-results limit: each run then returns only records that are new or changed since the previous run, so you pay only for what's new.

### Schedule daily

In Apify Console: open the Actor → **Schedules** → **Create schedule** → cron e.g. `0 14 * * *` (6 AM Pacific) → set input (states, `registeredFrom`: 7) → save. Connect the dataset to your CRM or webhook.

Locally, use cron + `APIFY_LOCAL_STORAGE_DIR=./storage node src/main.js` with your Apify token on the server when you deploy.

### Data sources & attribution

| State | Source | Terms |
|-------|--------|--------|
| **Colorado** | [Business Entities in Colorado](https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h) — CDOS, updated daily | [CDOS open data notes](https://data.colorado.gov/stories/s/pbek-aaa3) |
| **New York** | [Corporations and Other Entities: All Filings](https://data.ny.gov/Corporations-and-Other-Entities/Corporations-and-Other-Entities-All-Filings/63wc-4exh) — NY Dept. of State, updated daily | [data.ny.gov terms](https://data.ny.gov/developers/terms-of-use) |

NY rows are filtered to **formation-style** document types (Articles of Organization, Certificate of Incorporation, Application for Authority, etc.), not biennial statements or amendments.

### Run locally

```bash
npm install
APIFY_LOCAL_STORAGE_DIR=./storage node src/main.js
```

Input is read from `storage/key_value_stores/default/INPUT.json`.

# Actor input Schema

## `states` (type: `array`):

Two-letter state codes to monitor (supported: CO, NY).

## `registeredFrom` (type: `integer`):

Include formations filed on or after this many days ago (server-side date filter). Default 7.

## `entityTypes` (type: `array`):

If set, only include these entity type strings (state-specific labels, substring match).

## `nameKeywords` (type: `array`):

Entity name must contain at least one keyword (case-insensitive).

## `cities` (type: `array`):

Principal city or county must match one entry (case-insensitive).

## `zipPrefixes` (type: `array`):

Principal ZIP must start with one of these prefixes.

## `statuses` (type: `array`):

Entity status must match one entry (case-insensitive; CO only).

## `maxResults` (type: `integer`):

Cap rows fetched and emitted per state per run.

## `emitAll` (type: `boolean`):

When true, return every row in the date window and do not dedupe against the key-value store. The example input turns this on so a first run shows a sample; turn it off for scheduled monitoring.

## Actor input object example

```json
{
  "states": [
    "CO",
    "NY"
  ],
  "registeredFrom": 3,
  "entityTypes": [],
  "nameKeywords": [],
  "cities": [],
  "zipPrefixes": [],
  "statuses": [],
  "maxResults": 10,
  "emitAll": true
}
```

# Actor output Schema

## `results` (type: `string`):

New or updated business entity filings from this run (default dataset).

# 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 = {
    "states": [
        "CO",
        "NY"
    ],
    "registeredFrom": 3,
    "entityTypes": [],
    "nameKeywords": [],
    "cities": [],
    "zipPrefixes": [],
    "statuses": [],
    "maxResults": 10,
    "emitAll": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("socosupply/new-business-filings-watch").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 = {
    "states": [
        "CO",
        "NY",
    ],
    "registeredFrom": 3,
    "entityTypes": [],
    "nameKeywords": [],
    "cities": [],
    "zipPrefixes": [],
    "statuses": [],
    "maxResults": 10,
    "emitAll": True,
}

# Run the Actor and wait for it to finish
run = client.actor("socosupply/new-business-filings-watch").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 '{
  "states": [
    "CO",
    "NY"
  ],
  "registeredFrom": 3,
  "entityTypes": [],
  "nameKeywords": [],
  "cities": [],
  "zipPrefixes": [],
  "statuses": [],
  "maxResults": 10,
  "emitAll": true
}' |
apify call socosupply/new-business-filings-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,socosupply/new-business-filings-watch"
        }
    }
}
```

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/qRC9LFTLC5yMCY15T/builds/JNE0Yso0ZyeR73CuR/openapi.json