# 📈 SEC EFFECT Registration Effectiveness Monitor (`snuggly_beanie_970/sec-effectiveness-monitor`) Actor

📈 Detect when SEC registration statements become effective. 🎯 Export issuer, CIK, file number, referenced form, dates and official EDGAR links. ✅ Stable filing IDs, date filters and schedule-ready monitoring.

- **URL**: https://apify.com/snuggly\_beanie\_970/sec-effectiveness-monitor.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Business, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 36.4% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 sec effectiveness notices

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?

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

## 📈 SEC EFFECT Registration Effectiveness Monitor

Turn SEC `EFFECT` notices into a clean, schedulable dataset. The Actor finds the moment a registration statement is declared effective and returns normalized company, CIK, filing date, effective date, file numbers, referenced forms, accession links, and the original SEC document.

### Why this is useful

An `EFFECT` notice is a concrete regulatory milestone, but it is easy to miss inside the general EDGAR stream. Use it to monitor offerings, follow capital-markets events, trigger diligence, enrich issuer pipelines, or alert analysts when a tracked registration becomes effective.

### 📥 Input

- `daysBack`: rolling lookback (1–31 days), ideal for schedules.
- `startDate` and `endDate`: optional fixed range; provide both or neither.
- `companyQuery`: optional case-insensitive company-name filter.
- `cik`: optional exact SEC CIK filter.
- `maxItems`: hard result cap.
- `secContactEmail`: required for SEC fair-access identification and never included in output.

### 📤 Output

Each dataset item includes `accessionNumber`, `filingDate`, `effectiveDate`, `companyName`, `cik`, `fileNumbers`, `referencedForms`, `relatedAccessionNumber`, official filing links, and source provenance. Missing optional values remain `null` or empty arrays instead of being guessed.

### Scheduling

Leave fixed dates empty and schedule the Actor daily with `daysBack: 2`. Overlap is intentional so weekend or delayed filings are not missed; deduplicate downstream by `accessionNumber`.

### Data source and responsible use

Data comes from the official SEC EDGAR daily index and filing archives. Provide a real contact email, keep ranges bounded, and follow SEC fair-access guidance. This Actor reports public regulatory records and does not provide investment advice.

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `daysBack` | integer | `7` | Rolling lookback used when fixed dates are empty. |
| `startDate` | string | — | Optional YYYY-MM-DD. Provide together with endDate. |
| `endDate` | string | — | Optional YYYY-MM-DD. Provide together with startDate. |
| `companyQuery` | string | `""` | Optional case-insensitive substring matched against the SEC company name. |
| `cik` | string | `""` | Optional exact SEC Central Index Key, with or without leading zeroes. |
| `maxItems` | integer | `100` | Hard cap on paid dataset items written by one run. |
| `secContactEmail` | string | — | Required by SEC fair-access guidance; used only in the request User-Agent. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `accessionNumber` | string |
| `filingDate` | string |
| `effectiveDate` | string / null |
| `companyName` | string |
| `cik` | string |
| `formType` | string |
| `fileNumbers` | array |
| `referencedForms` | array |
| `relatedAccessionNumber` | string / null |
| `filingUrl` | string |
| `sourceDocumentUrl` | string |
| `signal` | string |
| `source` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/sec-effectiveness-monitor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

SEC EFFECT Registration Effectiveness Monitor, sec, effect, registration, effectiveness, monitor, Apify Actor, scraper API, structured data, scheduled monitor, automation.

### 💰 Pricing

Billing is tied to successfully delivered result events. Empty, filtered, duplicate or failed records are not charged as results. Open the **Pricing** tab for the current per-event rate before starting a run, and use Apify's maximum-charge control to enforce a hard budget.

# Actor input Schema

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

Rolling lookback used when fixed dates are empty.

## `startDate` (type: `string`):

Optional YYYY-MM-DD. Provide together with endDate.

## `endDate` (type: `string`):

Optional YYYY-MM-DD. Provide together with startDate.

## `companyQuery` (type: `string`):

Optional case-insensitive substring matched against the SEC company name.

## `cik` (type: `string`):

Optional exact SEC Central Index Key, with or without leading zeroes.

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

Hard cap on paid dataset items written by one run.

## `secContactEmail` (type: `string`):

Leave empty to use the hosted operator contact, or provide your own User-Agent contact.

## Actor input object example

```json
{
  "daysBack": 7,
  "companyQuery": "",
  "cik": "",
  "maxItems": 100
}
```

# Actor output Schema

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

Dataset containing one normalized record per SEC EFFECT filing.

# 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("snuggly_beanie_970/sec-effectiveness-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("snuggly_beanie_970/sec-effectiveness-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 '{}' |
apify call snuggly_beanie_970/sec-effectiveness-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/sec-effectiveness-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/jj7WYq6s2Z0jgCgtK/builds/MluSc1vX6fJVxYn07/openapi.json