Integration
Connect Federal Register to Transport for The Netherlands
When something happens in Federal Register, your agent does the next thing in Transport for The Netherlands. 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 Transport for The Netherlands 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 Transport for The Netherlands
Triggers and actions 1 trigger · 14 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
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
- Find passtimes by stop area
Get the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
- Find passtimes by timing point
Get the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.
- List journeys
List the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
- List lines
List all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.
- List stop areas
List all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.
- List timing points
List all timing point codes (bus stops, tram/train stops, and virtual points) known to the OVAPI within its current uptime.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews