Federal Register Scraper — US Rules, Notices & Monitor avatar

Federal Register Scraper — US Rules, Notices & Monitor

Pricing

$8.00 / 1,000 federal register digests

Go to Apify Store
Federal Register Scraper — US Rules, Notices & Monitor

Federal Register Scraper — US Rules, Notices & Monitor

US Federal Register scraper: track rules and notices. Open Input → leave defaults → Start (1 agency feed + maxDocs 5 ≈ USD 0.008/row): https://console.apify.com/actors/Amk9WaiNinR8xodgX/input From USD 8/1k.

Pricing

$8.00 / 1,000 federal register digests

Rating

0.0

(0)

Developer

naoki anzai

naoki anzai

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Federal Register Rule & Notice Watch Scraper

What you get: one digest row per Federal Register feed (agency + document types) with new-document counts, the document-type mix, watch-term hits, and the documents (number, type, title, abstract, publication date, comment or effective dates, HTML and PDF links).

Sample output from a real run (2026-10-18, the JSON below: EPA rules and proposed rules, last 3 days → 1 digest row with 5 documents, 3 shown):

docNumberdocTypepublicationDatetitle (start)dates
2026-21383PROPOSED RULE2026-10-19New Source Performance Standards and National Emission Standards for Hazardous Air Pollutants; Delegation of Authority…Comments must be received on or before November 18, 2026.
2026-21289PROPOSED RULE2026-10-19Air Quality Plan; Arizona; Agricultural Best Management Practices Rules for the West Pinal County PM10 Nonattainment…Comments must be received on or before November 18, 2026.
2026-21268RULE2026-10-19Approval and Promulgation of Implementation Plans; Arizona; Revisions to the Cleaner Burning Gasoline, Winter…This rule is effective on November 18, 2026.

The digest row had status: action_needed, newDocCount: 5 (4 proposed rules, 1 rule). One digest row is one dataset-item event (USD 0.008).

Open Input (leave defaults → Start)

Paid first run ≈ USD 0.008 per digest row (1 agency feed, maxDocsPerFeed 5, lookbackDays 3). Open Console Input (deep link above) and run this JSON.

{
"feeds": [
{
"id": "epa-rules-proposed",
"name": "EPA Rules & Proposed Rules",
"agencySlug": "environmental-protection-agency",
"documentTypes": "RULE,PRORULE",
"keywords": ""
}
],
"watchTerms": "climate,emissions",
"lookbackDays": 3,
"maxDocsPerFeed": 5,
"maxPagesPerFeed": 1,
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "federal-register-first-run",
"notifyOnNoNew": true,
"dryRun": false
}

Use this actor to monitor Federal Register rules, proposed rules, notices, agencies, and watch-term matches from the official API. Input agency slugs, document types, lookback windows, and watch terms; get source-linked digest rows for policy and regulatory monitoring. FederalRegister.gov provides an API view of Federal Register documents; verify important records with the linked official source before relying on them.

Store Quickstart

Run this actor with your target input. Results appear in the Apify Dataset and can be piped to webhooks for real-time delivery. Use dryRun to validate before committing to a schedule.

Use with Apify MCP

Exact actor: taroyamada/federal-register-digest

Sample input JSON:

{
"feeds": [
{
"id": "epa-rules-proposed",
"name": "EPA Rules & Proposed Rules",
"agencySlug": "environmental-protection-agency",
"documentTypes": "RULE,PRORULE",
"keywords": ""
}
],
"watchTerms": "climate,emissions",
"lookbackDays": 3,
"maxDocsPerFeed": 5,
"maxPagesPerFeed": 1,
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "federal-register-first-run",
"notifyOnNoNew": true,
"dryRun": false
}

Key Features

  • 🏛️ Government-sourced — Pulls directly from official agency feeds — no third-party aggregators
  • ⏱️ Timely digests — Daily/weekly rollups of new filings, rulings, or actions
  • 🔍 Keyword watchlists — Flag items matching your compliance/legal watch terms
  • 📊 Structured metadata — Agency, date, docket, document type, link — all dataset-ready
  • 📡 Webhook alerts — Push to legal/compliance teams the moment new items match watchlist

