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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
University of Warsaw

University of Warsaw Building API

The Building API from University of Warsaw — 25 operation(s) for building.

Documentation Provider Profile APIs.io OpenAPI GitHub

University of Warsaw Building API is one of 152 APIs that University of Warsaw publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Buildings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 37 operations across 25 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.2.25.

Requests are made against a single base URL, https://api.jaskier.uw.edu.pl.

37 operations 25 paths 17 schemas 7 DELETE17 GET7 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.25
Base URL
https://danebadawcze.uw.edu.pl/api/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

University of Warsaw Building API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization).

Paths & Operations 37

Across 25 paths, the API surfaces 37 operations — 7 DELETE, 17 GET, 7 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Building 37
GET
/api/v1/Building/{id}
Czytanie informacji o budynku z podanym id
getBuildingById 1 param → 200
PUT
/api/v1/Building/{id}
Aktualizacja budynku
updateBuilding 1 param body → 200
DELETE
/api/v1/Building/{id}
Usunięcie budynku
removeBuilding 2 params → 200
PUT
/api/v1/Building/{buildingId}/Unit/{buildingUnitId}
Aktualizacja jednostki budynku
updateBuildingUnit 2 params body → 200
DELETE
/api/v1/Building/{buildingId}/Unit/{buildingUnitId}
Usunięcie jednostki budynku
deleteBuildingUnit 2 params → 200
PUT
/api/v1/Building/{buildingId}/Room/{roomId}
Aktualizacja pokoju budynku
updateBuildingRoom 2 params body → 200
DELETE
/api/v1/Building/{buildingId}/Room/{roomId}
Usunięcie pokoju budynku
deleteBuildingRoom 2 params → 200
PUT
/api/v1/Building/{buildingId}/Plan/{planId}
Aktualizacja piętra budynku
updateBuildingPlan 2 params body → 200
DELETE
/api/v1/Building/{buildingId}/Plan/{planId}
Usunięcie piętra budynku
deleteBuildingPlan 2 params → 200
GET
/api/v1/Building/{buildingId}/Plan/{planId}/File
Pobranie obrazu piętra budynku
getBuildingPlanImage_1 3 params → 200
PUT
/api/v1/Building/{buildingId}/Plan/{planId}/File
Aktualizacja obrazu piętra budynku
addBuildingPlanImage 2 params body → 200
PUT
/api/v1/Building/{buildingId}/BuildingAttribute/{attributeLocationId}
Aktualizacja atrybutu lokalizacji budynku o podanym id
updateBuildingAttributeToBuilding 2 params body → 200
DELETE
/api/v1/Building/{buildingId}/BuildingAttribute/{attributeLocationId}
Usunuęcie atrybutu lokalizacji budynku
removeBuildingAttributeFromBuilding 2 params → 200
GET
/api/v1/Building
Listowanie danych o budynkach (z paginacją)
queryForBuildingWithPagination 5 params → 200
POST
/api/v1/Building
Dodawanie budynku
addBuilding body → 200
POST
/api/v1/Building/{id}/File/Upload
Upload pliku
uploadFile_1 1 param body → 200
GET
/api/v1/Building/{id}/BuildingAttribute
Pobranie atrybutów lokalizacji budynku
getBuildingAttributesForBuilding 1 param → 200
POST
/api/v1/Building/{id}/BuildingAttribute
Przypisanie atrybutu lokalizacji do budynku
addBuildingAttributeToBuilding 1 param body → 200
GET
/api/v1/Building/{buildingId}/Unit
Pobranie jendnostek budynku
getBuildingUnits 1 param → 200
POST
/api/v1/Building/{buildingId}/Unit
Dodanie jendnostki do budynku
addBuildingUnits 1 param body → 200
GET
/api/v1/Building/{buildingId}/Room
Pobranie pokoi budynku
getBuildingRooms_1 1 param → 200
POST
/api/v1/Building/{buildingId}/Room
Dodanie pokoju do budynku
addBuildingRoom 1 param body → 200
GET
/api/v1/Building/{buildingId}/Plan
Pobranie pięter budynku
getBuildingPlans_1 1 param → 200
POST
/api/v1/Building/{buildingId}/Plan
Dodanie piętra do budynku
addBuildingPlan 1 param body → 200
POST
/api/v1/Building/Thumbnail/Upload
Upload miniaturki
uploadThumbnail 1 param body → 200
GET
/api/v1/Building/{id}/Thumbnail/Download
Pobranie miniaturki
downloadThumbnail 2 params → 200
GET
/api/v1/Building/{id}/File
Lista plików przypisanych do budynku
getBuildingFiles 1 param → 200
GET
/api/v1/Building/{id}/File/{buildingFileId}/Download
Pobranie pliku
downloadFile_1 3 params → 200
GET
/api/v1/Building/{buildingId}/History
Czytanie historii zmian budynku
getBuildingHistory 1 param → 200
GET
/api/v1/Building/SearchPerson
Listowanie danych o osobach
searchPersonForBuilding 5 params → 200
GET
/api/v1/Building/SearchPerson('{personId}')
Czytanie informacji o osobie
getSearchPersonForBuilding 1 param → 200
GET
/api/v1/Building/ImportableFields
Lista pól dla których można wykonać import danych
getImportableFields → 200
GET
/api/v1/Building/Campus
Get campuses for building
getCampusesForBuilding → 200
GET
/api/v1/Building/BuildingAttribute
Pobranie atrybutów lokalizacji budynków
getAllAttributesForBuilding → 200
GET
/api/v1/Building/All
Listowanie danych o budynkach
queryForBuilding → 200
DELETE
/api/v1/Building/{id}/Thumbnail
Usunięcie miniaturki przypisanej do budynku
removeBuildingThumbnail 1 param → 200
DELETE
/api/v1/Building/{id}/File/{buildingFileId}
Usunięcie zdjęcia przypisanego do budynku
removeBuildingFile 2 params → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are BuildingResponse (33 properties), BuildingRequest (22 properties), HistoryResponse (11 properties), BuildingAttributeLocationResponse (11 properties). Each schema is shown below with its type and property counts.

