US Executive Orders Tracker: Federal Register

Daily-fresh dataset of every US Presidential Document (Executive Orders, Proclamations, Memoranda, Determinations, Notices) straight from the Federal Register's public API. One clean row per document.

Built for journalists, policy analysts, lawyers, gov-affairs consultants, history researchers who need a flat, sortable feed of presidential actions without re-implementing the Federal Register pagination themselves.

What you get

One dataset row per presidential document:

field	example
documentNumber	2026-10733
subtype	Proclamation
title	Memorial Day, 2026
executiveOrderNumber	14123 (only on EOs)
presidentialDocumentNumber	11031
signingDate	2026-05-22
publicationDate	2026-05-28
citation	91 FR 22480
abstract	(when present)
agencies	[{"name": "Executive Office of the President", ...}]
htmlUrl	https://www.federalregister.gov/documents/...
pdfUrl	https://www.govinfo.gov/content/pkg/FR-.../pdf/...
rawTextUrl	https://www.federalregister.gov/documents/full_text/text/...
fullText	(only if includeFullText: true)

Inputs

{
  "sinceDays": 30,
  "subtypes": ["Executive Order", "Proclamation"]
}

input	type	default	notes
sinceDays	integer	30	Lookback window from today. Use 1 for a daily cron.
since	YYYY-MM-DD	none	Overrides sinceDays if set.
until	YYYY-MM-DD	today	Inclusive.
subtypes	string[]	all	Filter by subtype. Empty = all presidential docs.
includeFullText	boolean	false	Adds the raw text body. Slower & heavier.
userAgent	string	preset	Override only if Federal Register rejects the default.

Daily cron pattern

{ "sinceDays": 1, "subtypes": ["Executive Order"] }

Schedule daily at 14:00 UTC (after the morning Federal Register drop). Each run yields only new EOs.

Historical backfill

{ "since": "1994-01-01" }

The Federal Register API returns presidential documents back to 1994. Set the range you want; the actor paginates through every page.

What it doesn't do (and why)

• No White House press scraping: different source, different shape. Use a separate actor.
• No prediction or sentiment analysis: raw cleaned text only.
• No congressional documents: this is Article-II executive branch only.

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Presidential document extracted	$10.00	$9.00	$8.00	$7.00

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

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/us-executive-orders-tracker").call(run_input={})
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/us-executive-orders-tracker').call({});
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~us-executive-orders-tracker/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{}'

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/us-executive-orders-tracker",
      "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
• USAspending Awards Scraper: Federal Contracts and Grants
• FCC ECFS Public Notices & Filings Scraper
• openFDA Drug Recalls Scraper: Enforcement Reports
• OFAC Sanctions Screening: SDN List Name Matching
• NIH RePORTER Scraper: Research Grants by Query

Maintained by

vøiddo studio: small independent shop. Ships software the way friends recommend it.