Integration
Connect Vouchsafe to Federal Register
When something happens in Vouchsafe, your agent does the next thing in Federal Register. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Vouchsafe and Federal Register 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 Vouchsafe and Federal Register
Triggers and actions 3 triggers ยท 15 actions
Trigger
User Needs ReviewTriggers when a user could not be automatically verified, and needs your review.
- User Verified
Triggers when a verification is automatically completed.
- Find addresses by postcode
Search for addresses matching a given postcode. GET /api/v1/postcode-search (SearchPostcode).
- Get account detail
Retrieve details for a specific monitored account (subject of an alert). GET /api/v1/accounts/{id} (GetAccountDetail).
- Get team
Retrieve details for a Vouchsafe team/workspace by ID. GET /api/v1/teams/{id} (GetTeam).
- Get verification
Retrieve a verification case's status and check results by ID. GET /api/v1/verifications/{id}.
- List verifications
List verification cases for the team. GET /api/v1/verifications.
- Perform smart lookup
Look up and enrich identity details (e.g. email/phone) via Vouchsafe's smart lookup service. POST /api/v1/smart-lookups (PerformSmartLookup).
- Request Verification
Starts a verification session for an applicant, new user or customer.
- Toggle alerts
Enable or disable proactive alert monitoring for an account. POST /api/v1/accounts/{id}/toggle-alerts (ToggleAlerts).
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
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.