Register Document API: Fetch one Federal Register document by document number
Fetch one Federal Register document by document number — normalized agencies, CFR references, docket ids, effective and comment dates with day-counts and deadline flags. Free. Same schema as all AnswerPool regulation feeds.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/regs/document — product id
reg_document. Over MCP, call answerpool_get with
product_id=reg_document.
curl "https://answerpool.io/v1/regs/document?document_number=2026-12341"
Live call: https://answerpool.io/v1/regs/document?document_number=2026-12341 · JSON sample: /v1/samples/reg_document
What does the answer look like?
A representative response, the same static sample served at /v1/samples/reg_document.
as_of | 2026-09-02T14:00:00Z |
|---|---|
document.document_number | 2026-12341 |
document.title | Cybersecurity Risk Management Rule |
document.type | Rule |
document.action | Final rule. |
document.agencies | Securities and Exchange Commission |
document.publication_date | 2026-08-30 |
document.effective_on | 2026-09-12 |
document.comments_close_on | — |
document.significant | true |
document.abstract | Requires registrants to disclose material cybersecurity incidents. |
document.docket_ids | SEC-2026-001 |
document.regulation_id_numbers | 3235-AN00 |
document.cfr_references | 17 CFR 240 |
document.topics | Securities |
document.url | https://www.federalregister.gov/d/2026-12341 |
document.flags | significant, effective_soon, final_rule_pending_effect |
document.days_to_comment_close | — |
document.days_to_effective | 10 |
refresh_after | 2026-09-18T00:00:00.000Z |
The same sample as raw JSON
{
"as_of": "2026-09-02T14:00:00Z",
"document": {
"document_number": "2026-12341",
"title": "Cybersecurity Risk Management Rule",
"type": "Rule",
"action": "Final rule.",
"agencies": [
"Securities and Exchange Commission"
],
"publication_date": "2026-08-30",
"effective_on": "2026-09-12",
"comments_close_on": null,
"significant": true,
"abstract": "Requires registrants to disclose material cybersecurity incidents.",
"docket_ids": [
"SEC-2026-001"
],
"regulation_id_numbers": [
"3235-AN00"
],
"cfr_references": [
"17 CFR 240"
],
"topics": [
"Securities"
],
"url": "https://www.federalregister.gov/d/2026-12341",
"flags": [
"significant",
"effective_soon",
"final_rule_pending_effect"
],
"days_to_comment_close": null,
"days_to_effective": 10
},
"refresh_after": "2026-09-18T00:00:00.000Z"
}How fresh is it, and where does the data come from?
The fastest source behind this answer can change daily, so every response carries a refresh_after timestamp — right now it would be 2026-09-18T00:00:00.000Z. Schedule the next call on that value rather than on a guess.
- Federal Register (US federal public domain) — upstream:
https://www.federalregister.gov/api/v1
Method version 0.1.0 ·
serving cache 1 day ·
every response carries a result_id you can resolve at
/v1/provenance.
When should you use it?
You have a document number (e.g. from a watch feed) and need full details.
What you skip building
- federalregister.gov API integration
- deadline math
When should you not use it?
Searching by topic or agency — use the search and feed endpoints.
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document