Federal Register Notices API

Federal Register Notices API helps you search the Federal Register and export structured notice records with titles, publication dates, agency details, and PDF links. Use it for regulatory monitoring, policy research, legal workflows, and content intelligence.

Why use this actor?

This actor turns the Federal Register into a clean dataset you can use for monitoring rulemaking, tracking notices, and feeding AI or research pipelines. It is useful when you need a quick, searchable export of current or historical notices without building your own integration.

Features

• Search Federal Register documents by keyword
• Filter results by publication date range
• Sort newest-first or oldest-first
• Export title, type, agency names, and document links
• Include or hide abstracts and PDF links
• Pay-per-event pricing tied to successful notice records

Input

Example input: keyword search

{
  "query": "artificial intelligence",
  "publicationDateFrom": "2026-05-01",
  "publicationDateTo": "2026-05-25",
  "order": "newest",
  "maxResults": 25
}

Example input: latest notices

{
  "query": "",
  "order": "newest",
  "maxResults": 10,
  "includeAbstract": false,
  "includePdfUrls": true
}

Input fields

• query (string): Search term for Federal Register documents. Leave empty to browse the latest notices.
• publicationDateFrom (string): Earliest publication date in YYYY-MM-DD format.
• publicationDateTo (string): Latest publication date in YYYY-MM-DD format.
• order (string): Sort order. Use newest or oldest.
• maxResults (integer): Maximum records to return. Values above 100 are clamped.
• pageSize (integer): Results fetched per API call. Values above 100 are clamped.
• includeAbstract (boolean): Include the abstract text.
• includeAgencies (boolean): Include the agency list.
• includePdfUrls (boolean): Include PDF and public inspection PDF URLs.

Output

Sample record:

{
  "recordType": "notice",
  "query": "artificial intelligence",
  "documentNumber": "2026-12345",
  "title": "Announcement of Requirements and Registration for EHIgnite Challenge",
  "documentType": "Notice",
  "publicationDate": "2026-05-25",
  "htmlUrl": "https://www.federalregister.gov/documents/2026/05/25/2026-12345/example",
  "pdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-05-25/pdf/2026-12345.pdf",
  "publicInspectionPdfUrl": "https://public-inspection.federalregister.gov/2026-12345.pdf",
  "abstract": "The EHIgnite Challenge addresses ...",
  "agencyNames": "Executive Office of the President",
  "agencyIds": "538",
  "excerpt": "The EHIgnite Challenge addresses ...",
  "sourceUrl": "https://www.federalregister.gov/documents/2026/05/25/2026-12345/example",
  "apiUrl": "https://www.federalregister.gov/api/v1/documents/2026-12345",
  "page": 1,
  "positionOnPage": 1
}

Use cases

• Track regulatory and policy updates
• Monitor agency notices in a specific date range
• Build legal research and compliance datasets
• Feed notice summaries into AI workflows
• Create alerts for relevant government publications

Limits and caveats

• Search quality depends on the keywords you provide.
• Very broad searches may return many results, so use date filters when possible.
• Some notices do not include abstracts or PDF links.
• Historical coverage and metadata completeness can vary by document.

Pricing

This actor uses pay-per-event pricing:

Event	Price	When it's charged
notice-produced	$0.0008 / item	Per notice successfully written to the dataset

You pay only for records that the actor produces, so small test runs stay inexpensive.

FAQ

Do I need an API key?

No. The Federal Register API is public.

Can I run this without a search term?

Yes. Leave query empty to fetch the latest notices.

What if my run charge limit is reached?

The actor stops gracefully after the last chargeable record and keeps the records already produced.