BuildingRoomResponse
object
10 properties
OdataResponseBuildingResponse
object
2 properties
OdataResponsePersonViewResponse
object
2 properties
BuildingUnitResponse
object
9 properties
BuildingPlanResponse
object
4 properties
BuildingResponse
object
Informacje o budynku
33 properties
BuildingRoomPersonResponse
object
6 properties
HistoryResponse
object
11 properties
BuildingPlanRequest
object
1 property
BuildingAttributeLocationResponse
object
11 properties
BuildingRoomRequest
object
6 properties 2 required
CampusResponse
object
3 properties
BuildingUnitRequest
object
2 properties
BuildingFileResponse
object
6 properties
PersonViewResponse
object
10 properties
BuildingRequest
object
22 properties
BuildingAttributeLocationRequest
object
8 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-warsaw-building-api-openapi.yml Raw ↑

Other APIs University of Warsaw publishes across the network.

Dane Badawcze UW Research Data Repository REST API
AE Profile APIs.io
Dane Badawcze UW OAI-PMH Endpoint
AE Profile APIs.io
University of Warsaw Apiref API
AE Profile APIs.io
University of Warsaw Apisrv API
AE Profile APIs.io
University of Warsaw Calendar API
AE Profile APIs.io
University of Warsaw Courses API
AE Profile APIs.io
University of Warsaw Fac API
AE Profile APIs.io
ReIn UW Institutional Repository REST API
AE Profile APIs.io
ReIn UW OAI-PMH Endpoint
AE Profile APIs.io
University of Warsaw SAML Identity Provider (eduGAIN / PIONIER.Id)
AE Profile APIs.io
DataCite DOI Registration (REPOD / REPOD.DBUW)
AE Profile APIs.io
Crossref Membership (member 4211)
AE Profile APIs.io
#Buildings
← Back to U APIs
API Details
ID
university-of-warsaw:university-of-warsaw-building-api
Base URL
https://danebadawcze.uw.edu.pl/api/
Docs
https://danebadawcze.uw.edu.pl/
Provider
University of Warsaw
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=university-of-warsaw-building-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/university-of-warsaw-building-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of University of Warsaw Building API, 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.