POST /api/federalregister/documents
Price: 1 credit
Get Federal Register document details by document number (or a list of numbers)
Get full details of one or more US Federal Register documents by document number (e.g. '2026-12535') or document URL. Returns title, type (Rule / Proposed Rule / Notice / Presidential Document), abstract, action, dates, publishing agencies, docket IDs, regulation ID numbers (RIN), CFR references, topics, citation, page range, executive order number, and links to PDF, XML and HTML full text.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)document_number union required — Federal Register document number, or a list of numbers (also accepts a document URL) (examples: "2026-12535", ["2026-12535","2026-12440"]; minLength: 1)@type string (default: "FederalregisterDocument")document_number string requiredtype string nullablesubtype string nullabletoc_doc string nullabletoc_subject string nullableabstract string nullableaction string nullabledates string nullableexcerpts string nullablepublication_date string nullableeffective_on string nullablecomments_close_on string nullablesigning_date string nullablecitation string nullablevolume integer nullablestart_page integer nullableend_page integer nullablepage_length integer nullablesignificant boolean nullableexecutive_order_number string nullableproclamation_number string nullablepresidential_document_number string nullabledocket_ids array (default: [])regulation_id_numbers array (default: [])regulation_id_number_info array (default: [])@type string (default: "FederalregisterRegulationIdNumber")regulation_id_number string nullableissue string nullablepriority_category string nullablehtml_url string nullablexml_url string nullabletopics array (default: [])agencies array (default: [])@type string (default: "FederalregisterAgencyRef")id integer nullablename string nullableraw_name string nullableslug string nullableparent_id integer nullableurl string nullablejson_url string nullablecfr_references array (default: [])@type string (default: "FederalregisterCfrReference")chapter string nullablepart string nullablecitation_url string nullabledockets array (default: [])@type string (default: "FederalregisterDocket")id string nullableagency_name string nullablesupporting_documents_count integer nullablesupporting_documents array (default: [])@type string (default: "FederalregisterSupportingDocument")document_id string nullabledocuments array (default: [])@type string (default: "FederalregisterDocketDocument")id string nullablecomment_count integer nullablecomment_url string nullablecomment_start_date string nullablecomment_end_date string nullableallow_late_comments boolean nullableregulations_dot_gov_open_for_comment boolean nullableupdated_at string nullablepage_view_count integer nullablecomment_url string nullablehtml_url string nullablepdf_url string nullablepublic_inspection_pdf_url string nullablefull_text_xml_url string nullablebody_html_url string nullableraw_text_url string nullablemods_url string nullablejson_url string nullableregulations_dot_gov_url string nullableregulations_dot_gov_info object nullable@type string (default: "FederalregisterRegulationsDotGovInfo")docket_id string nullabledocument_id string nullableagency_id string nullableregulation_id_number string nullablecomments_count integer nullablecomments_url string nullablesupporting_documents_count integer nullablesupporting_documents array (default: [])@type string (default: "FederalregisterSupportingDocument")document_id string nullablechecked_at string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Document not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.