# Colorado Charity Monitor: CDOS Status & Notice Alerts (`plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor`) Actor

Watch Colorado-registered charities, paid solicitors and fundraising consultants by SOS entity ID; get an event when status moves from GOOD to NOTICE, WITHDRAWN, REVOKED or DENIED, or the name changes, from the official CDOS dataset. Pay per change.

- **URL**: https://apify.com/plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 colorado charity status event delivereds

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

## Colorado Charity Registration Monitor: CDOS Status & Notice Alerts

Watch named **Colorado-registered charities, paid solicitors and paid fundraising consultants (by Colorado Secretary of State entity ID)** against the official **Colorado Department of State (CDOS) charitable solicitation dataset** on data.colorado.gov. Get one event when a registrant on your list moves out of **GOOD** standing (to **NOTICE 1-3, WITHDRAWN, REVOKED or REGISTRATION DENIED**), returns to GOOD, or changes its name.

**Quick start:** replace the example `entityIds` with your registrants' 11-digit Colorado IDs, set `sourceMode` = **live**, then save as a Task and schedule it daily or weekly. No API key needed.

**Who this is for:**

- **Grantmakers, community foundations and donor-advised fund sponsors** checking that grantees soliciting in Colorado stay in good standing
- **Fundraising platforms, payment processors and corporate giving / matching-gift programs** that must only raise money for registered charities
- **Nonprofit compliance firms and multi-state registration services** tracking client registrations and renewal notices
- **Paid solicitors and fundraising consultants** whose charity clients must be registered before a campaign runs

The recurring job: **tell me as soon as a charity or fundraiser we work with in Colorado gets a delinquency notice, is withdrawn, revoked or denied, or changes its name**, so a grant, campaign or payout can be paused before it becomes a compliance problem.

Billable events (PPE `co-charity-status-event-delivered` @ $0.02):

| Group | Event | Meaning |
|-------|-------|---------|
| `status` | `STATUS_CHANGED` | GOOD ↔ REMINDER / NOTICE 1 / NOTICE 2 / NOTICE 3 / NOTICE 3 ESTIMATE / WITHDRAWN / REVOKED / REGISTRATION DENIED / EXEMPT (`adverse=true` for anything other than GOOD / EXEMPT / REMINDER) |
| `name` | `NAME_CHANGED` | Registrant name changed (restatements with/without "The", "Inc." or punctuation are ignored) |
| `directory` | `APPEARED` / `DROPPED` | Entity ID appeared in, or disappeared from, the CDOS dataset |
| `filing` (opt-in) | `NEW_FILING` | A new renewal, extension or amendment was filed (with the new expiration date) |

Non-billable: `RUN_STATUS` (`FIXTURE_HEALTH`, `MONITOR_IDLE`, `CATCHUP_COMPLETE`, `HEALTH_OK`), first-run baselines and duplicates. A quiet watchlist costs only the platform start fee.

**Scope:** a watchlist monitor, not a bulk dump of the registry billed per row. Officer names, addresses and financial line items are never requested or output.

### First run vs later runs

Default `sourceMode=fixture` is a **free health check**: one non-billable `RUN_STATUS` row, not product data.

In live mode, **run 1** stores a baseline for each registrant (no change events, no product charge). **Run 2 onwards** emits only the differences against that checkpoint. Keep using the same Task so the checkpoint carries over.

### What you get per $0.02 event

Each event is one unique change for a named registrant. It includes the entity ID, name, registrant type, CDOS status and status date, an `adverse` flag, before and after values, the expiration date, the dataset date (`as_of`) and the official source URL. You are never charged for `RUN_STATUS`, baselines, quiet `MONITOR_IDLE` runs, invalid IDs, duplicates or fixture SAMPLE rows.

### Example output (SAMPLE)

SAMPLE: illustrative field shape only, not a real event.

```json
{
  "entity_id": "SAMPLE01",
  "name": "EXAMPLE FOOD BANK (SAMPLE)",
  "event_type": "STATUS_CHANGED",
  "event_subtype": "NOTICE_3",
  "previous_value": "GOOD",
  "new_value": "NOTICE 3",
  "effective_date": "2026-10-02",
  "adverse": true,
  "as_of": "2026-10-06",
  "billable": false,
  "sample": true,
  "summary": "SAMPLE (fixture demo data with placeholder entities, not a real event)"
}
```

### Input

- `entityIds`: 11-digit Colorado SOS entity IDs, for example `20023007075` (dashes and spaces are ignored). Aliases: `coloradoIds`, `registrationNumbers`.
- `sourceMode`: `fixture` (free health check) or `live` (official CDOS dataset)
- `signalGroups`: any of `directory`, `status`, `name`, `filing` (default: directory + status + name)

