How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NavigaTUM

Search and navigation API for TUM rooms, buildings and places — a Rust service over MeiliSearch, fully unauthenticated, documented with an OpenAPI 3 contract served live at https://nav.tum.de/api/openapi.json. Twelve operations across search, locations, maps, calendar, feedback and status. GET /api/status returns the exact deployed commit alongside its health, a build-provenance practice almost nothing else in this cohort does. Also publishes a .well-known/security.txt. The six OpenAPI files below are one contract split by tag by refine-openapis, not six APIs; they were repaired on 2026-08-19 after that split had stamped them with eat-api's title and eat-api's GitHub Pages servers block.

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

Tagged areas include Campus, Navigation, Maps, Locations, and Search. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

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

Requests are made against a single base URL, https://nav.tum.de.

5 operations 5 paths 38 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.0
Base URL
https://nav.tum.de/api
License
Terms of Service
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), PropsResponse (6 properties). Each schema is shown below with its type and property counts.

RoomsOverviewUsageChildResponse
object
2 properties 2 required
ExtraComputedPropResponse
object
3 properties 1 required
CoordinateResponse
object
4 properties 3 required
ComputedPropResponse
object
3 properties 2 required
DefaultMapsResponse
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…
LocationDetailsResponse
object
15 properties 12 required
ResultsSection
object
4 properties 4 required
URLRefResponse
object
A link with a localized link text and url
2 properties 1 required
PropsResponse
object
Data for the info-card table
6 properties 1 required
RoomfinderMapEntryResponse
object
9 properties 9 required
RoomfinderMapResponse
object
2 properties 2 required
CoordinateSourceResponse
string
RoomsOverviewResponse
object
1 property 1 required
ResultEntry
object
6 properties 4 required
RoomsOverviewUsageResponse
object
3 properties 3 required
FeaturedOverviewItemResponse
object
4 properties 4 required
SectionsResponse
object
3 properties
RankingFactorsResponse
object
5 properties 3 required
OverlayMapsResponse
object
2 properties 1 required
SearchResponse
object
Returned search results by this
2 properties 2 required
OperatorResponse
object
Operator of a location
4 properties 4 required
CoordinateAccuracyResponse
string
TransportationResponse
object
7 properties 5 required
MapsResponse
object
3 properties 1 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
ImageInfoResponse
object
The information you need to request Images from the /cdn/{size}/{id}{counter}.webp endpoint
3 properties 3 required
BuildingsOverviewResponse
object
2 properties 2 required
FeaturedOverviewResponse
object
1 property 1 required
FloorResponse
object
5 properties 5 required
PossibleURLRefResponse
object
A link with a localized link text and url
2 properties 1 required
SourceResponse
object
2 properties 1 required
OverlayMapEntryResponse
object
5 properties 5 required
ResultFacet
string
BuildingsOverviewItemResponse
object
4 properties 3 required
NearbyLocationsResponse
object
1 property 1 required
LocationTypeResponse
string
FloorType
string

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.

mediaTUM OAI-PMH Repository Interface
TUM Shibboleth Identity Provider (SAML 2.0 Metadata)
TUMonline (CAMPUSonline) — Course Catalog and Identity
eat-api — Munich Student Canteen Menus
Technical University of Munich Campus API
Where this information came from

This is an independent, third-party profile of NavigaTUM, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.