# New Business Filings: CO, CT, NY & OR New LLCs and Corps (`yzy001/new-business-filings`) Actor

Newly filed LLCs, corporations, nonprofits and partnerships in Colorado, Connecticut, New York and Oregon, from each state's official open-data portal. One table with entity type, out-of-state flag, filing date, address and registered agent; optional tracking returns only filings you have not seen.

- **URL**: https://apify.com/yzy001/new-business-filings.md
- **Developed by:** [宗諭 楊](https://apify.com/yzy001) (community)
- **Categories:** Lead generation, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 new 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: Colorado, Connecticut, New York & Oregon

Every newly filed LLC, corporation, nonprofit and partnership in four states, in one table, read straight from each state's official open-data portal. Pick a window (the last 7 days by default), filter by type, city, ZIP or name, and turn on tracking to get only the filings you have not received before.

A 7-day window across all four states is roughly 4,000 to 5,000 new entities.

### What you get for each filing

| Field | Meaning |
|---|---|
| `state`, `entityId`, `name` | The filing state, the state's own entity number, the registered name |
| `entityType` | `LLC`, `CORPORATION`, `NONPROFIT`, `PARTNERSHIP`, `OTHER` or `ASSUMED_NAME` (Oregon DBAs, only when you ask for them) |
| `entityTypeRaw` | The state's own type code or wording, unchanged |
| `isForeign`, `jurisdictionOfFormation` | `true` when the entity was formed in another state and registered here; where it was formed (US states as two-letter codes) |
| `filingDate` | The date the state records for the filing (see below) |
| `filingType` | New York only: articles of organization, certificate of incorporation, application of authority and so on |
| `status` | The state's current status for the entity, where it publishes one |
| `principalAddress`, `mailingAddress` | Street, city, state, ZIP, country, as filed (New York: not published) |
| `county` | New York only: county of the principal office |
| `registeredAgent` | Name and address of the registered agent (New York: the address for service of process); not available for Connecticut |
| `naicsCode`, `naicsTitle` | Connecticut only: the industry the business chose when it registered |
| `registryUrl`, `sourceRecordUrl` | Oregon's registry page for the entity; the exact record on the state's open-data portal |
| `changeStatus`, `firstSeen` | With tracking: `FIRST_RUN`, `NEW` or `SEEN`, and when this entity was first returned to you |

### How current it is

The portals are refreshed every day but trail the filings themselves by about one to three days (New York the most). The run summary shows, for each state, when its portal was last refreshed and the newest filing date it has published, and the status message says which states have not caught up with the end of your window. If a portal has not been refreshed for more than 7 days, that state is reported as failed rather than returned as if it were current.

For a daily schedule, use a 7-day window with tracking and "only filings not seen before": late-published filings are still picked up, and nothing is returned twice.

### What each state's date means

- **Colorado:** the formation date.
- **Connecticut:** the registration date.
- **New York:** the filing date of the document that created the entity (or admitted an out-of-state one).
- **Oregon:** the registry date.

For out-of-state entities it is the date they registered in that state, not the date they were formed at home.

### What is left out, and counted

- New York's daily file also contains biennial statements, amendments, assumed names, dissolutions and other filings about existing entities. Only filings that create an entity or admit an out-of-state one are used. The file also repeats many rows word for word; each entity appears once.
- Connecticut filings with the status Rejected never became entities and are left out.
- Oregon name reservations are names, not businesses, and are left out.

The run summary counts each of these by reason, per state, together with the rows your filters removed.

### Personal data

No e-mail addresses and no names of members, managers, officers or authorized representatives are collected; Connecticut's business e-mail column and Oregon's authorized-representative rows are not even requested from the portals. Registered agent names and addresses are included because the states publish them for service of process. You are responsible for how you use the data, including any marketing rules that apply to you.

### Run summary

Stored under `SUMMARY` in the key-value store: the window, and for each state its status, source dataset, last refresh, newest published filing date, rows read, entities, rows left out by reason, rows kept, counts by type, out-of-state count and filings per day.

### Data

Public-domain or openly published datasets from the Colorado Secretary of State, the Connecticut Business Registry, the New York Department of State and the Oregon Secretary of State, read through each portal's public API. No login, no scraping of search pages, and one request per second per portal as the portals ask.

# Actor input Schema

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

Which states to read. Each one comes from that state's official open-data portal.

## `daysBack` (type: `integer`):

Filings dated within the last N days, today included (1-31). The portals trail by one to three days, so a 1-day window is often empty. Ignored when a from date is set.

## `fromDate` (type: `string`):

Optional. First filing date to include (YYYY-MM-DD). The range can cover at most 31 days.

## `toDate` (type: `string`):

Optional. Last filing date to include (YYYY-MM-DD). Defaults to today.

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

Keep only these types. Assumed business names (DBAs, Oregon only) are left out unless you add ASSUMED_NAME.

## `includeForeign` (type: `boolean`):

Include entities formed in another state (often Delaware) that registered to do business here. Turn off for home-state formations only.

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

Optional. Keep entities whose principal address is in one of these cities (exact name, any case). New York publishes no street address, so New York rows are left out when this is set.

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

Optional. Keep entities whose principal address ZIP starts with one of these, for example 802 or 97209. Same New York note as cities.

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

Optional. Keep entities whose name contains any of these words, for example dental, construction, holdings.

## `trackChanges` (type: `boolean`):

Remember the entities returned by earlier tracked runs (120 days, in a key-value store named new-business-filings-state in your account) and mark each row NEW or SEEN.

## `onlyNew` (type: `boolean`):

With tracking on, leave out entities an earlier tracked run already returned. Good for a daily schedule with a 7-day window, which also catches filings the state published late.

## `allowPartial` (type: `boolean`):

On by default: if one state's portal cannot be read, the others are still returned and the status message names it. Turn off to make any failed state fail the run.

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

Upper bound on rows returned, newest filings first. A 7-day window across all four states is roughly 4,000-5,000 rows.

## Actor input object example

```json
{
  "states": [
    "CO",
    "CT",
    "NY",
    "OR"
  ],
  "daysBack": 7,
  "entityTypes": [
    "LLC",
    "CORPORATION",
    "NONPROFIT",
    "PARTNERSHIP",
    "OTHER"
  ],
  "includeForeign": true,
  "cities": [],
  "zipPrefixes": [],
  "nameKeywords": [],
  "trackChanges": false,
  "onlyNew": false,
  "allowPartial": true,
  "maxItems": 100
}
```

# Actor output Schema

## `items` (type: `string`):

Normalised filings from every state.

## `summary` (type: `string`):

Per-state status, how current each portal is, counts by type, rows left out and why, caveats.

# 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",
        "CT",
        "NY",
        "OR"
    ],
    "daysBack": 7,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("yzy001/new-business-filings").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",
        "CT",
        "NY",
        "OR",
    ],
    "daysBack": 7,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("yzy001/new-business-filings").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",
    "CT",
    "NY",
    "OR"
  ],
  "daysBack": 7,
  "maxItems": 100
}' |
apify call yzy001/new-business-filings --silent --output-dataset

```

## MCP server setup

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

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/fQ9v55li7A2aX6Fd7/builds/0JPRhMlPXMsSnzmIO/openapi.json