Build it
What do you want iDigBio and SLF 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 SLF
Triggers and actions 1 trigger · 7 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
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.