Developer API

The same dataset that powers this site, available as free, unauthenticated, static JSON. No API key, no rate limit beyond what a static file host imposes — these are plain files served from Cloudflare's edge, not a server.

Endpoints

GET /api/orders.json

Bulk listing of every order: id, EO number, title, president, dates, word count, sentiment, tone tag, topic tags, Federal Register citation, and legal status (`legal_status`: Revoked, Superseded, Amended, etc., or null when no action is recorded). No full document text — full text, plain-English summaries, key directives, and affected entities are on each order's own page (see below).

Full order detail

There's no standalone per-order JSON endpoint — with 11,000+ orders, statically pre-rendering one JSON file per order doubled this site's file count for no benefit over the page that already exists. Full detail (document text, plain-English summary, key directives, affected entities, all metrics) lives on each order's page at /orders/{id}, where {id} is the same slug that appears in every id field in the bulk listing above.

Example: /orders/fr-2026-19335

Example response

Shape of a single order from the bulk listing (truncated):

{
  "id": "fr-2026-19335",
  "eo_number": 14428,
  "eo_suffix": null,
  "title": "Executive Order — Example Title",
  "president_name": "…",
  "signing_date": "2026-01-15",
  "fr_citation": "91 FR 2150",
  "legal_status": "Amended",
  "word_count": 842,
  "reading_time_minutes": 4,
  "sentiment_valence": "Constitutional Fidelity",
  "sentiment_compound": 0.12,
  "tone_tag": "Art. II §3: Faithful Execution of Statutory Law",
  "topics": [
    "Energy & Environment",
    "Economy & Finance"
  ],
  "url": "https://executiveordersarchive.org/orders/fr-2026-19335"
}

Update frequency & caching

These files are regenerated whenever the underlying dataset changes and this site is rebuilt — in practice, roughly twice per weekday as new executive orders are synced from the Federal Register. They're served with a one-hour cache header; if you need fresher data than that, poll /api/orders.json and diff against your own copy.

License & attribution

Executive order text and official metadata are U.S. government works in the public domain. The derived fields — sentiment scores, tone tags, topic tags, plain-English summaries — are generated by this project's automated pipeline; see About & Methodology for exactly how, and its limitations. There's no legal requirement to credit this project, but a link back to executiveordersarchive.org is appreciated.

This is an independent, unofficial project — not affiliated with the U.S. government. Treat the derived analytical fields as a research starting point, not a legal authority.