Integration
Connect Open Government, Switzerland to Xitoring
When something happens in Open Government, Switzerland, your agent does the next thing in Xitoring. 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, Switzerland and Xitoring 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, Switzerland and Xitoring
Triggers and actions 1 trigger · 23 actions
Trigger
New datasetFires when a new dataset is published to the opendata.swiss catalog.
- Find datasets by criteria
Search the opendata.swiss dataset catalog by keyword, organization, category or tag and return matching datasets.
- Find datasets by tag
Search for datasets on opendata.swiss carrying a given tag or keyword label.
- Get dataset
Retrieve full metadata and resource list for a single published dataset by its identifier.
- Get organization
Retrieve details and dataset list for one publishing organization on opendata.swiss.
- Get resource
Retrieve metadata for a single data resource (file/API endpoint) within a dataset by its identifier.
- List datasets
List the names of all datasets published in the opendata.swiss catalog.
- List organizations
List the government organizations and agencies that publish data on opendata.swiss.
Action
Add checkCreate a new uptime/website/server check. POST /api/v2/check
- Add group
Store a new check/server group. POST /api/v2/groups
- Add heartbeat
Create a new heartbeat check. POST /api/v2/heartbeat/add
- Add maintenance schedule
Create a new maintenance window. POST /api/v2/maintenance-schedules/add
- Add ticket
Create a new support ticket. POST /api/v2/tickets
- Delete check
Delete a check. DELETE /api/v2/checks/{id}
- Delete server
Remove a server from monitoring. DELETE /api/v2/servers/{id}
- Get check
Retrieve a single check by id. GET /api/v2/check/{id}
- Get incident
Get a single incident's data. GET /api/v2/incidents/{id}
- Get server
Retrieve a single server by id. GET /api/v2/servers/{id}
- List checks
List all checks. GET /api/v2/check/
- List groups
List all groups. GET /api/v2/groups
- List maintenance schedules
List maintenance schedules. GET /api/v2/maintenance-schedules
- List servers
List all monitored servers. GET /api/v2/servers
- Resolve incident
Resolve an open incident. POST /api/v2/incidents/{id}/resolve
- Update check
Update an existing check. PUT /api/v2/check/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.