# Federal Register API

> Search US federal rules, proposed rules, notices and executive orders, plus today's filings

- Vendor: `federalregisterapi` · version 1.0 · category Regulatory Data · tags federal register api, federal rules api, regulations api, executive orders api, agency notices api, proposed rules api, us government documents, public inspection api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/federalregisterapi
- This document: https://apiclay.com/docs/federalregisterapi.md
- OpenAPI 3.1: https://apiclay.com/api/federalregisterapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `federalregisterapi`
- Updated: 2026-11-18

## About

## Federal Register API

Search every document published in the US Federal Register since 1994: final rules, proposed rules, notices, presidential documents and executive orders, filter by agency, type and date, and see what is on public inspection today before it publishes.

Data comes from **federalregister.gov** (https://www.federalregister.gov). Every route below calls the source's own public endpoint directly and returns the upstream response unchanged.

Typical flow: `/agencies` -&gt; `/documents` -&gt; `/document`

### Routes

#### GET `/documents` - Search documents
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| conditions[term] | query | string | no | Full-text search, e.g. `food labeling`. |
| conditions[agencies][] | query | string | no | Agency slug from `/agencies`, e.g. `food-and-drug-administration`. |
| conditions[type][] | query | string | no | `RULE`, `PRORULE`, `NOTICE` or `PRESDOCU`. |
| conditions[publication_date][gte] | query | string | no | From date, YYYY-MM-DD. |
| conditions[publication_date][lte] | query | string | no | To date, YYYY-MM-DD. |
| per_page | query | number | no | Up to 1000 (default 20). |
| page | query | number | no | Page number. |
| order | query | string | no | `relevance`, `newest`, `oldest`, `executive_order_number`. |
| fields[] | query | string | no | Limit fields, e.g. `title`. |

Returns: `count`, `total_pages`, `results[]` with `document_number`, `title`, `type`, `abstract`, `agencies`, `publication_date`, `html_url`, `pdf_url`.

#### GET `/document` - One document
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| document_number | path | string | yes | e.g. `2024-12345`. |

Returns: full metadata incl. `action`, `dates`, `effective_on`, `cfr_references`, `regulation_id_numbers`, `body_html_url`, `raw_text_url`.

#### GET `/agencies` - All agencies
Returns: `[]` with `id`, `name`, `short_name`, `slug`, `url`, `parent_id`.

#### GET `/public-inspection` - On public inspection today
Returns: `count`, `results[]` with `title`, `type`, `agencies`, `filed_at`, `publication_date`, `pdf_url`.

### License

Federal Register content is US government work and in the public domain.

### Caveats

- Bracketed parameter names (e.g. `conditions[term]`) must be sent exactly as written.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by federalregister.gov.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /documents — Search documents
- Gateway: `GET https://api.apiclay.com/v1/api/federalregisterapi/documents`
- Public query params: `conditions[term]` (string), `conditions[agencies][]` (string), `conditions[type][]` (string), `conditions[publication_date][gte]` (string), `conditions[publication_date][lte]` (string), `per_page` (string), `page` (string), `order` (string), `fields[]` (string)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /document — Document by number
- Gateway: `GET https://api.apiclay.com/v1/api/federalregisterapi/document`
- Public query params: `document_number` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /agencies — Agencies
- Gateway: `GET https://api.apiclay.com/v1/api/federalregisterapi/agencies`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /public-inspection — Public inspection (today)
- Gateway: `GET https://api.apiclay.com/v1/api/federalregisterapi/public-inspection`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/federalregisterapi/documents" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