Use Cases

WhoWhy
DevelopersAutomate recurring data fetches without building custom scrapers
Data teamsPipe structured output into analytics warehouses
Ops teamsMonitor changes via webhook alerts
Product managersTrack competitor/market signals without engineering time

Input

FieldTypeDefaultDescription
feedsarrayrequiredOne entry per agency/topic watch target. Each feed produces one summary digest row. Set agencySlug and documentTypes to
watchTermsstring—Keywords, company names, or regulatory topics to flag in document titles and abstracts. Matching documents receive a wat
lookbackDaysinteger7Fetch documents published within this many days. Use 7–14 for recurring scheduled runs; widen to 30+ for initial discove
maxDocsPerFeedinteger5Upper bound on documents fetched per feed per run. Increase for broad discovery; keep low (50) for fast recurring digest
maxPagesPerFeedinteger5Hard page cap per feed to prevent runaway pagination. Each page fetches up to 100 documents.
deliverystring"dataset"dataset stores results in the Apify dataset. webhook posts the digest JSON to webhookUrl.
webhookUrlstring—POST target for the digest payload. Leave empty for dataset delivery.
datasetModestring"all"all emits every feed digest row. action_needed emits only feeds with watch-term hits. new_only emits only feeds with doc

Input Example

{
"lookbackDays": 7,
"maxDocsPerFeed": 50,
"maxPagesPerFeed": 5,
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "federal-register-digest-state",
"federalRegisterApiUrl": "https://www.federalregister.gov/api/v1/documents.json",
"requestTimeoutSeconds": 30,
"notifyOnNoNew": true,
"dryRun": false
}

Input Examples

Example: One agency, final rules only

{
"feeds": [
{
"id": "fda-rules",
"name": "FDA final rules",
"agencySlug": "food-and-drug-administration",
"documentTypes": "RULE"
}
],
"lookbackDays": 14,
"maxDocsPerFeed": 5
}

Example: Two agencies with keywords

{
"feeds": [
{
"id": "sec-notices",
"name": "SEC rules and notices",
"agencySlug": "securities-and-exchange-commission",
"documentTypes": "RULE,PRORULE",
"keywords": "disclosure"
},
{
"id": "epa-rules-proposed",
"name": "EPA Rules & Proposed Rules",
"agencySlug": "environmental-protection-agency",
"documentTypes": "RULE,PRORULE"
}
],
"lookbackDays": 7,
"maxDocsPerFeed": 5
}

Example: Recurring watch-term alerts only

{
"feeds": [
{
"id": "epa-rules-proposed",
"name": "EPA Rules & Proposed Rules",
"agencySlug": "environmental-protection-agency",
"documentTypes": "RULE,PRORULE"
}
],
"watchTerms": "emissions,PFAS",
"lookbackDays": 7,
"maxDocsPerFeed": 5,
"datasetMode": "action_needed",
"notifyOnNoNew": false
}

Output

FieldTypeDescription
metaobject
errorsarray
digestsarray
digests[].feedIdstring
digests[].feedNamestring
digests[].agencySlugsarray
digests[].documentTypesarray
digests[].checkedAttimestamp
digests[].statusstring
digests[].newDocCountnumber
digests[].totalDocCountnumber
digests[].changedSinceLastRunboolean
digests[].actionNeededboolean
digests[].recommendedActionstring
digests[].signalTagsarray
digests[].watchTermHitsarray
digests[].topDocTypesobject
digests[].documentsarray
digests[].errornull

Output Example