### Production use

```json
{
  "entityIds": ["20023007075", "20023003251", "20143015105", "20023006766"],
  "sourceMode": "live",
  "signalGroups": ["directory", "status", "name"]
}
```

### Source and honesty notes

- Official dataset: `https://data.colorado.gov/resource/37wu-kn3g.json` ("Registration of Charities, Paid Solicitors, Professional Fundraising Consultants, and for-profit Public Benefit Corporations in Colorado", CDOS, public domain), refreshed daily. One small Socrata query per 50 IDs per run.
- Durable key: the 11-digit CDOS entity ID. On 2026-10-06 the dataset held 273,271 filing rows for 29,686 registrants: about 16,874 GOOD, 7,588 NOTICE 3, 3,558 WITHDRAWN, 1,114 NOTICE 3 ESTIMATE, 488 EXEMPT, plus REMINDER, NOTICE 1/2, REGISTRATION DENIED and REVOKED.
- Each registrant has one row per filing; the monitor uses the latest filing for name and type, and the latest status date for status.
- Cadence: changes appear when CDOS refreshes the dataset, not in real time. `as_of` is the dataset's last-updated date.
- Attribution: Source: Colorado Department of State, via the Colorado Information Marketplace (data.colorado.gov). This Actor is not affiliated with or endorsed by the Colorado Department of State.

### Pricing

| Event | USD |
|-------|-----|
| `co-charity-status-event-delivered` | $0.02 |
| `apify-actor-start` | $0.00005 |

### Limitations

- Check the CDOS charity search and the registrant's filings before relying on a status for a grant, payout or campaign.
- Withdrawn registrants normally stay in the dataset with their status. `DROPPED` fires only if an ID disappears entirely.
- Colorado only. It does not cover IRS tax-exempt status, other states' charity registrations or Colorado business-entity good standing.

# Actor input Schema

## `entityIds` (type: `array`):

11-digit Colorado Secretary of State charity registration IDs (shown on the CDOS charity search), e.g. 20023007075. Examples: Food Bank of the Rockies (20023007075), Denver Rescue Mission (20023003251), The American National Red Cross (20143015105), Habitat for Humanity of Metro Denver (20023006766).

## `coloradoIds` (type: `array`):

Optional alias merged into the watchlist.

## `registrationNumbers` (type: `array`):

Optional alias merged into the watchlist.

## `signalGroups` (type: `array`):

directory (APPEARED/DROPPED from the CDOS dataset), status (STATUS_CHANGED: GOOD / REMINDER / NOTICE 1-3 / NOTICE 3 ESTIMATE / WITHDRAWN / REVOKED / REGISTRATION DENIED / EXEMPT), name (NAME_CHANGED, ignoring The/Inc./punctuation restatements), filing (NEW_FILING: renewal, extension, amendment; opt-in). Default: directory+status+name.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget.

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (RUN_STATUS excluded).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume registrant snapshots and seen event_uids from the default Key-Value Store (keep the same Task).

## `sourceMode` (type: `string`):

fixture = free Store/CI health check (no network; one non-billable RUN_STATUS row unless emitFixtureDemoEvents=true). live = official Colorado Department of State charities dataset on data.colorado.gov (no API key). Fixture demo rows use placeholder registrants, are flagged sample=true / isSample=true, billable=false, and are never charged.

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, emit SAMPLE demo events from local fixtures (placeholder registrants, never charged). Default false.

## `maxTotalChargeUsd` (type: `number`):

Optional soft budget hint.

## `asOfHint` (type: `string`):

Optional as_of label (defaults to the dataset rowsUpdatedAt date).

## `socrataUrl` (type: `string`):

Optional override for the official data.colorado.gov 37wu-kn3g endpoint.

## Actor input object example

```json
{
  "entityIds": [
    "20023007075",
    "20023003251",
    "20143015105",
    "20023006766"
  ],
  "signalGroups": [
    "directory",
    "status",
    "name"
  ],
  "maxRunSeconds": 120,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, coverage, attribution

# 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 = {
    "entityIds": [
        "20023007075",
        "20023003251",
        "20143015105",
        "20023006766"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor").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 = { "entityIds": [
        "20023007075",
        "20023003251",
        "20143015105",
        "20023006766",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor").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 '{
  "entityIds": [
    "20023007075",
    "20023003251",
    "20143015105",
    "20023006766"
  ]
}' |
apify call plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/us-co-sos-charity-registration-portfolio-status-monitor"
        }
    }
}
```

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/rwKuJc8bd5zTEBNVW/builds/zV4PEPNL9a6iEPbDJ/openapi.json