Custom Connector
München Open Data Portal
Global
The München Open Data Connector enables efficient integration with the City of München’s official open data platform — dataset discovery via package search with filtering, complete inventory retrieval, and system monitoring via status checks. It supports parameterized queries and pagination, plus portal metadata access.
Overview
Integration Overview
This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the Munich Open Data Connector.
- package_search. Searches for datasets with filtering and pagination options.
- package_list. Retrieves a list of all dataset IDs available in the portal.
- status_show. Retrieves the current status and metadata of the API.
- site_read. Gets information about the open data portal site.
Documentation
Detailed Integration Documentation
Package Search
| Action | package_search |
|---|---|
| Purpose | Retrieves datasets matching search criteria with filtering and pagination. |
| Parameters | Optional: q (search query); rows (results to return); start (pagination offset); fq (faceted filter query); sort (field and order). |
| Output | Successful: JSON with search results and metadata. Failure: error details. |
| Workflow example | Use package_search with query terms, filter by topic (e.g. transportation), and apply pagination for large result sets. |
Package List
| Action | package_list |
|---|---|
| Purpose | Retrieves a complete list of all dataset identifiers. |
| Parameters | Optional: limit (maximum results); offset (pagination). |
| Output | Successful: an array of dataset IDs. Failure: error details. |
| Workflow example | Execute package_list to enumerate the full catalog, then fetch detail per dataset. |
Status & Site Info
| Action | status_show / site_read |
|---|---|
| Purpose | Retrieves the current operational status and version of the API, and general information about the portal site. |
| Parameters | None. |
| Output | Successful: API status/version, or site configuration and description. Failure: error if unavailable. |
| Workflow example | Use status_show to monitor availability and site_read for integration context. |
Example Workflow: Municipal Data Discovery & Monitoring
| Search | Use package_search with query parameters, filtering by topic and applying pagination. |
|---|---|
| Process | Extract relevant dataset information and identify new or updated datasets. |
| Monitor | Store metadata for ongoing monitoring, and use status_show to track API health. |
Support
For technical support, contact custom-connectors-support@isolutions.sa.