Integration
Connect Federal Register to FilePost
When something happens in Federal Register, your agent does the next thing in FilePost. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Federal Register and FilePost to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Federal Register and FilePost
Triggers and actions 1 trigger · 17 actions
Trigger
New documentPolling trigger that fires when a new Federal Register document is published, using GET /documents.{format} sorted by publication_date descending as the dedup source for regulatory monitoring.
- Find documents
Search all Federal Register documents published since 1994 by term, agency, document type, publication/effective date, and docket number. Endpoint: GET /documents.{format}
- Find public inspection documents
Search public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}
- Get agency
Fetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}
- Get document
Fetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}
- Get issue
Fetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}
- Get public inspection document
Fetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}
- List agencies
Fetch all agency details known to the Federal Register. Endpoint: GET /agencies
Action
Create Intake LinkCreates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
- Delete File
Permanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
- Delete intake link
Closes a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
- Get file
Returns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
- Get intake link
Returns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
- List Files
Returns the files stored in your FilePost account, newest first, together with the total number of files.
- List intake links
Returns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
- Update file
Changes whether a stored file's name appears in its public link, and returns the file with its new link.
- Upload File
Uploads a file to FilePost and returns its shareable link.
- Upload File From URL
Stores a file from a public web link in FilePost and returns its shareable link.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.