Skip to content

How to query the infocenter


All data in the infocenter is accessible without authorization, considering that we will add personalization functionalities soon we recommend to add the profile and authorization headers just like you do on the profile API as well.

The infocenter is one big pool of public data all over Switzerland and so far we did not add any restrictions for accessing the data by the partner. But you must comply to the guidelines described in the chapter data governance and the platform guidlines.

Our goal is to deliver quality data forming a graph expressed by json-ld.


At the moment we provide a REST API only and can not offer a Graph-API like GraphQL - but we want to add it this year.

Data Models

All our data models are based on the definitions of


Detailed information about the data models and their relations you can find in the data schema definition.

  "continuation": "...",
  "data": [{
    "identifier" : "CH_Zürich_Fischers_Fritz_Campsite_Zurich",
    "@id": "ürich_Fischers_Fritz_Campsite_Zurich",
    "@type": "",
    "additionalType": "",
    "datasource": "ZHT-CMS",



Each Vertex in our graph has its unique identifier which represents exactly 1 object in the real world.

identifier which is typically used in the @id property to create the url
@id url to load the details of this object →


An identifier should only change when the real world object is changing and it should not be some internal id leaking out in the world. Ideally, everybody and each system should be able to create it in the same way. Easy examples are cities, they never change their names. After the first experiences, we made there will be some changes in the identifiers.


We offer endpoints for all Vertex classes. Properties of values of types of other Vertex classes like "containedInPlace" or "images" contain a simplified model with just enough information to download the full object or in the case of the image display it.

sample endpoints:

  • /places
  • /places/{id}
  • /localbusinesses
  • /localbusinesses/{id}

At the current state, an endpoint delivers only objects of exactly this type and not derived types. For example a LodgingBusiness or AdministrativeArea is not contained in the list of places. But City is contained in AdministrativeArea endpoint because it has no additional property and technically it is an AdministrativeArea. The type schemaOrg.City is defined in the AdditionalType property.


Search endpoints which deliver polymorphic results are coming soon.

All list endpoint deliver paged results.


default: de-CH

Language: Based on the Accept-Language header localized properties are translated.

DateTime formatting: "2019-08-09T13:59:57.097+00:00"

Use Accept-Timezone header to specify request timezone. Supply a TimeZone id property acquired from Infocenter /timezones route or IANA code in order to get data with desired time offset

The default timezone is UTC

Number formatting: CH -> 250.00

Next steps

Last update: May 25, 2021 07:43:36