Integration
Connect Colorado Information Marketplace to Transport for The Netherlands
When something happens in Colorado Information Marketplace, 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 Colorado Information Marketplace 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 Colorado Information Marketplace and Transport for The Netherlands
Triggers and actions 1 trigger · 11 actions
Trigger
New recordPolling trigger: fires when a new row appears in a specified Colorado Information Marketplace (Socrata SODA API) dataset. GET https://data.colorado.gov/resource/{dataset_id}.json ordered by a rowid/created/updated system field ($order=:id DESC or an updated_at column) with $limit, dedup by the row's system id (:id) or an updated_at watermark since datasets vary in whether they expose a stable update timestamp column.
Action
Find datasetsSearch the Colorado Information Marketplace open-data catalog for datasets by keyword/category. GET https://data.colorado.gov/api/catalog/v1?q={query}&limit=... (Socrata Discovery API) returning dataset id, name, description, category, and update timestamps. Used to locate the dataset identifier that other ops (List/Get/Find records) require as input.
Action
Find records by criteriaQuery a Colorado Information Marketplace (Socrata SODA API) dataset with a SoQL $where/$select/$order filter. GET https://data.colorado.gov/api/v3/views/{dataset_id}/query.json (or resource/{dataset_id}.json on older SODA2 endpoints) with SoQL query params ($where, $select, $order, $limit, $offset). Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu) as input plus the SoQL clauses.
Action
Get recordGet a single row from a Colorado Information Marketplace (Socrata SODA API) dataset by its row identifier. GET https://data.colorado.gov/resource/{dataset_id}/{row_id}.json (or a $where=:id='{row_id}' query when the dataset has no explicit row identifier). Requires dataset_id and row_id.
Action
List recordsList all rows in a Colorado Information Marketplace (Socrata SODA API) dataset, paginated. GET https://data.colorado.gov/resource/{dataset_id}.json with $limit/$offset params. Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu).
Action
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
Action
Find passtimes by stop areaGet the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
Action
Find passtimes by timing pointGet the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.
Action
List journeysList the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
Action
List linesList all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.
Action
List stop areasList all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.
Action
List timing pointsList 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