Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Kin Lane

Chat with Kin

AI assistant · trained on my blog

Technical University of Munich

Technical University of Munich locations API

API to access/search for location information

Documentation Provider Profile APIs.io OpenAPI GitHub

Technical University of Munich locations API is one of 9 APIs that Technical University of Munich publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include locations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 5 paths, and defines 38 schemas. It is described by OpenAPI 3.0.1, at version 2.1.

Requests are made against a single base URL, https://tum-dev.github.io/eat-api/{language}.

5 operations 5 paths 38 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.1
Base URL
https://nav.tum.de/api
Resource Areas
1

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. Each is listed below with its method, path, parameters, and response codes.

locations 5

API to access/search for location information

GET
/api/locations/{id}
Get entry-details
get_handler 2 params → 200400404
GET
/api/locations/{id}/nearby
Get the nearby items
nearby_handler 1 param → 200400404
GET
/api/locations/{id}/preview
Get a entry-preview
maps_handler 3 params → 200400404
GET
/api/locations/{id}/qr-code
Get a QR code for a location
qr_code_handler 1 param → 200400500
GET
/api/search
Search entries
search_handler 15 params → 200400404414

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are LocationDetailsResponse (15 properties), RoomfinderMapEntryResponse (9 properties), TransportationResponse (7 properties), ResultEntry (6 properties). Each schema is shown below with its type and property counts.

OverlayMapsResponse
object
2 properties 1 required
BuildingsOverviewItemResponse
object
4 properties 3 required
ExtraComputedPropResponse
object
3 properties 1 required
MapsResponse
object
3 properties 1 required
BuildingsOverviewResponse
object
2 properties 2 required
CoordinateResponse
object
4 properties 3 required
DefaultMapsResponse
string
RankingFactorsResponse
object
5 properties 3 required
ResultFacet
string
FloorType
string
FeaturedOverviewItemResponse
object
4 properties 4 required
NearbyLocationsResponse
object
1 property 1 required
TransportationResponse
object
7 properties 5 required
SectionsResponse
object
3 properties
RoomsOverviewUsageChildResponse
object
2 properties 2 required
RoomfinderMapEntryResponse
object
9 properties 9 required
ResultsSection
object
4 properties 4 required
LocationDetailsResponse
object
15 properties 12 required
ImageInfoResponse
object
The information you need to request Images from the /cdn/{size}/{id}{counter}.webp endpoint
3 properties 3 required
CoordinateSourceResponse
string
FacetFilter
string
Allowlisted values for the ?type= query parameter. Modeled as an enum so serde rejects unknown values with a 400 instead of silently dropping them, and so the…
ResultEntry
object
6 properties 4 required
FloorResponse
object
5 properties 5 required
PossibleURLRefResponse
object
A link with a localized link text and url
2 properties 1 required
URLRefResponse
object
A link with a localized link text and url
2 properties 1 required
ComputedPropResponse
object
3 properties 2 required
RoomsOverviewResponse
object
1 property 1 required
PropsResponse
object
Data for the info-card table
6 properties 1 required
OperatorResponse
object
Operator of a location
4 properties 4 required
SourcesResponse
object
Where we got our data from, should be displayed at the bottom of any page containing this data
2 properties 1 required
CoordinateAccuracyResponse
string
LocationTypeResponse
string
SearchResponse
object
Returned search results by this
2 properties 2 required
OverlayMapEntryResponse
object
5 properties 5 required
RoomfinderMapResponse
object
2 properties 2 required
FeaturedOverviewResponse
object
1 property 1 required
SourceResponse
object
2 properties 1 required
RoomsOverviewUsageResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tum-locations-api-openapi.yml Raw ↑

Other APIs Technical University of Munich publishes across the network.

TUM Campus App Backend (gRPC)
AE Profile APIs.io
Technical University of Munich calendar API
AE Profile APIs.io
Technical University of Munich feedback API
AE Profile APIs.io
Technical University of Munich maps API
AE Profile APIs.io
Technical University of Munich menu API
AE Profile APIs.io
Technical University of Munich Openapi.json API
AE Profile APIs.io
Technical University of Munich static API
AE Profile APIs.io
Technical University of Munich Status API
AE Profile APIs.io
#locations
← Back to T APIs
API Details
ID
tum:tum-locations-api
Base URL
https://nav.tum.de/api
Docs
https://github.com/TUM-Dev/NavigaTUM
Provider
Technical University of Munich
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network