Integration
Connect Swiftype to Transport for The Netherlands
When something happens in Swiftype, 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 Swiftype 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 Swiftype and Transport for The Netherlands
Triggers and actions 1 trigger · 21 actions
Trigger
New DocumentTriggers when a new Document is created.
- Add domain
Add a crawler domain to an Engine. POST /api/v1/engines/{engine_id}/domains.json with url.
- Add engine
Create a new Engine (index). POST /api/v1/engines.json with name.
- Create Document
Creates a new Document.
- Delete document
Delete a document by document_id from a document type. DELETE /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}.json
- Delete domain
Remove a crawler domain from an Engine. DELETE /api/v1/engines/{engine_id}/domains/{domain_id}.json
- Delete engine
Delete an Engine by id. DELETE /api/v1/engines/{engine_id}.json
- Get document
Retrieve a single document by external_id from a document type. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{external_id}.json
- Get engine
Retrieve a single Engine by id or name. GET /api/v1/engines/{engine_id}.json
- List documents
List documents within a document type/engine. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents.json
- List domains
List crawler domains configured on an Engine. GET /api/v1/engines/{engine_id}/domains.json
- List engines
List all Engines for the account. GET /api/v1/engines.json
- Recrawl domain
Trigger a recrawl of a domain's crawled content. PUT /api/v1/engines/{engine_id}/domains/{domain_id}/recrawl.json
- Search documents
Perform full-text search over documents within an Engine. GET/POST https://search-api.swiftype.com/api/v1/public/engines/search.json with engine_key + q. Returns matching records grouped by document type.
- Update document
Update fields on an existing document. PUT /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}/update_fields.json
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.