{
"meta": {
"generatedAt": "2024-02-15T09:00:00.000Z",
"now": "2024-02-15T09:00:00.000Z",
"lookbackDays": 7,
"feedCount": 2,
"totalDocs": 5,
"newDocs": 4,
"watchTermHitCount": 2,
"actionNeededCount": 1,
"snapshot": {
"key": "federal-register-digest-sample",
"loadedFrom": "local",
"savedTo": "local"
},
"warnings": [],
"executiveSummary": {
"overallStatus": "action_needed",
"brief": "1 feed(s) have watch-term hits requiring review.",
"watchTermHits": [
{
"term": "climate",
"docNumber": "2024-02974",
"title": "National Ambient Air Quality Standards for Particulate Matter",
"docType": "RULE",
"primaryAgency": "Environmental Protection Agency",
"publicationDate": "2024-02-07T00:00:00.000Z",
"htmlUrl": "https://www.federalregister.gov/documents/2024/02/07/2024-02974/national-ambient-air-quality-standards"
},
{
"term": "greenhouse",
"docNumber": "2024-02345",
"title": "Greenhouse Gas Reporting: Additions and Revisions",
"docType": "PRORULE",
"primaryAgency": "Environmental Protection Agency",
"publicationDate": "2024-02-12T00:00:00.000Z",
"htmlUrl": "https://www.federalregister.gov/documents/2024/02/12/2024-02345/greenhouse-gas-reporting"
}
],
"actionItems": [

API Usage

Run this actor programmatically using the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Settings → Integrations.

cURL

curl -X POST "https://api.apify.com/v2/acts/taroyamada~federal-register-digest/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "lookbackDays": 7, "maxDocsPerFeed": 50, "maxPagesPerFeed": 5, "delivery": "dataset", "datasetMode": "all", "snapshotKey": "federal-register-digest-state", "federalRegisterApiUrl": "https://www.federalregister.gov/api/v1/documents.json", "requestTimeoutSeconds": 30, "notifyOnNoNew": true, "dryRun": false }'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("taroyamada/federal-register-digest").call(run_input={
"lookbackDays": 7,
"maxDocsPerFeed": 50,
"maxPagesPerFeed": 5,
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "federal-register-digest-state",
"federalRegisterApiUrl": "https://www.federalregister.gov/api/v1/documents.json",
"requestTimeoutSeconds": 30,
"notifyOnNoNew": true,
"dryRun": false
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('taroyamada/federal-register-digest').call({
"lookbackDays": 7,
"maxDocsPerFeed": 50,
"maxPagesPerFeed": 5,
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "federal-register-digest-state",
"federalRegisterApiUrl": "https://www.federalregister.gov/api/v1/documents.json",
"requestTimeoutSeconds": 30,
"notifyOnNoNew": true,
"dryRun": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Tips & Limitations

  • Run daily for active watchlists; weekly for passive monitoring.
  • Webhook delivery works well for compliance team Slack channels — include docket URL for 1-click access.
  • Use watchKeywords generously — false positives are cheap to triage, false negatives miss filings.
  • Pair with regulatory-change-monitor for cross-agency coverage.
  • Archive Dataset rows weekly for long-term compliance evidence retention.

FAQ

How far back does history go?

This actor monitors forward-only — new items since first run. For historical data, use the agency's own search tool.

What timezones are used?

All timestamps are UTC. Use your downstream pipeline to convert to agency-local time if needed.

Does it translate non-English content?

No — original language is preserved. Use downstream translation services if needed.

Is the data official?

Yes — sourced directly from official government websites and feeds. Not a third-party aggregator.

Can I use this for legal research?

For alerting and monitoring, yes. For litigation research, cross-verify with primary sources (agency websites) — this actor is a monitoring tool, not a legal database.

Government & Regulatory cluster — explore related Apify tools:

Cost

Pay Per Event (Apify Store pricing):

  • apify-default-dataset-item: $0.008 per digest row

Example: 100 rows = 100 × $0.008 = $0.8

No subscription required — you only pay for what you use.

⭐ Was this helpful?

If this actor saved you time, please leave a ★ rating on Apify Store. It takes 10 seconds, helps other developers discover it, and keeps updates free.

Bug report or feature request? Open an issue on the Issues tab of this actor.

Compliance Guardrails

This actor is independently operated and has no source-agency affiliation, sponsorship, or approval. It uses public data from FederalRegister.gov API (https://www.federalregister.gov/developers/documentation/api/v1). Results are informational only and may be delayed, incomplete, amended, withdrawn, or superseded by the source. Verify all records with the linked official source before relying on them.

  • Use the documented API, not UI scraping.
  • Treat results as informational monitoring; link users to official document URLs/PDFs for verification.
  • Do not imply agency endorsement or legal advice.