Integration
Connect iDigBio to District of Columbia Open Data
When something happens in iDigBio, your agent does the next thing in District of Columbia Open Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want iDigBio and District of Columbia Open Data 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 iDigBio and District of Columbia Open Data
Triggers and actions 1 trigger ยท 9 actions
Trigger
New recordPolls for specimen records newly indexed into iDigBio matching a saved search query, sorted by modified/index date. GET /v2/search/records/ sorted on datemodified.
Action
Find media recordsSearch iDigBio media records (images/media associated with specimens) matching a query. GET/POST /v2/search/media/ using the iDigBio Query Format (mq/rq parameters).
Action
Find recordsSearch iDigBio specimen records matching a query. GET/POST /v2/search/records/ using the iDigBio Query Format (rq parameter).
Action
Find recordsetsSearch iDigBio recordsets (collections/datasets contributed by publishers) matching a query. GET/POST /v2/search/recordsets/ using the iDigBio Query Format (rsq parameter).
Action
Get media recordRetrieve a single iDigBio media record by its UUID. GET /v2/view/mediarecords/{uuid}.
Action
Get recordRetrieve a single iDigBio specimen record by its UUID. GET /v2/view/records/{uuid}.
Action
Get recordsetRetrieve a single iDigBio recordset (dataset) by its UUID. GET /v2/view/recordsets/{uuid}.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
Action
Find recordsQuery a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
Action
Get datasetGet a dataset's metadata and field/schema definitions by dataset or layer id, so callers know what attributes can be filtered or returned.
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