FutureDataHubDeutsch
Menu

For developers

Open standards, documented contracts and source code you can read.

Interfaces

  • REST: described with OpenAPI 3.1, versioned under /v1. Choose the format via Accept: JSON, JSON-LD or CSV for measurements.
  • GraphQL: for targeted queries across several object types, with limits on depth and complexity.
  • JSON-LD: data model based on schema.org and ODTA, every response checked against JSON Schema and SHACL.
  • Feeds and DCAT: all open, approved records as a JSON-LD feed per type, plus a DCAT catalogue for open data portals.
  • Webhooks: notifications on changes instead of constant polling, signed with HMAC-SHA256.
  • Search: hybrid search by meaning and keyword at /v1/search.
  • Widgets: web components such as <hub-event-list>, <hub-detail> and <hub-map> for any website, without a framework, served from your own server.
  • MCP: a Model Context Protocol server through which AI agents read with the same permissions as your API key, with provenance and license in every response.

Provenance and license in every response

Every record carries meta with source, retrieval time, license and attribution. So you always know what you may pass on and how.

Contracts first

The data model and interfaces are defined as contracts before code is written. Changes to them are documented, versioned and checked in CI.

Connectors

Every data source is its own container following the Airbyte protocol. The code contains connectors for feratel DS-API and DSI, contwise, Outdooractive, GeoSphere Austria, destination.one, ODTA JSON-LD feeds, iCal and CSV. GeoSphere Austria, ODTA feeds, iCal and CSV are tested with test data; the others await source access. You can build your own connectors using the same pattern.

API documentation and repository

We will link the API documentation and the public repository here as soon as publication is approved.