What is the Open Data Hub?

The Open Data Hub is an open data platform for South Tyrol and beyond. It exposes datasets through REST APIs that return JSON, so you can pull live data into apps, websites, dashboards, and integrations. Most data is open and needs no authentication to read.

There are two ways people work with the Open Data Hub, and this documentation is organized around them:

• Use the data: call the APIs to read mobility and tourism data. Start with the Quickstart, then the Content API and Time Series API references.
• Bring data in: build a collector and transformer to ingest a new data source. See Data Ingestion.

Quickstart

Make your first API request and read the response.

Discover datasets

Find the dataset and fields you need before you query.

Content API

Read tourism content: accommodations, events, points of interest.

Time Series API

Read mobility measurements from stations and sensors.

Bring data in

Build a collector and transformer to ingest a new source.

Inspect and visualize

Browse content in the Data Browser or chart it in Analytics.

1. What data is available

Data is grouped into domains:

• Mobility: public transport, parking, e-charging stations, traffic, and other time series from sensors and stations.
• Tourism: accommodations, events, points of interest, activities, and related content.
• Other: datasets that do not fit the two main domains.

Domains overlap intentionally: public-transport data lives in Mobility but is useful for tourism apps too. See Domains and datasets for how datasets are addressed and what metadata each carries.

2. How you access it

Every dataset is a REST endpoint that returns JSON. You can open an endpoint in a browser to explore it, or call it from any HTTP client. For example, to fetch tourism points of interest from the Content API:

Go

package main

import (
    "fmt"
    "io"
    "net/http"
)

func main() {
    resp, err := http.Get("https://tourism.api.opendatahub.com/v1/ODHActivityPoi")
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

curl

curl "https://tourism.api.opendatahub.com/v1/ODHActivityPoi"

Python

import requests

response = requests.get("https://tourism.api.opendatahub.com/v1/ODHActivityPoi")
print(response.json())

JavaScript

fetch('https://tourism.api.opendatahub.com/v1/ODHActivityPoi')
  .then(response => response.json())
  .then(data => console.log(data));

The two APIs differ in shape: the Content API serves tourism entities, while the Time Series API serves mobility measurements. Their references cover endpoints, parameters, filtering, and response formats.

3. Also see

• Domains and datasets: how data is organized and addressed.
• Data licensing: what you can do with the data.
• Tools: Discovery, Data Browser, and Analytics for finding and inspecting data.

4. Report an issue or contribute

The Open Data Hub is open source and community-driven.

• Found a bug in an API or a gap in a dataset? Open an issue in the NOI Techpark GitHub organization.
• Want to contribute data or build a collector? Start with the Data Ingestion guide.
• Documentation feedback: help@opendatahub.com.

info

APIs are designed for stability, but check the reference docs before relying on an endpoint in production, as the platform evolves.