Federal Register Notices & Consultations

Turn published US Federal Register notices, proposed rules, or rules into a table your policy or compliance team can filter, export, and track. Search by keyword, agency, document type, and publication dates; each saved row links back to its source document and official PDF when available.

Quick start

For a small set of Environmental Protection Agency proposed rules published in September 2026:

{
  "agency": "environmental-protection-agency",
  "documentType": "PRORULE",
  "dateFrom": "2026-09-01",
  "dateTo": "2026-09-30",
  "maxDocuments": 5
}

The dataset contains one row per document. A representative source record is:

{
  "document_number": "2026-19500",
  "title": "Public Water System Supervision Program Revision for the State of Arkansas",
  "type": "Proposed Rule",
  "agencies": ["Environmental Protection Agency"],
  "publication_date": "2026-09-23",
  "comments_close_date": "2026-10-23",
  "docket_ids": ["FRL-13495-01-R6"],
  "source_url": "https://www.federalregister.gov/api/v1/documents/2026-19500.json"
}

Rows also include an abstract and HTML/PDF links when the source provides them. effective_date and comments_close_date appear only when published in the API record; a missing date is not inferred. The OUTPUT record shows fetched, saved and skipped counts, source count, filters, and any limit or error.

Search and coverage

• Source: the public Federal Register documents API for published US Federal Register documents. This Actor does not cover other countries, state registers, regulations.gov submissions, or unpublished public-inspection documents.
• documentType: NOTICE (default), PRORULE (Proposed Rule), or RULE. Run once per type when you need several types.
• agency: one Federal Register agency slug from an agency page URL, such as environmental-protection-agency.
• dateFrom and dateTo: inclusive publication dates, YYYY-MM-DD. They do not filter effective dates or comment deadlines.
• maxDocuments: 1–1,000 saved rows per run, default 10. Results follow the API's search order; searches and publication data can change. Check OUTPUT.status and OUTPUT.limit_reason before treating a dataset as complete.

Usage and billing

The result unit is one saved document. Under pay-per-result pricing, only document rows written to the dataset count as result events; skipped records, errors and the OUTPUT summary are not result rows. A run can end with fewer rows than the requested cap if the source has fewer matches, a source error occurs, or the run's spending or request limit is reached. The OUTPUT record identifies partial runs and the number saved. Apify platform usage follows your account plan.

FederalRegister.gov's HTML rendering is an informational resource. For legal decisions, verify the linked official PDF and applicable current law. This Actor provides source fields; it does not interpret legal effect or infer deadlines.