FCC ECFS Public Notices & Filings Scraper

Pull FCC public notices and ECFS filings by proceeding/docket number. Returns filer name, date received, document URLs, submission type, and address for each filing. Built for telco compliance, ISP regulatory ops, and FCC news desks.

---

How to use

Set the proceeding input to an array of FCC docket numbers. The actor fetches up to limitPerProceeding filings per docket (default 25, max 100) sorted by newest first.

{
  "proceeding": ["17-108", "21-450", "23-65"],
  "limitPerProceeding": 25,
  "apiKey": "DEMO_KEY"
}

Field	Type	Default	Description
proceeding	string[]	["17-108","21-450","23-65"]	FCC proceeding/docket numbers (e.g. 17-108 net neutrality, 21-450 Affordable Connectivity)
limitPerProceeding	integer	25	Max filings per docket (max 100)
apiKey	string	DEMO_KEY	FCC API key from api.data.gov. DEMO_KEY works but is throttled to ~30 req/hr

---

Example output row

{
  "snapshotAt": "2026-06-15T09:00:00+00:00",
  "filing_id": "10242011490047",
  "date_received": "2024-03-15T00:00:00.000Z",
  "submission_type": "COMMENT",
  "filer_name": "Electronic Frontier Foundation",
  "proceeding": "17-108",
  "allProceedings": ["17-108"],
  "document_filename": "EFF_Comments_17-108.pdf",
  "document_url": "https://docs.fcc.gov/public/attachments/DOC-401234A1.pdf",
  "city": "San Francisco",
  "state": "CA",
  "text_snippet": "The Electronic Frontier Foundation submits these comments in support..."
}

---

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Result	$2.55	$2.29	$2.04	$1.78

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

---

Buyer

• Telco & ISP regulatory teams tracking proceeding activity across key FCC dockets (net neutrality, spectrum, ACP).
• FCC reporters and policy analysts monitoring new comment filings in real time without clicking through ECFS manually.
• Law firms and compliance consultants building audit trails of filer participation by docket.
• Lobbyists and advocacy orgs tracking competitor and coalition filing activity across their priority proceedings.
• Data vendors ingesting structured FCC filing metadata for downstream legal research products.

---

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/fcc-public-notices").call(run_input={"proceeding": ["17-108", "21-450", "23-65"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/fcc-public-notices').call({"proceeding": ["17-108", "21-450", "23-65"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~fcc-public-notices/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"proceeding": ["17-108", "21-450", "23-65"]}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/fcc-public-notices",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Federal Register Scraper: Rules, Proposed Rules, Notices
• US Executive Orders & Presidential Docs Tracker
• USAspending Awards Scraper: Federal Contracts and Grants
• openFDA Drug Recalls Scraper: Enforcement Reports
• OFAC Sanctions Screening: SDN List Name Matching
• SEC 13D/13G Beneficial Ownership Filings Scraper

Source

FCC ECFS Public API https://publicapi.fcc.gov/ecfs/filings

• Docs: https://www.fcc.gov/ecfs/help/public-api-documentation
• Filter by docket: proceedings.name={proceeding}
• Sort: sort=date_received,DESC
• Max page size: 100 filings
• Rate limit: DEMO_KEY ~30 req/hr per IP; register at api.data.gov for 1 000 req/hr
• New filings drop ~midnight ET daily