Integration
Connect Federal Register to Uploadcare
When something happens in Federal Register, your agent does the next thing in Uploadcare. 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 Uploadcare 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 Uploadcare
Triggers and actions 2 triggers · 22 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
Trigger
New File UploadedTriggers when a new file is uploaded.
- Add file tags
/files/{uuid}/tags/ (add mode) — add tags to a file for organization/AI auto-tagging.
- Add group
/groups/ (Upload API) — create a file group from a set of uploaded file UUIDs.
- Convert document
convert a document/image to another format (e.g. PDF, DOCX to images).
- Convert video
transcode/thumbnail a video file into another format.
- Delete file
delete a file (or POST /files/storage/ for batch delete).
- Delete group
delete a file group (does not delete member files).
- Find files
/files/ with query params — search/filter uploaded files by criteria (used with removed/stored/uploaded_range filters).
- Get file
file info: metadata, size, mime type, URLs.
- Get file metadata
arbitrary key-value metadata attached to a file.
- Get group
file group info: files list, creation date, storage flag.
- List files
return paginated list of uploaded files, with filters (stored, removed, ordering).
- List groups
paginated list of file groups.
- Store file
mark an uploaded file as permanently stored (or POST /files/storage/ for batch store).
- Update file metadata
set/update a metadata key's value on a file.
- Upload File
Upload a new file into your project.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.