Integration
Connect Open Government, Germany to APIs.guru
When something happens in Open Government, Germany, your agent does the next thing in APIs.guru. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Open Government, Germany and APIs.guru 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 Open Government, Germany and APIs.guru
Triggers and actions 1 trigger · 15 actions
Trigger
New datasetFires when a new dataset is published to the open-data catalog.
- Find datasets
Search the open-data catalog for published datasets matching a keyword, tag, organization, or format filter.
- Find resources
Search across dataset resources by query text or format.
- Get dataset
Retrieve full details for a single published dataset, including its resources, tags, and organization.
- Get group
Retrieve details for a single topical group, including its member datasets.
- Get organization
Retrieve details for a single publishing organization, including its published datasets.
- Get resource
Retrieve details for a single data resource (file/link) belonging to a dataset.
- List datasets
List the names of all published datasets in the catalog.
- List groups
List the topical groups datasets can belong to in the catalog.
- List organizations
List the publishing organizations registered in the catalog.
Action
Find APIs by providerReturns all APIs listed for a given provider. GET /{provider}.json (provider input path param)
- Find service names by provider
Returns all serviceNames registered for a given provider (providers that host multiple APIs under sub-services). GET /{provider}/services.json (provider input path param)
- Get API metrics
Returns basic aggregate metrics about the APIs.guru directory (numSpecs, numAPIs, numEndpoints, etc). GET /metrics.json
- Get API specification
Retrieves one version of a particular API's OpenAPI spec by provider and api version, optionally scoped to a serviceName. GET /specs/{provider}/{api}.json or /specs/{provider}/{service}/{api}.json (provider, api, optional service input params)
- List APIs
Returns the full catalog of all APIs indexed by APIs.guru, keyed by provider/api. GET /list.json
- List providers
Returns the full list of API providers known to APIs.guru. GET /providers.json
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